4 replies to this topic

[cujo]

I recently installed the BP-BGT-NEJ mod on my computer. After about 6 tries I finally managed to get it to the point where it would allow me to start a game. However, whenever I click the "Baldur's Gate" button in an attempt to start a Bg1 game it simply starts me in BG2. I've already installed the S and H patch so any help would be greatly appreciated (Windows XP by the way)

Before you installed the mod, did you run Setup-bp-bgt.exe? This will update the WeiDU installer if you have other mods in the same directory. It looks like Baldur's Gate Trioligy didn't install properly. Also did you start BG at least once to have a complete baldur.ini?

[cujo]

[quote name='Guest' date='Mar 26 2005, 09:20 PM']
[quote name='cujo' date='Mar 26 2005, 12:11 PM']
[/quote]
Before you installed the mod, did you run Setup-bp-bgt.exe? This will update the WeiDU installer if you have other mods in the same directory. It looks like Baldur's Gate Trioligy didn't install properly. Also did you start BG at least once to have a complete baldur.ini?
[right][/right]
[/quote]
Yes I did run BG1 before I installed it, I used the autoinstaller to make the whole thing install so I'm not sure if it did the setup.
[right][/right]
[/quote]
Before you run the autoinstaller double click on setup-bp-bgt.exe. If it asks you to install something press Q to exit. If you have a newer version of WeiDU from another mod or a patch in the same directory this will update the WeiDU version and give you a message that you have to restart the file because Windows won't allow WeiDU to restart the file itself. After you have the message about restarting run the autoinstaller.

[Sir BillyBob]

What Cujo is saying is that sometimes the autoinstaller won't work correctly because the patches and other mods may need to update themselves before you can run the autoinstaller. This isn't obvious to anyone who has never installed several mods together before. Each mod uses a Setup.exe file and that file has the (sometimes nasty) habit of looking at the other Setup.exe files and saying "hey, I am a newer version so let me update your files"). When it does this, the autoinstaller will fail but it looks like it installed everything correctly.

So to fix this issue, before you run the autoinstaller, run any of the Setup***.exe files in your SOA directory. Usually the Setup-BP-BGT.exe file is the one to run but it doesn't matter. You will see a DOS screen pop up and the text in the screen will tell you that the Setup you ran is looking at the other setup files (Setup-S&H6.EXE, etc). Once it is finished, then you can actually run the Autoinstaller.

Last thing, if nothing needs updating, do NOT install whatever mod you had just run, select Q to quit that install. You only ran the setup to make sure all the other setup files are current.