2 replies to this topic

[Stormbringer]

I have a request for all modders to include an additional statement in the ReadMe file and/or installation instructions. I recently installed BGT along about 10 other mods/tweaks/fix packs. I had quite a bit of trouble with mod installation and wasted 3-4 hours due to one minor problem.

What happened was that shortly after installing the BG2 fixpack, BGT and maybe another mod or two, I'd try to install the next mod and would get a DOS window showing a huge file verification scan rather than the usual chose language screen. This is the first time I tried adding mods (only second plaing the game) so I thought it might be a normal install procedure. After quite a while, (the scan looks at every single modification entry!) I'd get a install failure notice. Tried it again and same result. If I tried to install another mod, some worked and some had the same issue. Since doing another clean install is often suggested when problems arrise, I tried that. Same problem so searched onine and finally found one forum post with the solution.

As I'm sure all modders know, I learned that the modname.exe (ex. gminion.exe) is just a renamed weidu.exe file. If the mod I was trying to install used a version of weidu.exe older than one used by any already installed mod, it would go into that very lengthy scan and fail to install. All you need to do if you get that scan is close the window, download the latest version of weidu.exe, rename it the same as the modname.exe, copy/overwrite the modname.exe file with that one, and then install. I did that and had zero problems from that point on.

I'm making a request that modders simply put a sentence or two about this into their ReadMe/Installation Instructions so that others who experience the same issue won't needlessly waste a lot of time trying to solve something that's very easy to fix.

Thanks.

[Turambar]

As I'm sure all modders know, I learned that the modname.exe (ex. gminion.exe) is just a renamed weidu.exe file. If the mod I was trying to install used a version of weidu.exe older than one used by any already installed mod, it would go into that very lengthy scan and fail to install. All you need to do if you get that scan is close the window, download the latest version of weidu.exe, rename it the same as the modname.exe, copy/overwrite the modname.exe file with that one, and then install. I did that and had zero problems from that point on.

That's quite strange... the reason why that thing happens is that weidu always tries to update to its most recent window, and does it automatically, by copying the recent file over the previous one. Every time you start weidu, it checks all setup-... files in your directory; if anyone is newer or older, it just copies the newest one over all other files. The process usually takes a few seconds.
This has often happened to me, and never failed.
What OS do you have? Are you sure you didn't have anything preventing the file "setup-[mod].exe" to be modified?

[Jarno Mikkola]

This has often happened to me, and never failed.
What OS do you have? Are you sure you didn't have anything preventing the file "setup-[mod].exe" to be modified?

More accurately, the file might be flagged as "read only" when it's run, which makes the file unable to be updated to the latest version, which fails the procedure. More about the subject...
The BWS has this covered with an override function, it mostly works, but there's situations it doesn't either, which is why the post in the FAQ.