12 replies to this topic

[Turambar]

I haven't understood when an (un)installation is considered interactive.
For example: if I have a mod with components 0 and 1, both installed; I [R]e-install 0.
It uninstalls 1 automatically, then 0 as requested. It then re-installs 0 as requested;I quit when it prompts for 1.
Which of these processes are %INTERACTIVE% and which aren't?

Another question: how can I re-install component 0 of a mod from terminal/cmd?
can I do something like setup-mymod(.exe) [options] or do I need a copy of weidu(.exe) called weidu?

Edited by Turambar, 24 January 2011 - 03:35 AM.

[the bigg]

The quick answer is: only use AT_NOW and AT_UNINSTALL in your mod (no AT_INTERACTIVE_* or AT_*_EXIT), and don't check against INTERACTIVE. Attempts at acting differently between INTERACTIVE and non-INTERACTIVE will backfire and leave you with a partially installed mod or otherwise cause you grief. If you really have to use INTERACTIVE, and then run a trillion of mock tests with ACTION_IF INTERACTIVE THEN BEGIN PRINT ~interactive~ END ELSE BEGIN PRINT ~non interactive~ END to ensure that it will work the way you designed it in all scenarios.

--yes, --force-install and friends count as INTERACTIVE, components automatically [R]einstalled if you answered [Q]uit are non-interactive (whether from the same tp2 or another tp2).

To reinstall a single mod component, setup-mymod.exe --force-install 124 works correctly.

[Turambar]

The quick answer is: only use AT_NOW and AT_UNINSTALL in your mod (no AT_INTERACTIVE_* or AT_*_EXIT), and don't check against INTERACTIVE. Attempts at acting differently between INTERACTIVE and non-INTERACTIVE will backfire and leave you with a partially installed mod or otherwise cause you grief. If you really have to use INTERACTIVE, and then run a trillion of mock tests with ACTION_IF INTERACTIVE THEN BEGIN PRINT ~interactive~ END ELSE BEGIN PRINT ~non interactive~ END to ensure that it will work the way you designed it in all scenarios.

--yes, --force-install and friends count as INTERACTIVE, components automatically [R]einstalled if you answered [Q]uit are non-interactive (whether from the same tp2 or another tp2).

To reinstall a single mod component, setup-mymod.exe --force-install 124 works correctly.

I actually wanted to use an A_I_U_E (in this case, at the end of component 1, AT_I_U_EXIT ~(./)setup-mymod(.exe) --reinstall 0~) as a "fool-saver": if component 1 is re-installed without touching component 0, the game is broken. Re-installing 0 (and thus 1) recovers it.
I have written "do not [R]e-install, but I thought that an AT_INTERACTIVE_EXIT which re-installs component 0 would fix the game automatically.
The thing is, if it triggers when I re-install component 0, it could cause a loop, and if it triggers when I [u] or [R] component 0 without touching component 1, it prevents uninstallation.

[the bigg]

Again, can't you could simply tell the three Linux players to grab generalized biffing rather than having to code multi-stage uninstallers and whatnot?

[Turambar]

Again, can't you could simply tell the three Linux players to grab generalized biffing rather than having to code multi-stage uninstallers and whatnot?

Yes, you're right, it's much easier and safer. I've removed all ITM, SPL,... biffs and written that they should use generalized biffing at the end of their installation.

I actually wanted to use an A_I_U_E (in this case, at the end of component 1, AT_I_U_EXIT ~(./)setup-mymod(.exe) --reinstall 0~) as a "fool-saver": if component 1 is re-installed without touching component 0, the game is broken. Re-installing 0 (and thus 1) recovers it.
I have written "do not [R]e-install, but I thought that an AT_INTERACTIVE_EXIT which re-installs component 0 would fix the game automatically.
The thing is, if it triggers when I re-install component 0, it could cause a loop, and if it triggers when I [u] or [R] component 0 without touching component 1, it prevents uninstallation.

Anyway, I've made some tests.
Uninstall 0, no change 1 -> 0 is interactive, 1 isn't.
But the --reinstall option from command line applies to all components -> both wuold uninstall interactively, and it would loop.
Is there any way to only re-install component 0 (I mean, a command line equivalent to the sequence [R] and [Q] in a manual installation)?

edit: another question. I've read, in the WeiDu documentation, that AT_NOW ~weidu.exe --make-biff ...~ crashes installation, and you must use AT_EXIT instead.
does it also happen with other Weidu.exe command line options? For example, can I AT_NOW --get-biff, in order to get some resources from a different game, and then normally work on them?

Edited by Turambar, 24 January 2011 - 03:12 AM.

[the bigg]

Anyway, I've made some tests.
Uninstall 0, no change 1 -> 0 is interactive, 1 isn't.
But the --reinstall option from command line applies to all components -> both wuold uninstall interactively, and it would loop.
Is there any way to only re-install component 0 (I mean, a command line equivalent to the sequence [R] and [Q] in a manual installation)?

--force-install 0 should do the trick.

edit: another question. I've read, in the WeiDu documentation, that AT_NOW ~weidu.exe --make-biff ...~ crashes installation, and you must use AT_EXIT instead.
does it also happen with other Weidu.exe command line options? For example, can I AT_NOW --get-biff, in order to get some resources from a different game, and then normally work on them?

Depends on the command; --get-biff works: if the target file was backed up, then it'll be restored (or erased) at Reinstall even if it's edited by an external source. If the file wasn't backed up the original can't be restored, but that doesn't really matter if you're creating a new file rather than overwriting an existing file.

[Turambar]

if the target file was backed up, then it'll be restored (or erased) at Reinstall even if it's edited by an external source. If the file wasn't backed up the original can't be restored, but that doesn't really matter if you're creating a new file rather than overwriting an existing file.

I don't quite get that...
if I --get-biff file.ext, it should leave the biff (and chitin.key) unmodified (just read them), and create a copy of file.ext in my folder; I can then patch the file and so on, and when I uninstall, the original file.ext will be in my folder. Does it work like that?

[the bigg]

Yes; my point is that, if file.ext already existed, it will be overwritten without creating a backup.

[Turambar]

Yes; my point is that, if file.ext already existed, it will be overwritten without creating a backup.

Ok, thanks for the warning. Anyway, I'd do it to an empty folder, and then MOVE, COPY,... it with WeiDU actions

[Turambar]

How does weidu --biff work?

./weidu --log bif.log --out biff/out.txt --biff data/stores.bif

should output a list of all files in data/stores.bif. It does not output anything but the log, is my command wrong?

Spoiler

WeiDU v 22700 Log

./weidu --log bif.log --out biff/out.txt --biff data/stores.bif
[./chitin.key] loaded, 590565 bytes
[./chitin.key] 182 BIFFs, 41794 resources
[./dialog.tlk] loaded, 10032337 bytes
[./dialog.tlk] 79246 string entries
[./linux.ini] loaded, 555 bytes
Possible HD/CD Path: [/home/francesco/.wine/dosdevices/../drive_c/bg2/]
Possible HD/CD Path: [//tmp/bg2cd/CD1/]
Possible HD/CD Path: [//tmp/bg2cd/CD2/]
Possible HD/CD Path: [//tmp/bg2cd/CD3/]
Possible HD/CD Path: [//tmp/bg2cd/CD4/]
Possible HD/CD Path: [/home/francesco/.wine/dosdevices/../drive_c/bg2/]
Possible HD/CD Path: [/home/francesco/.wine/dosdevices/../drive_c/bg2/cd1/]
Possible HD/CD Path: [/home/francesco/.wine/dosdevices/../drive_c/bg2/cd2/]
Possible HD/CD Path: [/home/francesco/.wine/dosdevices/../drive_c/bg2/CD2/]
Possible HD/CD Path: [/home/francesco/.wine/dosdevices/../drive_c/bg2/cd3/]
Possible HD/CD Path: [/home/francesco/.wine/dosdevices/../drive_c/bg2/cd4/]
Possible HD/CD Path: [/home/francesco/.wine/dosdevices/../drive_c/bg2/cd5/]
[./mplaynow.ini] loaded, 230 bytes
[./baldur (copia).ini] loaded, 1151 bytes
Possible HD/CD Path: [c:\bg2\]
Possible HD/CD Path: [Z:\tmp\bg2cd\CD1\]
Possible HD/CD Path: [Z:\tmp\bg2cd\CD2\]
Possible HD/CD Path: [Z:\tmp\bg2cd\CD3\]
Possible HD/CD Path: [Z:\tmp\bg2cd\CD4\]
[./autorun.ini] loaded, 1365 bytes
[./keymap.ini] loaded, 5615 bytes
[./baldur.ini] loaded, 2321 bytes
Possible HD/CD Path: [c:\bg2\]
Possible HD/CD Path: [c:\bg2\cd1\]
Possible HD/CD Path: [c:\bg2\cd2\]
Possible HD/CD Path: [c:\bg2\CD2\]
Possible HD/CD Path: [c:\bg2\cd3\]
Possible HD/CD Path: [c:\bg2\cd4\]
Possible HD/CD Path: [c:\bg2\cd5\]
[./dialogf.tlk] loaded, 10112514 bytes
[./dialogf.tlk] 79246 string entries
[./weidu] Using scripting style "BG2"

WeiDU Timings
load TLK 0.000
loading files 0.040
stuff not covered elsewhere 0.060
unmarshal KEY 0.060
unmarshal TLK 0.280
TOTAL 0.440

Is it possible to pipe the output of a WeiDU command into another? for example, list all files in x.bif | --biff-get them?

Edited by Turambar, 25 January 2011 - 06:18 AM.

[the bigg]

--biff requires to use backslashes (\) even on Linux. weidu --biff data\stores.bif --out log.txt produces this log.txt:

Spoiler

[DATA\STORES.BIF] contains INN2616.STO at index 0
[DATA\STORES.BIF] contains TEM2304.STO at index 1
[DATA\STORES.BIF] contains TEM4802.STO at index 2
[DATA\STORES.BIF] contains ARLED.STO at index 3
[DATA\STORES.BIF] contains HENDAK.STO at index 4
[DATA\STORES.BIF] contains KYLIE.STO at index 5
[DATA\STORES.BIF] contains LEHTINAN.STO at index 6
[DATA\STORES.BIF] contains MERCHANT.STO at index 7
[DATA\STORES.BIF] contains RIBALD.STO at index 8
[DATA\STORES.BIF] contains SHOP01.STO at index 9
[DATA\STORES.BIF] contains SHOP02.STO at index 10
[DATA\STORES.BIF] contains SHOP03.STO at index 11
[DATA\STORES.BIF] contains SHOP04.STO at index 12
[DATA\STORES.BIF] contains SHOP05.STO at index 13
[DATA\STORES.BIF] contains SHOP07.STO at index 14
[DATA\STORES.BIF] contains SLSHOP01.STO at index 15
[DATA\STORES.BIF] contains SLSHOP02.STO at index 16
[DATA\STORES.BIF] contains WALLACE.STO at index 17
[DATA\STORES.BIF] contains BMTHIEF.STO at index 18
[DATA\STORES.BIF] contains BSHOP01.STO at index 19
[DATA\STORES.BIF] contains BSHOP02.STO at index 20
[DATA\STORES.BIF] contains DMARK.STO at index 21
[DATA\STORES.BIF] contains DSHOP01.STO at index 22
[DATA\STORES.BIF] contains DSHOP02.STO at index 23
[DATA\STORES.BIF] contains FFBART.STO at index 24
[DATA\STORES.BIF] contains GORCH.STO at index 25
[DATA\STORES.BIF] contains SHOP06.STO at index 26
[DATA\STORES.BIF] contains THUMB.STO at index 27
[DATA\STORES.BIF] contains BHELM.STO at index 28
[DATA\STORES.BIF] contains BINNKEEP.STO at index 29
[DATA\STORES.BIF] contains DOGHMA.STO at index 30
[DATA\STORES.BIF] contains ROGER.STO at index 31
[DATA\STORES.BIF] contains SHOP08.STO at index 32
[DATA\STORES.BIF] contains SLILMAT.STO at index 33
[DATA\STORES.BIF] contains WILMAT.STO at index 34
[DATA\STORES.BIF] contains WINNKEEP.STO at index 35
[DATA\STORES.BIF] contains TEMHELM.STO at index 36
[DATA\STORES.BIF] contains TEMLATH.STO at index 37
[DATA\STORES.BIF] contains TEMTALOS.STO at index 38
[DATA\STORES.BIF] contains BERNARD.STO at index 39
[DATA\STORES.BIF] contains DAWNMAS.STO at index 40
[DATA\STORES.BIF] contains HELMPR.STO at index 41
[DATA\STORES.BIF] contains TALMISS.STO at index 42
[DATA\STORES.BIF] contains UHINN01.STO at index 43
[DATA\STORES.BIF] contains BERNARD2.STO at index 44
[DATA\STORES.BIF] contains UHMER01.STO at index 45
[DATA\STORES.BIF] contains UHMER02.STO at index 46
[DATA\STORES.BIF] contains UHMER03.STO at index 47
[DATA\STORES.BIF] contains MURCRAG.STO at index 48
[DATA\STORES.BIF] contains TANALLY1.STO at index 49
[DATA\STORES.BIF] contains KPCHAP01.STO at index 50
[DATA\STORES.BIF] contains TRRAK01.STO at index 51
[DATA\STORES.BIF] contains TRTHF02.STO at index 52
[DATA\STORES.BIF] contains JAYES.STO at index 53
[DATA\STORES.BIF] contains TEMSUP.STO at index 54
[DATA\STORES.BIF] contains TRMER03.STO at index 55
[DATA\STORES.BIF] contains TRMER04.STO at index 56
[DATA\STORES.BIF] contains DMARK1.STO at index 57
[DATA\STORES.BIF] contains CROBAR01.STO at index 58
[DATA\STORES.BIF] contains BDBART01.STO at index 59
[DATA\STORES.BIF] contains BERNARD3.STO at index 60
[DATA\STORES.BIF] contains BERNARD4.STO at index 61
[DATA\STORES.BIF] contains BERNARD5.STO at index 62
[DATA\STORES.BIF] contains BERNARD6.STO at index 63
[DATA\STORES.BIF] contains RIBALD2.STO at index 64
[DATA\STORES.BIF] contains RIBALD3.STO at index 65
[DATA\STORES.BIF] contains SCROLLS.STO at index 66
[DATA\STORES.BIF] contains SHTHSTOR.STO at index 67
[DATA\STORES.BIF] contains TRINNK01.STO at index 68
[DATA\STORES.BIF] contains TRMER01.STO at index 69
[DATA\STORES.BIF] contains TRMER02.STO at index 70
[DATA\STORES.BIF] contains TRMER04A.STO at index 71
[DATA\STORES.BIF] contains TRGENI01.STO at index 72
[DATA\STORES.BIF] contains TEMPLE.STO at index 73
[DATA\STORES.BIF] contains TYPE1.STO at index 74
[DATA\STORES.BIF] contains TYPE2.STO at index 75
[DATA\STORES.BIF] contains TYPE3.STO at index 76
[DATA\STORES.BIF] contains TRCAR04.STO at index 77
[DATA\STORES.BIF] contains PPINN01.STO at index 78
[DATA\STORES.BIF] contains PPSTOR01.STO at index 79
[DATA\STORES.BIF] contains PPUMB01.STO at index 80
[DATA\STORES.BIF] contains SEVBAR01.STO at index 81
[DATA\STORES.BIF] contains UDDROW22.STO at index 82
[DATA\STORES.BIF] contains UDDROW23.STO at index 83
[DATA\STORES.BIF] contains UDDROW24.STO at index 84
[DATA\STORES.BIF] contains UDDROW25.STO at index 85
[DATA\STORES.BIF] contains UDSVIR04.STO at index 86
[DATA\STORES.BIF] contains UDSVIR05.STO at index 87
[DATA\STORES.BIF] contains WALLACE2.STO at index 88
[DATA\STORES.BIF] contains UDDUER01.STO at index 89
[DATA\STORES.BIF] contains UDDUER02.STO at index 90
[DATA\STORES.BIF] contains BAG01.STO at index 91
[DATA\STORES.BIF] contains BAG02.STO at index 92
[DATA\STORES.BIF] contains BAG03.STO at index 93
[DATA\STORES.BIF] contains BAG04.STO at index 94
[DATA\STORES.BIF] contains GOVWAU01.STO at index 95
[DATA\STORES.BIF] contains BAG02B.STO at index 96
[DATA\STORES.BIF] contains BAG02C.STO at index 97
[DATA\STORES.BIF] contains BAG02D.STO at index 98
[DATA\STORES.BIF] contains BAG02E.STO at index 99
[DATA\STORES.BIF] contains BAG02F.STO at index 100
[DATA\STORES.BIF] contains BAG03B.STO at index 101
[DATA\STORES.BIF] contains BAG03C.STO at index 102
[DATA\STORES.BIF] contains BAG03D.STO at index 103
[DATA\STORES.BIF] contains BAG03E.STO at index 104
[DATA\STORES.BIF] contains BAG03F.STO at index 105
[DATA\STORES.BIF] contains SUELF10.STO at index 106
[DATA\STORES.BIF] contains WMART1.STO at index 107
[DATA\STORES.BIF] contains WMART2.STO at index 108
[DATA\STORES.BIF] contains SAHPR1.STO at index 109
[DATA\STORES.BIF] contains .0x0 at index 0
[DATA\STORES.BIF] contains .0x0 at index 0

On Linux, you can equivalently use `` or $() to pass the output of a command to a command line; such a construct doesn't exist on Windows.

Let me re-state that, if you use gen_biff -like coding, you can leave the files in SoS-Itm and let WeiDU move them back to the override without having to do it yourself. 12 MB of on-disk space for a mod that weights over 300 MB is not significant enough to warrant complex uninstall procedures.

[Turambar]

--biff requires to use backslashes (\) even on Linux. weidu --biff data\stores.bif --out log.txt produces this log.txt:

That same code, copy-pasted in my terminal, does not create any output file. I've tried to --list-biffs and

[DATA\STORES.BIF] 156344 bytes, 1 locations

is in its output. I've tried your code upper and lower case, but still without effect. It doesn't work with other biffs, either

./weidu --biff DATA\AREA550A.bif --out log.txt

[the bigg]

In Bash, \ is the escape character, and you need to escape it to be passed to WeiDU: weidu --biff data\\stores.cre --other-options.