11 replies to this topic

[nooneatall]

I got what I wanted for BP, started the installation...

Well, it just got stuck.

I know that some oparts o it take a while to process, but I've been watching very carefully for thirty minutes and it doesn't appear to be processing anything. The cmd window is open, not doing anything and showing the flashing DOS curser which means it's not gonna work. I started the install and then left it alone completely.

I'm doing a BG2-only, TACTICS-level install, but with many fewer mods than the full. I did in fact avoid any dependencies. I previously had a bad install of BP, but have fully cleansed any and all files from the the computer (things would be in totally different sections of the drive now anyhow).


This is the last thing it displays.

[Setup-WeiDU.exe] WeiDU version 21100
Auto-updating on behalf of [Setup-A6XPPATCH.exe]
Copying [Setup-WeiDU.exe] -> [Setup-A6XPPATCH.exe]:
Auto-updating on behalf of [Setup-A6XPPATCH.exe] <done>
[Setup-A6XPPATCH.exe] WeiDUversion 21100
<setup-allison.exe> Queried <pid = 36>[WeiDU version 21000
[./CHITIN.KEY] 182 BIFFs, 41793 resources
[.dialog.tlk] 74107 string entries
[WeiDU=Backup] Using scrupting style "BG2"


Any hints? Will I be able to close this and restart without botching the whole install?


Second, I had to remove several mods I had hoped to pop in because BP won't recognize them for some reason. Specifically, BPO just won't recognize Kelsey. BP Setup wil download Kelsey just finer, and unpack, but then the installer doesn't recognize it. I have had this happen in both attempts to setup BP.

[nooneatall]

Just reporting in. Still doing it.

[Ranadiel]

Just to make sure, are you doing a BiG World Project install? Based on what you have said, it looks to me that you are, but I just want to be sure.

Assuming that you are, I know one way that you might be able to continue the install without botchng the entire install. However be aware that I do not know of anyone else besides myself who has tried to do this, and I never completed an run through so this method may result in bugs that I am unaware of(although I don't think that hould happen). Also please be aware that I am basing these instructions off of the Big World Project version 5.5, as that is what I have immediatly available. There may be some differences with the latest version, but it should be mostly the same.

Anyways, what you are going to want to do is oen up the Big World Install batch file in notepad(or any other text editor). For reference mine is named, "BiG World Install v5.5.1". In here you are going to be deleting all the instructions that you have already run. I personally reccomend that you maintain the pre-install stuff just because I don't know which of those steps are important. So you want to find the first portion of the install file that actually modifies BGII in anyway.

From my version of the install file, the indicator of this is the following lines:

%IFG.%	 L A S S T   D E N   W A H N S I N N   B E G I N N E N !
%IFE.%	   L E T   T H E   M A D N E S   B E G I N !

Below this you are going to want to look for the first time that a mod is actually called. Below is a sample from my install bat:

%.%PRE-NEJ MODS | %M%
%.%
%.%
%IFGS%TP%S%TP%L%0%SK% 0 | %M%
%IFES%bg2fixpack%S%bg2fixpack%L%0%SK% 0 1 3 100 101 103 104 106 107 108 109 110 111 112 113 114 | %M%
%IFGS%bg2fixpack%S%bg2fixpack%L%3%SK% 0 3 100 101 103 104 106 107 108 109 110 111 112 113 114 | %M%
%IFES%BDToBv166%S%BDToBv166%L%0%SK% 2 3 4 5 7 | %M%
%IFGS%BDToBv166%S%BDToBv166%L%1%SK% 2 3 4 5 7 | %M%
%IFS%1pp%S%1pp%L%0%SK% 0 1 2 3 4 5 6 7 8 9 10 11 | %M%
%IFS%spell_rev%S%spell_rev%L%0%SK% 0 1 2 3 | %M%
%IFS%RR%S%RR%L%0%SK% 0 | %M%

Note that there are several entries between the previosu two code excerts. I reccomend leaving those lines as they should not cause any problems and some of them might be important. However do be aware that your first mods may not be the Pre-NEJ Mods due to the version difference. Just look for the first instance similair to the above(ideally there should be a header above it informing you that it is a section of mods).

Once you have located the first section of mods in the batch file, your next step is to find the last mod that was installed. In your case this appears to be Allison. So control F until you find an instance of th word allison after mods begin to be installed. Once you have found these two locations delete everything from the first mod until Allison. Whether you delete the Allison mod line depends on if you want to try to install it in the batch format again. I personally would try to install it outside of the batch and then run the batch(meaning delete the entry for her), but that is just personal opinion.

Another thing I should mention is that you should back up your BiG World debug file before the running the batch again to be sure that you don't lose it. I think that should cover everything.

-=Edit: Oh yeah I should mention that I have no idea of what will happen if you close the installer now. I developed this method because of a forced premature closing by the program not by the user. I'm assuming you can the Allison weidu and undo any changes made by that install, but I don't know for sure.=-

Edited by Ranadiel, 01 August 2009 - 02:54 PM.

[Jarno Mikkola]

This is the last thing it displays.

[Setup-WeiDU.exe] WeiDU version 21100
Auto-updating on behalf of [Setup-A6XPPATCH.exe]
Copying [Setup-WeiDU.exe] -> [Setup-A6XPPATCH.exe]:
Auto-updating on behalf of [Setup-A6XPPATCH.exe] <done>
[Setup-A6XPPATCH.exe] WeiDUversion 21100
<setup-allison.exe> Queried <pid = 36>[WeiDU version 21000
[./CHITIN.KEY] 182 BIFFs, 41793 resources
[.dialog.tlk] 74107 string entries
[WeiDU=Backup] Using scrupting style "BG2"

Same as in here. Read, read, read. Copy and rename a more recent WeiDU or setup-*.exe as setup-allison.exe and rerun the setup-*.exe ...

Edited by Jarno Mikkola, 01 August 2009 - 03:06 PM.

[nooneatall]

I just realized I as being rude. Thank you both for being such a help.

[dreamer2007]

I am doing Big World, yup. I went and tried something else before I got these messages. It may actually be working. it is taking a very long time and it may be gitching and re-installing things multiple times.

Fortunately, I have a backup of a pure and clean BG2-SOA install. (Uhh... how exactly do I revert back to the backup files? ;D

Assuming this does not work out, what can I do to avoid this in the future? Allison is an NPC mod, right? Will avoiding that avoid the problem? Second, is this a problem which comes up only with the Tactics install? Because I can take that out and go with Reccomended. Should I also avoid the Widescreen mod?

I wished there had been a good warning about some of these probblems packages with the Big World installer. Thus far I've spent something like three days of downloading and installing and dealing with bugs.

You encounter all these problems because the current version isn't stable anymore, and it would be a good idea to wait for BWP version 8 like many of us. Look here for info about this.

[Lollorian]

It might be a good idea to run the WeiDU auto-update before actually starting with the install.bat, that way once all the setup-X's are updated, the bat installer won't halt in the middle and people who can't go about editing the bat file (like me ... a while earlier ) won't have to start from scratch (clean install).

Otherwise, nooneatall could try to delete all the %IFES% and %IFGS% lines upto the %IFES%allison% line
Messy procedure warning

1. open the install.bat in notepad,
2. do a search for %IFES%allison% first
3. start deleting lines from %IFES%A6XPPATCH% ... till the line above %IFES%allison%...

Of course, make a backup of the install.bat just in case something screws up

Otherwise, if you've already started with a clean install,

1. just run any Setup-Modname.exe file (before install.bat starts)
2. let the updater update itself
3. if it freezes, replace like Jarno said
4. Finally, there should be a list allowing you to choose language etc. Close the cmd prompt window
5. start install.bat (because everything's already updated, it won't get stuck )

Cheers,
Lol

[Jarno Mikkola]

Otherwise, nooneatall could try to delete all the %IFES% and %IFGS% lines upto the %IFES%allison% line
Messy procedure warning

1. open the install.bat in notepad,
2. do a search for %IFES%allison% first
3. start deleting lines from %IFES%A6XPPATCH% ... till the line above %IFES%allison%...

Yeah, but that would require that nooneatall would have already &/(% up his/her install cause the BWP Fixpack would need to be included in the manual install and that's hard... and then he/she would swich to the auto install and even then it would work cause the setup-allison.exe, that is the WeiDU.exe renamed... would still be in the folder and the WeiDU.exe's auto-update would still be locked into the same phase, most probably.

[Lollorian]

Well, what I thought was this:

[Setup-WeiDU.exe] WeiDU version 21100
Auto-updating on behalf of [Setup-A6XPPATCH.exe]
Copying [Setup-WeiDU.exe] -> [Setup-A6XPPATCH.exe]:
Auto-updating on behalf of [Setup-A6XPPATCH.exe] <done>
[Setup-A6XPPATCH.exe] WeiDUversion 21100
<setup-allison.exe> Queried <pid = 36>[WeiDU version 21000
[./CHITIN.KEY] 182 BIFFs, 41793 resources
[.dialog.tlk] 74107 string entries
[WeiDU=Backup] Using scrupting style "BG2"

That piece shows that nooneatall's install had stalled while the WeiDU auto-updater tries to update the (seemingly) bugged Setup-allison.exe. So, I figured everything upto the Allison mod must've been installed without errors (which was rather silly considering we haven't seen his/her WeiDU.log yet ) That's why I suggested deleting those (already installed) lines from the install.bat.

Now, I forgot to mention that the "delete-lines-and-restart-install.bat-again-method" was used to resume a hanged install (so that you don't have to reinstall and start from scratch) AND I also forgot to quote Jarno on that you have to manually replace any stalling Setup-X.exe's with a renamed WeiDU.exe

And yes, it does run the fixpack script again, but the Fixpack.bat is coded rather beautifully and does not apply patches it has already applied (or so it seems ) So it probably doesn't matter if it's run again. (Also, deleting the fixpack lines would make the "procedure" unnecessarily long and complicated )

Now if you're talking about the file-moving stuff that occurs between individual mod installs, it's coded in the install.bat and shouldn't be affected as those lines are also deleted

Cheers,
Lol

Edited by Lollorian, 03 August 2009 - 06:01 AM.

[Jarno Mikkola]

...
That piece shows that nooneatall's install had stalled while the WeiDU auto-updater tries to update the (seemingly) bugged Setup-allison.exe. So, I figured everything upto the Allison mod must've been installed without errors (which was rather silly considering we haven't seen his/her WeiDU.log yet ) That's why I suggested deleting those (already installed) lines from the install.bat.

Well, I am actually talking about that the BiG World Install.bat assumes all the setup-*modname*.exe's to be there before it starts the final re-check, which would exclude the fact that any mods would have been installed before...

Edited by Jarno Mikkola, 03 August 2009 - 06:39 AM.