Baldurdashing a clone install

[Guest Guest_flem_*]

I'm trying to keep my clean install totally clean, since some mod setups don't want even Baldurdash. But the fixpack exe doesn't like installations it doesn't detect in the registry...

 

Does anyone have a neat solution to this? I remember once I was able to unpack the fixpack as an archive, but it's been ages and I can't remember what program did the trick.

[Idobek]

IRRC WinRAR is able unpack the archives.

[flem]

IRRC WinRAR is able unpack the archives.

<{POST_SNAPBACK}>

 

It worked; thanks for the help!

 

Incidentally, I also had to comment out a data/25scripts.bif check in Sim's Quest Pack tp2 (the improved oasis component) to get it to install. Not sure if I should take that up with him at PPG or if it's something for you guys to address. (And I hope a similar check hasn't invisibly botched the install of other ToB-seeking components...)

[Idobek]

Incidentally, I also had to comment out a data/25scripts.bif check in Sim's Quest Pack tp2 (the improved oasis component) to get it to install.  Not sure if I should take that up with him at PPG or if it's something for you guys to address.  (And I hope a similar check hasn't invisibly botched the install of other ToB-seeking components...)

<{POST_SNAPBACK}>

Unfortunately it is possible that there a silent ToB checks in some mods that won't detect ToB on multiple install setups. ToB checks that are multiple install friendly are being phased in almost everywhere but some mods won't have been updated yet. I suggest you run a search for ACTION_IF FILE_EXISTS on mods that you suspect have ToB content, if they are searching for a ToB bif then you'll want to change it to a file that's always there.

[andrewas]

Incidentally, I also had to comment out a data/25scripts.bif check in Sim's Quest Pack tp2 (the improved oasis component) to get it to install.  Not sure if I should take that up with him at PPG or if it's something for you guys to address.  (And I hope a similar check hasn't invisibly botched the install of other ToB-seeking components...)

<{POST_SNAPBACK}>

 

I was under the impression that the normal way of doing a ToB check was to look for data\25dialog.bif , which should be copied. I'll add 25scripts.bif to the next version.

 

Anyone have any other files which need adding?

[Orions_Stardom]

I was under the impression that the normal way of doing a ToB check was to look for data\25dialog.bif , which should be copied.  I'll add 25scripts.bif to the next version.

 

Anyone have any other files which need adding?

Since the game ignores ./data/* (using hd0/data/*), it might be easier to kludge around it, with something like the following shell script:

for file in $originalgamedir/data/25*bif; do
    echo 'KLUDGY DUMMY FILE'  > $newgamedir/`basename $file`
done

 

Rationale: since the file isn't actually used, except in these checks, the content of it doesn't matter. It will save us some space to just put some filler in there, rather than copying the original file (on average, I imagine a *.bif is bigger than 17 characters ). The important thing is that the file has to exist, and contain more than zero bytes. This can be safely limited to 25*bif, since that prefix is used to indicate TOB. The only potential issue that I can see with this is if WeiDU happens to attempt to read that bif to find a file for COPY_EXISTING. If it doesn't, all should well. If it does, we should keep copying the files for now, and maybe report this as a bug against WeiDU. But the important thing is that dealing with *every* TOB-specific bif, if it exists, should guarantee us compatibility with all mods.

[Orions_Stardom]

This will still be a problem in the current versions. Moving to Bug Reports to remind myself to fix it.

[Orions_Stardom]

I've added code to CloneWorker.java such that if data isn't copied, it will create a file in the sink of the same name with this content:

TO WHOM IT MAY CONCERN
Hello.
Regards,
The MultiInstall Tool

 

Which is still a fair bit smaller than most bifs.