Jump to content


Photo

Installation Pauses


  • Please log in to reply
8 replies to this topic

#1 locater16

locater16
  • Member
  • 1 posts

Posted 23 February 2010 - 10:15 PM

Running 8.3 and Win 7

Installation pauses on DOS command window, last entry is "[WeiDU-Backup] Using Scripting Style BG2"
Then it just sits there. I've waited over an hour for nothing to happen. Anyone know if it's done, screwing up, or etc.

#2 Jarno Mikkola

Jarno Mikkola

    The Imp in his pink raincoat.

  • Member
  • 10911 posts

Posted 23 February 2010 - 10:33 PM

...

One or more of the WeiDU.exe's that are re-named as setup-*modname*.exe's has not been patched(more info on the matter, answer #1), exit the installer with the X, run the BiG World Setup.vbs and let it redo the setup until it reopens the cmd.exe window where it asks language and exit it, then run one of the setup-*modname*.exe's, any one of them which will start the auto-patching ritual until you find it will stop just like it does for you now, and exit that, and manually update the WeiDU.exe by copying the current game folders WeiDU.exe to the same directory and then renaming them according to the list that the window says that have failed to update.

Edited by Jarno Mikkola, 23 February 2010 - 10:34 PM.

Deactivated account. The user today is known as The Imp.


#3 horred the plague

horred the plague

    Scourge of the Seven Seas

  • Modder
  • 1899 posts

Posted 24 February 2010 - 06:06 AM

...

One or more of the WeiDU.exe's that are re-named as setup-*modname*.exe's has not been patched(more info on the matter, answer #1), exit the installer with the X, run the BiG World Setup.vbs and let it redo the setup until it reopens the cmd.exe window where it asks language and exit it, then run one of the setup-*modname*.exe's, any one of them which will start the auto-patching ritual until you find it will stop just like it does for you now, and exit that, and manually update the WeiDU.exe by copying the current game folders WeiDU.exe to the same directory and then renaming them according to the list that the window says that have failed to update.


Now now Mr Jarno Mikkola, nowhere does it say in this post, that they were using the BigWorld Setup. There's a fair chance they are, but it is not a currently established fact. :P

Locater16, Mr Mikkola's procedure for a stalled Weidu.exe is accurate, but if you're not using BigWorld Setup there is no reason to open that VisualBasic Script. Otherwise, do as suggested. :)

Edited by horred the plague, 24 February 2010 - 06:07 AM.
Forgot to smile


#4 Jarno Mikkola

Jarno Mikkola

    The Imp in his pink raincoat.

  • Member
  • 10911 posts

Posted 24 February 2010 - 06:18 AM

Running 8.3...

Now now Mr Jarno Mikkola, nowhere does it say in this post, that they were using the BigWorld Setup. There's a fair chance they are, but it is not a currently established fact. :P

Ho ho ho, at least I assume the 8.3 is the BWS v8.3... after all the BP is v1.79... ho ho ho(santa laughter).

Deactivated account. The user today is known as The Imp.


#5 horred the plague

horred the plague

    Scourge of the Seven Seas

  • Modder
  • 1899 posts

Posted 24 February 2010 - 12:59 PM

Running 8.3...

Now now Mr Jarno Mikkola, nowhere does it say in this post, that they were using the BigWorld Setup. There's a fair chance they are, but it is not a currently established fact. :P

Ho ho ho, at least I assume the 8.3 is the BWS v8.3... after all the BP is v1.79... ho ho ho(santa laughter).


*curses, and scripts a better mousetrap*

#6 -Lighthouse-

-Lighthouse-
  • Guest

Posted 07 March 2010 - 05:51 PM

Jarno Mikkola - I'm having a the same problem as listed above, however I must admit to having some difficulty following your fix instructions. Could you please re-explain?

#7 Jarno Mikkola

Jarno Mikkola

    The Imp in his pink raincoat.

  • Member
  • 10911 posts

Posted 08 March 2010 - 12:23 AM

Jarno Mikkola - I'm having a the same problem as listed above, however I must admit to having some difficulty following your fix instructions. Could you please re-explain?

Re-explain what?
We'll give it a try.
The mod installer is always the WeiDU.exe renamed as setup-*modname*.exe, it's done so that it will take orders from a file called setup-*modname*.tp2... see the tp2 is the actual command lines that allow you to copy and modify the files.
Now, because of this, the WeiDU.exe's need all be of the same version, or they could do different things with the same command line, which is obvoiusly a bad thing.
Now to manage this, the WeiDU.exe's all have an automatic update procedure... but it's not always ran(or it fails at points) when you install the bits in with a .bat installer like the BiG World Install.bat... from which the problem comes from.

Now, you can do the update simply by first having all the setup-*modname*.exe's in the game folder(at where you usually use the BiG World Setup.vbs program until it's completed), then running one of them in the game folder, which should update all of them... it will list all of the setup-*modname*.exe's and say what versions they are and if the updating is successful. Then you just list the game folders files by size ans see what their exact size is. Most if not all of their size should be really close to 600 Kb(if the latest version of the WeiDU.exe is v21300).
Now then you see if you can see any other size files that start with 'setup-' and end with '.exe' and then delete them all and then copy the WeiDU.exe that's in the game folder inthere again so you get copies of it, and then you rename the copies as the deleted setup-*modname*.exe's . It's done, and then you can just start the BiG World Install.bat ...
Understood?

Edited by Jarno Mikkola, 08 March 2010 - 01:44 AM.

Deactivated account. The user today is known as The Imp.


#8 -Lighthouse-

-Lighthouse-
  • Guest

Posted 08 March 2010 - 04:43 PM

Jarno Mikkola - I'm having a the same problem as listed above, however I must admit to having some difficulty following your fix instructions. Could you please re-explain?

Re-explain what?
We'll give it a try.
The mod installer is always the WeiDU.exe renamed as setup-*modname*.exe, it's done so that it will take orders from a file called setup-*modname*.tp2... see the tp2 is the actual command lines that allow you to copy and modify the files.
Now, because of this, the WeiDU.exe's need all be of the same version, or they could do different things with the same command line, which is obvoiusly a bad thing.
Now to manage this, the WeiDU.exe's all have an automatic update procedure... but it's not always ran(or it fails at points) when you install the bits in with a .bat installer like the BiG World Install.bat... from which the problem comes from.

Now, you can do the update simply by first having all the setup-*modname*.exe's in the game folder(at where you usually use the BiG World Setup.vbs program until it's completed), then running one of them in the game folder, which should update all of them... it will list all of the setup-*modname*.exe's and say what versions they are and if the updating is successful. Then you just list the game folders files by size ans see what their exact size is. Most if not all of their size should be really close to 600 Kb(if the latest version of the WeiDU.exe is v21300).
Now then you see if you can see any other size files that start with 'setup-' and end with '.exe' and then delete them all and then copy the WeiDU.exe that's in the game folder inthere again so you get copies of it, and then you rename the copies as the deleted setup-*modname*.exe's . It's done, and then you can just start the BiG World Install.bat ...
Understood?



#9 -Lighthouse-

-Lighthouse-
  • Guest

Posted 08 March 2010 - 04:46 PM

I do! Once I had a better understanding just exactly how WeiDu functions, I was able to install without any troubles at all. Took about 4 hours or so altogether, but there seem to be no issues nor crashes (2 hours in). I appreciate the time put into your answer.

It's good to be able to wallow right into BG again but with new, unexplored content.