21 replies to this topic

[Jarno Mikkola]

One of your setup-*modname*.exe's that are actually the WeiDU.exe just renamed, has not been updated, and so it will not run the code lines that are given to it because they were not there yet, so you have to manually update the setup-*modname*.exe's to be the latest versions... read here about the WeiDU.exe... The first answer.

[Jarno Mikkola]

Much appreciated. Everything is updated now (at least, all of the setup-*modname*.exe files are now 605kb). But I'm not sure what needs to be done after that. I tried running the vbs file again, and I got back to the same point again.

The BiG World Setup.vbs restarts the extraction process, so that's a no-no if you have everything already exacted but nothing installed... What you should do is first of all have a clean setup(so you probably need to start it )... but when then BiG World Install.bat starts(I assume you don't use the BWS beta), the black window opens and begins to ask a few questions, you should close it before the "Let the madness begin" finishes and it begins to install stuff, (update the setup-*modname*.exe's)start one of the setup-*modname*.exe's and not install a thing, then update the rest of the setup-*modname*.exe's like you did, and then run the BiG World Install.bat, answer the questions and then let it run.

Edited by Jarno Mikkola, 24 June 2010 - 05:28 PM.

[Jarno Mikkola]

This is the error message I'm getting. So if I understand you correctly, what I need to do is a fresh install, wait until the command prompt gets to the "let the madness begin" is on the screen, close the window before I start it, open one of the "setup-*modname*.exe" files, allow it to update all of them, and then run it again? Or do I need to open each individual "setup-*modname*.exe" file?

Where exactly is the BiG World Install.bat? Cause that would seem to be in totally off...

[dabus]

Why bother, just edit the batch-file and we'll try to track down the error with another batch-file later...

Uh, sorry about that, I just thought about it and there is something fishy about that picture. The batch includes a few lines before the update:

%IFE.%     All Setup-x.exe get updated with the recent WeiDU.exe, now.
%IFE.%     This may take some time. Please be patient! 
%IFG.%     Alle Setup-x.exe werden nun auf die neue WeiDU.exe geupdated.
%IFG.%     Dies kann etwas dauern. Bitte seid geduldig!
%IFH.%     Todo Setup-x.exe se actualiza con los ultimos WeiDU.exe, ahora.
%IFH.%     Esto puede tomar algun tiempo. Por favor se paciente!

So the batch did not reach the replacement-part before exiting out, otherwise you should have seen the first two lines in the posted picture.

I guess it could come from these lines, but there's an if-statement:

%IF% ".\override\override" move ".\override\override\*.*" ".\override" | %M%
%IF% ".\override\override" rmdir /s /q ".\override\override" | %M%

To solve what's going on:
remove every line between 118 (:: Every choice-key may be used only one single time.) and 2878 (:BWSStart).
->This way you will not have to do the same choices all over again.
Then add a @echo on before the :BWSStart.
->This will show each line that is executed, so it will also show us the problamatic one.
Start a cmd and go to your installation-folder. Execute the batch.
->This will avoid the closing of the cmd-window after the batch exited.
Copy & paste the output.

Edited by dabus, 25 June 2010 - 01:45 PM.

[dabus]

Muah -- I think something messed with your path-variable...
Go and search how to reset your windows vista or 7 back to defaults or add another path. Maybe ]this fits.
The path for xcopy is C:\WINDOWS\system32...

[dabus]

Most people install under c:, but in your case you'll use h:.
There are no absolute paths in the batch.
The batch needs some basic commands like cmd, findstr and internal commands like dir.
Other programs might also fail if these are missing. So you better get that fixed before you try to go on.

[Setharnas]

Just to get some more info, could you please
- open a cmd window (hope that's the same on vista)
- type "set" (without quotes) and enter
- post the results, no matter if by screenshot or copypasted
? That should give a clue if your OS installation is actually being weird or not.

[Setharnas]

ComSpec=H:\Windows\system32\cmd.exe
Path=H:\Windows\system32;H:\Windows;H:\Windows\System32\Wbem;H:\Windows\System32\WindowsPowerShell\v1.0\;H:\Program Files\Common Files\DivX Shared\;H:\Program Files\QuickTime\QTSystem\
SystemDrive=H:
SystemRoot=H:\Windows
windir=H:\Windows

Hope this is what you need.

It is indeed, and it shows at least your environment is ok. Windows setup has always had a habit of making facepalm inducing decisions for drive letters when there were other drives present. Unfortunately, that doesn't explain why it chokes on a standard call to xcopy...

Can you please just do a search for xcopy.exe, findstr.exe (and what else, dabus?) and see if they exist anywhere on your system?

[dabus]

Ok, I think there was a misunderstanding:
I thought your PATH-variable was broken so you asked if you should use still use C: when Windows 7 is installed to your H: drive.

So I answered that you in your case should use H:.

There was no need to install the game on another partition to get it working.
The system just does not know where to search for standard-commands that lay somewhere in the paths that are specified in the PATH-variable. So that's pretty funny (and ugly in your case).

Anyway.

Select to open an cmd-window and see if you can execute xcopy and get some result like "need some more parameters, 0 files copied".

If that does not work, try to do a SET PATH=H:\WINDOWS;H:\Windows\system32 or SET PATH=C:\WINDOWS;C:\Windows\system32 and try to run that command again. If it does work, you should be able to to a cd /D C:\Games\BGII - SoA and start the BiG World Install.bat (or wherever you put that game -- beware, the folder may grow a lot (up to 25 GB in worst case).

By the way, I don't know if adding C:\windows... and so on to your path would hurt your system.

The edited SET-Path is only used in your current cmd-window. If you open a new one, you will get the old setting.
(If you don't, you have an online-backup )

@Setharnas: Sorry, I don't know exactly what's used in the batches.
Yes, you can try to copy something into you BG2-folder and see if it's working, but you still will be having troubles running a lot of standard-batches that may be used to use any of those standard-commands.

I also guess that someone uses other things then batches to script things, but if one does -- bad luck again.

Edited by dabus, 26 June 2010 - 06:43 PM.

[Setharnas]

@dabus:
I was more thinking of whether or not he could copy some misplaced command exes back into system32. And you're right about the "other things to script things" - I've been wondering if that Windows Power Shell did some funky things when it was installed, but I can't really imagine that.

[Setharnas]

Probably not. I'm more confused over the (apparent) fact that there haven't been more reports based on this little stunt - Win7 isn't that new anymore, and I'm sure other BWP users must have it... Question is, now, if it's (legally, specifically) possible to include those files in the BWP installer distribution's utilities folder.