DECOMPRESS_BIFF fails to find the file

[Magus_BGforge]

The environment is Mac OS, when using just biff filename, weidu can't find it. If relative path is used, then it does find it, but also gives a deprecated warning.

tp2

Code: [Select]

DECOMPRESS_BIFF ~25ambsnd.bif~output

Code: [Select]

Stopping installation because of error.

ERROR Installing [sl], rolling back to previous state
Will uninstall   0 files for [sl/sl.tp2] component 0.
Uninstalled      0 files for [sl/sl.tp2] component 0.
ERROR: Failure("DECOMPRESS_BIFF could not find biff 25ambsnd.bif")
baldur.ini

Code: [Select]

[Alias]
HD0:=C:\Games\bg2\
CD1:=C:\Games\bg2\
CD2:=C:\Games\bg2\
CD3:=C:\Games\bg2\
CD4:=C:\Games\bg2\
CD5:=C:\Games\bg2\
CD6:=C:\Games\bg2\
the file

Code: [Select]

bg2 adm$ ls -lh data/25ambsnd.bif
-rw-r--r--  1 adm  staff   7.3M May 12  2001 data/25ambsnd.bif

[Wisp]

This looks like Wine. I would guess you need an INI file with *nix paths to your biffs. Tolower might be able to make one for you, otherwise they look like this:

HD0:=/home/fredrik/Games/BaldursGateII/data
CD2:=/home/fredrik/Games/BaldursGateII/cd2
CD3:=/home/fredrik/Games/BaldursGateII/cd3
CD4:=/home/fredrik/Games/BaldursGateII/cd4
CD5:=/home/fredrik/Games/BaldursGateII/cd5

[CrevsDaak]

I'd recommend running Windows WeiDU on wine when you're touching a game-that-you-play-on-Wine's biff files. Otherwise you'll mangle the chitin.key. It's slower, it's bad for your mental health, but it greatly reduces the chances of having to fix your game's chitin.key.

[Wisp]

The hell? So if it breaks both backslashed key files and slashed ones, does Mac-WeiDU use slashes or backslashes? Regardless, DECOMPRESS_BIFF does not write to the key file, only MAKE_BIFF, DISABLE_FROM_KEY, --make-biff and --remove-biff do.

[Magus_BGforge]

I tried unix paths, the result is the same. (Just to clarify, it's fine by me to use relative paths in tp2, as long as it doesn't get removed from weidu)

I'm using mac weidu to work with wine-based game, and I don't have any probem with chitin.key. (did general biffing/unbiffing multiple times).

[Wisp]

Looks like it might be caused by a redundant data/ being appended onto the path in case it already ends with data/. Try unix paths but with HD0 not ending with data/, e.g., ./ (this might not work with other things, but just as a test). If it's not the data/ thing, please check your debug file. All the paths WeiDU tries are logged ("Looking for biff <x> at <path/x>").

I'm using mac weidu to work with wine-based game, and I don't have any probem with chitin.key. (did general biffing/unbiffing multiple times).

Good. Thanks for the info.

[Magus_BGforge]

I have no "data" in my paths at all:

Code: [Select]

HD0:=/Users/adm/bg2/
CD1:=/Users/adm/bg2/
CD2:=/Users/adm/bg2/
CD3:=/Users/adm/bg2/
CD4:=/Users/adm/bg2/
CD5:=/Users/adm/bg2/
CD6:=/Users/adm/bg2/

Relevant debug part:

Code: [Select]

[baldur.ini] loaded, 3989 bytes

HD0: is /Users/adm/bg2/
Looking for biff 25ambsnd.bif at CD6/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD5/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD4/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD3/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD2/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD1/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD6/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD5/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD4/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD3/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD2/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD1/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD1/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD2/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD3/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD4/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD5/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD6/data/25ambsnd.bif
Stopping installation because of error.
I've no idea why is it looking there.

[Wisp]

Can you check for lines like "Possible HD/CD Path:" in your debug? Also which ini files are loaded before these lines are printed, if they are. It looks like it might be raising an exception while reading the ini file and resorting to default paths. If you have lines like the aforementioned in your debug (and they correspond to what you have in your ini), at least it's not that.

[Magus_BGforge]

Code: [Select]

WeiDU v 24000 Log

 weidu sl/sl.tp2 --log sl.debug
[./CHITIN.KEY] loaded, 935665 bytes
[./CHITIN.KEY] 403 BIFFs, 65971 resources
[./autorun.ini] loaded, 1452 bytes
[./baldur.ini] loaded, 3989 bytes
Possible HD/CD Path: [CD1]
Possible HD/CD Path: [CD2]
Possible HD/CD Path: [CD3]
Possible HD/CD Path: [CD4]
Possible HD/CD Path: [CD5]
Possible HD/CD Path: [CD6]
Possible HD/CD Path: [CD1]
Possible HD/CD Path: [CD2]
Possible HD/CD Path: [CD3]
Possible HD/CD Path: [CD4]
Possible HD/CD Path: [CD5]
Possible HD/CD Path: [CD6]
[./keymap.ini] loaded, 5617 bytes
[./mplaynow.ini] loaded, 230 bytes
[./unins000.ini] loaded, 86 bytes
[./dialog.tlk] loaded, 18922795 bytes
[./dialog.tlk] 145275 string entries
[./dialog.tlk] claims to be writeable.
[./dialog.tlk] claims to be a regular file.
TOBEX/TOBEX.TP2  0 100 Installed


[Wisp]

Oh, I see. Sorry, I should have spotted this sooner. The old PPC version of BG used a different format for its [Alias] section and Mac-WeiDU is still looking for that. I'll make the necessary changes for Mac-WeiDU-that-does-not-target-PPC-BG and hope no one else's game breaks.

[Magus_BGforge]

This isn't fixed yet, is it? Trying 242, same result.

[Wisp]

Looks like I forgot. It's been committed now.