2 replies to this topic

[Scipio]

LATER EDIT: I found a way to get all the mods installed. It was a tedious and unsatisfactory process but it worked. I started again with all the mods and installed them one at a time, then shut down, switched back on and started with the next mod. Restarting the PC without switching off completely didn't work.

I'd still be interested to know what the problem might have been. RAM, maybe? I have 512MB. Or clutter that Windows loads at Startup? Or not the amount of RAM itself but the fact that Windows XP doesn't purge RAM effectively when an app or a file closes?

** If the moderators want to delete this post entirely to make room for something needing attention, please do so unless you think the problems I enjoyed may be relevant to anyone else some time soon.


EDIT: Please see the notes below the WeiDU log at the bottom of this post.

I am unable to install some WeiDU mods after doing the following:

1. Uninstalling all mods after a few bugs had stalled CtB and I thought a reinstall might help. I hadn't got very far yet.

2. Then deciding a complete BG2 reinstall might be good, too, although I had only WeiDU mods installed.

3. Reinstalling the game, I did:
- Bioware uninstall.
- Windows Explorer to remove everything else; I had no important saved games.
- Shut down and start.
- SoA, then restart;
- ToB, then restart;
- Patch BGII-ThroneofBhaal_Patch_26498_ENGLISH.exe (as always), then restart.

4. Installing mods, I had no problems with Fixpack (without Beta core fixes), Banterpack and IEP Banters. But then:

5. Tried BagBonus -- error.
6. Tried Lion Warrior kit -- error.
7. Tried Weimar's ItemUpgrade -- error.

The error message in the install screen was to this effect: "Please reinstall (actually, Windows won't let me in.)"

8. Deleted all files and folders for these three problematical mods from the game folder, which is the default:
Program Files / Black Isle / SoA

9. Shut down, restarted computer, tried to install these mods again, but got the same error message.

I run Win XP Pro. Might it help if I were to reinstall BG2 again but outside the Program Files folder? I know Windows can be Bill Gatesishly annoying about letting its users do some things, and I seem to remember that XP (or was it Vista?) won't let you install files in Program Files unless they go through the Windows installer... which weiDu doesn't, right?

I have background apps running, like resident Nod 32 and Spybot, plus whatever else Windows thinks should be running. I'm too dumb to to know which if any Startup files I can terminate, remove, or whatever. Although I didn't think this would matter with WeiDU, especially with little files like BagBonus or ItemsUpgrade.

This is my current WeiDU log:

// Log of Currently Installed WeiDU Mods
// The top of the file is the 'oldest' mod
// ~TP2_File~ #language_number #component_number // [Subcomponent Name -> ] Component Name
~BG2FIXPACK/SETUP-BG2FIXPACK.TP2~ #0 #0 // BG2 Fixpack - Core Fixes
~BG2FIXPACK/SETUP-BG2FIXPACK.TP2~ #0 #1 // BG2 Fixpack - Game Text Update
~BG2FIXPACK/SETUP-BG2FIXPACK.TP2~ #0 #2 // Super Happy Fun Lucky Modder Pack
~SETUP-BANTERPACK.TP2~ #0 #0 // Pocket Plane Banter Pack for BG2: Shadows of Amn
// Recently Uninstalled: ~SETUP-BANTERPACK.TP2~ #0 #1 // Install SOA Banter Accelerator script? (Increases the frequency of interparty banter)
// Recently Uninstalled: ~SETUP-BANTERPACK.TP2~ #0 #3 // Install TOB Banter Accelerator script? (Increases the frequency of interparty banter)
~IEPBANTERS/IEPBANTERS.TP2~ #0 #4 // Install Banter Accelerator? How much time would you like in between NPC banters in-game? -> 15 Minutes
~SETUP-BANTERPACK.TP2~ #0 #2 // Pocket Plane Banter Pack for BG2: Throne of Bhaal
~IEPBANTERS/IEPBANTERS.TP2~ #0 #0 // Extended NPC-NPC Interaction SoA
~IEPBANTERS/IEPBANTERS.TP2~ #0 #1 // Extended Minsc/Aerie Interaction ToB
~IEPBANTERS/IEPBANTERS.TP2~ #0 #2 // NPC Conflict Revisions

EDIT:
1. Without changing anything I have been able to install the Viconia Friendship beta mod without any problems.
2. I then tried to install Level 1 NPCs. It took about 20 minutes before the installation terminated with this message (abbreviated): "SysError... Too many open files."
3. For the heck of it I tried to install the Lion Warrior kit again. Some days ago I had installed the Lion Warrior OK. It took about 5 seconds that time. Now it did actually start installing without any "Windows won't let me in," but it began with the same long, long installation process as Level 1 NPCs, so I terminated it.

The WeiDU log now shows Viconia freindship installed successfully.

Does Win XP sometimes prevent an action, then mull over things for an hour and finally let you proceed?

Using Windows... why did we ever stop using DOS?

Edited by Scipio, 12 April 2008 - 07:04 PM.

[Jarno Mikkola]

Using Windows... why did we ever stop using DOS?

Well I support the double-click theory... + the OS upgrade theory...

But back to the original point of this thread.
Your problem mostly can be caused by the different WeiDU.exe's . Yes, the setup-mod.exe is actually a WeiDU.exe just renamed to install the mod using the command lines from the setup-mod.tp2...
The problem is caused by the difference of the operating systems( ) as the different versions of the WeiDU.exe's are actually different OS's. So they behave differently. There is always a few cliches when the OS changes, which thus can cause headache. So usually the WeiDU auto updates the exes to make sure they are the same. And some of the problem can raise from this or that you install a different version and it has different rules. A good example: "SysError... Too many open files." The WeiDU had a temperal build in system to prevent multiple WeiDU installations at the same time, that can cause havoc on their own, but the system was determined to be faulty cause of the usual user error of closing the WeiDU-window the wrong way(the red hot X a the top, not the Enter -key, as commanded by the WeiDU at the end) causing the WeiDU.lock to stay in the BG directory. It was removed from the later editions, but it's still in the v1zyWeiDU.exe . The lock(file) can be removed if you know that no Weidu.exe's are running, because you have just exited from them.

Yey, the OS upgrade theory.

Edited by Jarno Mikkola, 14 April 2008 - 05:58 AM.

[Scipio]

Using Windows... why did we ever stop using DOS?

Well I support the double-click theory... + the OS upgrade theory...

This is weird, Jarno! There were about a dozen helpful replies between my first post and your reply. They've gone. They did include much of what you've just told me, so thanks, my good Imp.

The server was offline for a while last night. It wasn't just the occasional traffic problem, something was right down. I can't think what else might have obliterated those other guys' posts and left mine here.