Bardan the Slayer
Member Since 10 Jul 2002Offline Last Active May 17 2009 11:38 AM
Community Stats
- Group Member
- Active Posts 25
- Profile Views 3304
- Age 45 years old
- Birthday February 7, 1979
-
Gender
Not Telling
User Tools
Posts I've Made
In Topic: WeiDU 136 Problems
19 September 2003 - 11:23 AM
Just to add that little extra confirmation, it works fine on ME too (naturally).
In Topic: Potential trouble for auto-update
11 September 2003 - 04:08 PM
Sorry, I was a little imprecise.
Now, when you run a 136 Setup-Foozle, it doesn't execute the TP2. It gives only the lines of code I quoted above, and then stops, forcing a manual exit from DOS.
Also, when it is run, it seems to pick one of the 125 setups, and says as the title of the dos window that pops up that it is running *that* 125 exe (however, this is purely cosmetic - the named v125 setup never actually runs either). If you delete said v125 setup exe (Ascension in the above example), then it simply picks another v125, and does exactly the same thing.
Nothing else happens. It doesn't 'retrodate' everything to 125 (thankfully), but just stops dead in it's tracks.
Running one of the v125 Setups works just fine, as expected. No update occurs, but the TP2 executes, and no mention is made of an update.
EDIT : just to add, if I manually go to my BG2 folder form the DOS prompt and run a setup with the command >weidu setup-foozle.tp2, it uses v136, but no update occurs either. Now, I have no idea whether any update is meant to occur in this fashion, but I thought I would mention it. The problem seems to be purely with v136 Setup-Foozle.exe's
What I *will* do now is see if a v136 Setup-Foozle exe works for me in the absence of any other setups of an earlier version.
EDIT2 - In the absence of any earlier versions of Weidu, a v136 Setup-Foozle.exe works just fine. Throw even a single v125 Setup-Foozle.exe into the same folder, and it doesn't work, as described above.
Now, when you run a 136 Setup-Foozle, it doesn't execute the TP2. It gives only the lines of code I quoted above, and then stops, forcing a manual exit from DOS.
Also, when it is run, it seems to pick one of the 125 setups, and says as the title of the dos window that pops up that it is running *that* 125 exe (however, this is purely cosmetic - the named v125 setup never actually runs either). If you delete said v125 setup exe (Ascension in the above example), then it simply picks another v125, and does exactly the same thing.
Nothing else happens. It doesn't 'retrodate' everything to 125 (thankfully), but just stops dead in it's tracks.
Running one of the v125 Setups works just fine, as expected. No update occurs, but the TP2 executes, and no mention is made of an update.
EDIT : just to add, if I manually go to my BG2 folder form the DOS prompt and run a setup with the command >weidu setup-foozle.tp2, it uses v136, but no update occurs either. Now, I have no idea whether any update is meant to occur in this fashion, but I thought I would mention it. The problem seems to be purely with v136 Setup-Foozle.exe's
What I *will* do now is see if a v136 Setup-Foozle exe works for me in the absence of any other setups of an earlier version.
EDIT2 - In the absence of any earlier versions of Weidu, a v136 Setup-Foozle.exe works just fine. Throw even a single v125 Setup-Foozle.exe into the same folder, and it doesn't work, as described above.
In Topic: Potential trouble for auto-update
11 September 2003 - 03:48 PM
Nopey. Although I don't get any updating to old versions, now any mod that I try to install from the 136 exe simply states (in this case, I renamed 136 to Setup-Solaufein) :
[C:\Program Files\Black Isle\BG2 - SoA\Setup-Solaufein.exe} WeiDU version 136
(Setup-Ascension.exe) Queried (pid = 92) [WeiDU-Backup] WeiDU version 125
[./chitin.key] 179 BIFFs, 41639 resources
[./dialog.tlk] 76119 string entries
Also note that again, when running Solaufein, it states at the top of the DOS box that it is running Setup-Ascension.
Bummer.
Just in case it was something funky happening with Sola, I tried with another mod. no dice - same deal.
[C:\Program Files\Black Isle\BG2 - SoA\Setup-Solaufein.exe} WeiDU version 136
(Setup-Ascension.exe) Queried (pid = 92) [WeiDU-Backup] WeiDU version 125
[./chitin.key] 179 BIFFs, 41639 resources
[./dialog.tlk] 76119 string entries
Also note that again, when running Solaufein, it states at the top of the DOS box that it is running Setup-Ascension.
Bummer.
Just in case it was something funky happening with Sola, I tried with another mod. no dice - same deal.
In Topic: Potential trouble for auto-update
11 September 2003 - 11:07 AM
I'm getting the same problems as described above, on ME. Inexplicably, though I downloaded 136, renamed and ran, it somehow decided to update everything to 135
In Topic: WeiDU installation bug (v1.34)
08 September 2003 - 11:01 AM
135 works fine on my ME.
- Spellhold Studios
- → Viewing Profile: Posts: Bardan the Slayer
- Guidelines