4 replies to this topic

[Sam.]

After my installation of Classic Adventures, I notice that NearInfinity complains about missing .BIF files while performing various functions. It isn't important since CA is a total conversion and it is stuff from SoA (areas in particular) that is missing. It could be the .BIF files were deleted to save space since they were unnecessary but chitin.key wasn't updated accordingly, I don't know. Regardless, I would really like to run a Keyfile cleanup, but the one in NearInfinity tends to screw thing up. Is something like this possible to do with WeiDU or is there another program out there that does the job right?

The missing .BIFs include but are not necessarily limited to:

• DATA/PROGTEST.BIF
  
• DATA/PROGTES2.BIF
  
• DATA/AREA020A.BIF
  
• DATA/AREA020B.BIF
  
• DATA/AREA090B.BIF
  
• DATA/AREA090C.BIF
  
• DATA/AREA0900.BIF
  
• DATA/AREA090A.BIF
  
• DATA/AREA1100.BIF
  
• DATA/AREA110A.BIF
  
• DATA/AREA1200.BIF
  
• DATA/AREA120A.BIF
  
• DATA/AREA120B.BIF
  
• DATA/AREA1300.BIF
  
• DATA/AREA130A.BIF
  
• DATA/AREA130B.BIF
  
• DATA/AREA1400.BIF
  
• DATA/AREA140A.BIF
  
• DATA/AREA140B.BIF
  
• DATA/AREA1500.BIF
  
• DATA/AREA150A.BIF
  
• DATA/AREA150B.BIF
  
• DATA/AREA150C.BIF
  
• DATA/AREA1600.BIF
  
• DATA/AREA160A.BIF
  
• DATA/AREA160B.BIF
  
• DATA/AREA1700.BIF
  
• DATA/AREA1800.BIF
  
• DATA/AREA1900.BIF
  
• DATA/AREA190A.BIF
  
• DATA/AREA2000.BIF
  
• DATA/AREA200A.BIF
  
• DATA/AREA200B.BIF
  
• DATA/AREA2100.BIF
  
• DATA/AREA210A.BIF
  
• DATA/AREA210B.BIF
  
• DATA/AREA2200.BIF
  
• DATA/AREA220A.BIF
  
• DATA/AREA2300.BIF
  
• DATA/AREA2400.BIF
  
• DATA/AREA2500.BIF
  
• DATA/AREA2600.BIF
  
• DATA/AREA260A.BIF
  
• DATA/AREA2700.BIF
  
• DATA/AREA2800.BIF
  
• DATA/AREA280A.BIF
  
• DATA/AREA280B.BIF
  
• DATA/AREA2900.BIF
  
• DATA/AREA290A.BIF

TIA,
Sam.

[Miloch]

I have never done anything with .key files but I suspect after reading the IESDP key format, doing the right READs and careful DELETE_BYTEs and then WRITEing the updated counts when you've removed entries, you could do it. Don't ask me for the code though, because as I said, I've never done it .

Edit: the lazy man's option might be just overwriting those BIFs with zero-byte files.

Edited by Miloch, 27 December 2009 - 11:53 AM.

[Jarno Mikkola]

Edit: the lazy man's option might be just overwriting those BIFs with zero-byte files.

Can you confirm that we can make WeiDU.exe biff an empty folders? And thus create illusions of the file actually being there, so we don't have to put the renamed sw1h01.itm there... so it has something to actually do.

Edited by Jarno Mikkola, 27 December 2009 - 01:45 PM.

[Miloch]

Can you confirm that we can make WeiDU.exe biff an empty folders? And thus create illusions of the file actually being there, so we don't have to put the renamed sw1h01.itm there... so it has something to actually do.

I'm not talking about biffing empty folders, or biffing anything at all, but just COPYing a blank file over to the location of the .bif files. And these are all (unused in CA) area file biffs presumably that Sam's talking about, not those for standard items or anything, the nulling of which would be incredibly foolish (though WeiDU keeps a backup of everything it overwrites anyway). That way those files are still there but they're not taking up space and you don't have to mess with chitin.key. But the only real point of doing this is to avoid modding tool false reports. You're not saving much space unless you delete the backup biffs or tell WeiDU not to back them up in the first place with COPY -. In which case you're probably not going to be able to uninstall CA (though why would you bother doing that when you can do a clean BG2 install).

[Jarno Mikkola]

Can you confirm that we can make WeiDU.exe biff an empty folders? And thus create illusions of the file actually being there, so we don't have to put the renamed sw1h01.itm there... so it has something to actually do.

I'm not talking about biffing empty folders, or biffing anything at all, but just COPYing a blank file over to the location of the .bif files. And these are all (unused in CA) area file biffs presumably that Sam's talking about, not those for standard items or anything, the nulling of which would be incredibly foolish (though WeiDU keeps a backup of everything it overwrites anyway). That way those files are still there but they're not taking up space and you don't have to mess with chitin.key. But the only real point of doing this is to avoid modding tool false reports. You're not saving much space unless you delete the backup biffs or tell WeiDU not to back them up in the first place with COPY -. In which case you're probably not going to be able to uninstall CA (though why would you bother doing that when you can do a clean BG2 install).

You have to forget that I am talking about CA, I am not... I am actually talking about making(read the rest...) the WeiDU.exe think that the few files that are required by ACTION_IF FILE_EXISTS to initialize something... exists, but might not have actual references within the chitin.key file to the .bif file, other than the files being elsewhere(not biffed infact as they never were).