Okay... WeiDU 135 (Setup-KelseyTOB.exe) thought that Setup-NPCFlirt.exe (WeiDU 134) was newer than it was because Setup-NPCFlirt.exe had been adjusted more recently by being updated TO WeiDU 134 more recently than WeiDU 135 was released.
Now, I can solve this problem by obtaining a touch-like tool, but unfortunately the bigger problem here would seem to be that a mod user who has a lesser WeiDU update occur at any time between the release of that mod and the time of install is going to be "stuck" with an earlier version of WeiDU.
Potential trouble for auto-update
Started by
-jcompton-
, Sep 08 2003 02:10 PM
20 replies to this topic
#2
-jcompton-
-jcompton-
-
- Guest
Posted 08 September 2003 - 02:17 PM
More Auto-Update Badness:
To amuse myself I re-copied Setup-KelseyTOB.exe (WeiDU 135) from my development drawer into the BG2 dir, overwriting Setup-KelseyTOB.exe (WeiDU 134.)
This was the result. As you can see, WeiDU 135 is still replacing itself with WeiDU 134, it's doing so twice, and now it's running the wrong TP2 to boot.
[D:\games\bg2\Setup-KelseyTOB.exe] WeiDU version 135
Newest WeiDU is [Setup-GBThfKp.exe], updating!
Copying [Setup-GBThfKp.exe] -> [Setup-GBThfKp.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-FWKetoDEV.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-ElvenResizer.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Ascension.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-oasis.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-NPCFlirt.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-natlia.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-LMA.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-KelseyOPC.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Kelsey104.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Kelsey.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-katiemod.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-josh.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-ItemUpgrade.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-IronGhrey.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-IronCuv.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-ict.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-GRoA.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Valen.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Tactics.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-StJo2.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-StJo.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Solaufein.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-simebanters.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-replacetriggerlehtin.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Player1Test.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Oversight.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-lilith.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-KizIM.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-KelseyLoopKill.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Ease.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-DungeonBeGone.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-CWS.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-circle.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-bantergoose.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-AshesofEmbers.exe]: true
[Setup-GBThfKp.exe] WeiDU version 134
Newest WeiDU is [Setup-AshesofEmbers.exe], updating!
[Setup-AshesofEmbers.exe] -> [Setup-AshesofEmbers.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Oversight.exe]
[Setup-AshesofEmbers.exe] -> [setup-lilith.exe]
[Setup-AshesofEmbers.exe] -> [Setup-KizIM.exe]
[Setup-AshesofEmbers.exe] -> [Setup-KelseyLoopKill.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Ease.exe]
[Setup-AshesofEmbers.exe] -> [Setup-DungeonBeGone.exe]
[Setup-AshesofEmbers.exe] -> [Setup-CWS.exe]
[Setup-AshesofEmbers.exe] -> [setup-circle.exe]
[Setup-AshesofEmbers.exe] -> [setup-bantergoose.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Valen.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Tactics.exe]
[Setup-AshesofEmbers.exe] -> [Setup-StJo2.exe]
[Setup-AshesofEmbers.exe] -> [Setup-StJo.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Solaufein.exe]
[Setup-AshesofEmbers.exe] -> [setup-simebanters.exe]
[Setup-AshesofEmbers.exe] -> [setup-replacetriggerlehtin.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Player1Test.exe]
[Setup-AshesofEmbers.exe] -> [Setup-GRoA.exe]
[Setup-AshesofEmbers.exe] -> [Setup-KelseyOPC.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Kelsey104.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Kelsey.exe]
[Setup-AshesofEmbers.exe] -> [Setup-katiemod.exe]
[Setup-AshesofEmbers.exe] -> [Setup-josh.exe]
[Setup-AshesofEmbers.exe] -> [Setup-ItemUpgrade.exe]
[Setup-AshesofEmbers.exe] -> [Setup-IronGhrey.exe]
[Setup-AshesofEmbers.exe] -> [setup-IronCuv.exe]
[Setup-AshesofEmbers.exe] -> [setup-ict.exe]
[Setup-AshesofEmbers.exe] -> [setup-oasis.exe]
[Setup-AshesofEmbers.exe] -> [Setup-NPCFlirt.exe]
[Setup-AshesofEmbers.exe] -> [setup-natlia.exe]
[Setup-AshesofEmbers.exe] -> [Setup-LMA.exe]
[Setup-AshesofEmbers.exe] -> [Setup-GBThfKp.exe]
[Setup-AshesofEmbers.exe] -> [Setup-FWKetoDEV.exe]
[Setup-AshesofEmbers.exe] -> [Setup-ElvenResizer.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Ascension.exe]
[Setup-AshesofEmbers.exe] -> [Setup-KelseyTOB.exe]
Rerunning [Setup-GBThfKp.exe] ...
[Setup-GBThfKp.exe] WeiDU version 134
Using Language [American English]
Install Component [Expanded Thief Stronghold]
[Y]es or [N]o or [Q]uit?
To amuse myself I re-copied Setup-KelseyTOB.exe (WeiDU 135) from my development drawer into the BG2 dir, overwriting Setup-KelseyTOB.exe (WeiDU 134.)
This was the result. As you can see, WeiDU 135 is still replacing itself with WeiDU 134, it's doing so twice, and now it's running the wrong TP2 to boot.
[D:\games\bg2\Setup-KelseyTOB.exe] WeiDU version 135
Newest WeiDU is [Setup-GBThfKp.exe], updating!
Copying [Setup-GBThfKp.exe] -> [Setup-GBThfKp.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-FWKetoDEV.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-ElvenResizer.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Ascension.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-oasis.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-NPCFlirt.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-natlia.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-LMA.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-KelseyOPC.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Kelsey104.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Kelsey.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-katiemod.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-josh.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-ItemUpgrade.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-IronGhrey.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-IronCuv.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-ict.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-GRoA.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Valen.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Tactics.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-StJo2.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-StJo.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Solaufein.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-simebanters.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-replacetriggerlehtin.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Player1Test.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Oversight.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-lilith.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-KizIM.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-KelseyLoopKill.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-Ease.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-DungeonBeGone.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-CWS.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-circle.exe]: true
Copying [Setup-GBThfKp.exe] -> [setup-bantergoose.exe]: true
Copying [Setup-GBThfKp.exe] -> [Setup-AshesofEmbers.exe]: true
[Setup-GBThfKp.exe] WeiDU version 134
Newest WeiDU is [Setup-AshesofEmbers.exe], updating!
[Setup-AshesofEmbers.exe] -> [Setup-AshesofEmbers.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Oversight.exe]
[Setup-AshesofEmbers.exe] -> [setup-lilith.exe]
[Setup-AshesofEmbers.exe] -> [Setup-KizIM.exe]
[Setup-AshesofEmbers.exe] -> [Setup-KelseyLoopKill.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Ease.exe]
[Setup-AshesofEmbers.exe] -> [Setup-DungeonBeGone.exe]
[Setup-AshesofEmbers.exe] -> [Setup-CWS.exe]
[Setup-AshesofEmbers.exe] -> [setup-circle.exe]
[Setup-AshesofEmbers.exe] -> [setup-bantergoose.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Valen.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Tactics.exe]
[Setup-AshesofEmbers.exe] -> [Setup-StJo2.exe]
[Setup-AshesofEmbers.exe] -> [Setup-StJo.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Solaufein.exe]
[Setup-AshesofEmbers.exe] -> [setup-simebanters.exe]
[Setup-AshesofEmbers.exe] -> [setup-replacetriggerlehtin.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Player1Test.exe]
[Setup-AshesofEmbers.exe] -> [Setup-GRoA.exe]
[Setup-AshesofEmbers.exe] -> [Setup-KelseyOPC.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Kelsey104.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Kelsey.exe]
[Setup-AshesofEmbers.exe] -> [Setup-katiemod.exe]
[Setup-AshesofEmbers.exe] -> [Setup-josh.exe]
[Setup-AshesofEmbers.exe] -> [Setup-ItemUpgrade.exe]
[Setup-AshesofEmbers.exe] -> [Setup-IronGhrey.exe]
[Setup-AshesofEmbers.exe] -> [setup-IronCuv.exe]
[Setup-AshesofEmbers.exe] -> [setup-ict.exe]
[Setup-AshesofEmbers.exe] -> [setup-oasis.exe]
[Setup-AshesofEmbers.exe] -> [Setup-NPCFlirt.exe]
[Setup-AshesofEmbers.exe] -> [setup-natlia.exe]
[Setup-AshesofEmbers.exe] -> [Setup-LMA.exe]
[Setup-AshesofEmbers.exe] -> [Setup-GBThfKp.exe]
[Setup-AshesofEmbers.exe] -> [Setup-FWKetoDEV.exe]
[Setup-AshesofEmbers.exe] -> [Setup-ElvenResizer.exe]
[Setup-AshesofEmbers.exe] -> [Setup-Ascension.exe]
[Setup-AshesofEmbers.exe] -> [Setup-KelseyTOB.exe]
Rerunning [Setup-GBThfKp.exe] ...
[Setup-GBThfKp.exe] WeiDU version 134
Using Language [American English]
Install Component [Expanded Thief Stronghold]
[Y]es or [N]o or [Q]uit?
#4
-jcompton-
-jcompton-
-
- Guest
Posted 08 September 2003 - 03:39 PM
Wes, is there a reason you can't just create a 16-bit version number at some predictable offset and key auto-update off THAT instead? It would seem to be a bit more bulletproof, no?
#5
hlidskialf
-
- Modder
-
- 2510 posts
Incarnation of the Eternal Ale Warrior
Posted 08 September 2003 - 04:31 PM
I had this exact bug come up running Windows XP.
The great wolf Fenrir gapes ever at the dwelling of the gods.
#6
Rastor
-
- Member
- 2001 posts
Yes, I really am a dragon. Yes, I am a jerk. Live with it.
Posted 08 September 2003 - 05:33 PM
This is great.
WeiDU 1.35 works fine on Windows 98SE, but now it doesn't work on 2k and XP?
Why bother using the newer log entries anyway? Wouldn't it be better to do things the old way?
WeiDU 1.35 works fine on Windows 98SE, but now it doesn't work on 2k and XP?
Why bother using the newer log entries anyway? Wouldn't it be better to do things the old way?
Home of Kitanya, Improved Asylum, more...
#7
weimer
-
- Member
- 1569 posts
Posted 08 September 2003 - 06:44 PM
Good point, Jason. I must admit, you're much better at imagining an "adversarial" user than I am.
Known Offset: not possible, by default we compress weidu.exe.
However, I'll just query WeiDU and have it report its version number.
Rastor: thus bug will afflict all WeiDU plaftorms. We don't have the new log entries -- these concerns are orthogonal.
Known Offset: not possible, by default we compress weidu.exe.
However, I'll just query WeiDU and have it report its version number.
Rastor: thus bug will afflict all WeiDU plaftorms. We don't have the new log entries -- these concerns are orthogonal.
#8
-jcompton-
-jcompton-
-
- Guest
Posted 08 September 2003 - 06:48 PM
While I'll take that as a compliment, this wasn't done with deliberate QA/malicious intent... it's just how things happened to work out when I was testing the Kelsey-TOB fixup.Good point, Jason. I must admit, you're much better at imagining an "adversarial" user than I am.
Known Offset: not possible, by default we compress weidu.exe.
I feared as much.
#9
weimer
-
- Member
- 1569 posts
Posted 08 September 2003 - 08:24 PM
OK, v136 is out and claims to fix these problems. It uses WeiDU's internal version numbers.
Please check it out under 98/me and 2k/xp.
Please check it out under 98/me and 2k/xp.
#10
hlidskialf
-
- Modder
-
- 2510 posts
Incarnation of the Eternal Ale Warrior
Posted 09 September 2003 - 12:42 PM
Worked fine and as it should! Thankee Wes. 
The great wolf Fenrir gapes ever at the dwelling of the gods.
#11
Hesperus
-
- Member
- 18 posts
Posted 09 September 2003 - 12:57 PM
Novice here (who is a BIG fan of Solaufein, tactics, spell-50, ascension)... just where do I get version 136? I have 134 on all my mods, but am having some trouble installing the Chloe patch and thought 136 might help (as I've had no luck yet from the current advice over at the Chloe site). Thanks in advance.
#13
-jcompton-
-jcompton-
-
- Guest
Posted 09 September 2003 - 03:34 PM
I released Kelsey-TOB v2.1 with 136, so hopefully it works. 
#14
Grim Squeaker
-
- Member
- 1018 posts
Fallen
Posted 10 September 2003 - 02:20 AM
'Weimer we have a problem...'
I am running Windows 98SE. I downloaded WeiDU 136. Copied WeiDU.exe and renamed it Setup-Harvey.exe and stuck it in my BG2-SoA directory. I then ran it:
[D:\C Drive Extended\Program Files\Black Isle\BG2 - SoA\Setup-Harvey.exe} WeiDU version 136
(Setup-Solaufein.exe) Queried (pid = 76) [WeiDU-Backup] WeiDU version 135
[./chiten.key] 182 BIFFs, 41793 resources
[./dialog.tlk] 93090 string entries
It now does absolute nothing and I have no options available. I have to close it manually. Also the DOS box is labelled Setup-Solaufein as opposed to Setup-Harvey.
Eeb...
Edit: If I then after manually closing that box run another Setup-Foozle.exe (in this case Seup-Kelsey.exe) then it actually updates the version and ends with the: 'Now rerun Setup-Kelsey.exe. Sorry I can't do it for you. Windows won't let me' message. Any Setup-Foozle.exe I run after this is now running with v136.
Wierd...
I am running Windows 98SE. I downloaded WeiDU 136. Copied WeiDU.exe and renamed it Setup-Harvey.exe and stuck it in my BG2-SoA directory. I then ran it:
[D:\C Drive Extended\Program Files\Black Isle\BG2 - SoA\Setup-Harvey.exe} WeiDU version 136
(Setup-Solaufein.exe) Queried (pid = 76) [WeiDU-Backup] WeiDU version 135
[./chiten.key] 182 BIFFs, 41793 resources
[./dialog.tlk] 93090 string entries
It now does absolute nothing and I have no options available. I have to close it manually. Also the DOS box is labelled Setup-Solaufein as opposed to Setup-Harvey.
Eeb...
Edit: If I then after manually closing that box run another Setup-Foozle.exe (in this case Seup-Kelsey.exe) then it actually updates the version and ends with the: 'Now rerun Setup-Kelsey.exe. Sorry I can't do it for you. Windows won't let me' message. Any Setup-Foozle.exe I run after this is now running with v136.
Wierd...
"You alone can make my song take flight..."
#15
Bardan the Slayer
-
- Member
- 25 posts
Posted 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 
#16
weimer
-
- Member
- 1569 posts
Posted 11 September 2003 - 12:00 PM
Grim, Bardan - if you guys had versions like 134 or 135 lying around, it's possible that 136 won't work with them (they had problems, as noticed earlier).
Try this little test:
Download WeiDU-125 from the website ( http://weidu.org/old/ ) and copy that EXE over all of the Setup-*.exe files in your BG2 directory. Then download the newest version (136) and copy it over Setup-Harvey.exe (or whatever) and run that. Let me know if it works.
Try this little test:
Download WeiDU-125 from the website ( http://weidu.org/old/ ) and copy that EXE over all of the Setup-*.exe files in your BG2 directory. Then download the newest version (136) and copy it over Setup-Harvey.exe (or whatever) and run that. Let me know if it works.
#17
Bardan the Slayer
-
- Member
- 25 posts
Posted 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.
#18
-jcompton-
-jcompton-
-
- Guest
Posted 11 September 2003 - 04:00 PM
...so what are you saying it does now? Updates everything to 125? Or doesn't execute the TP2?
#19
Bardan the Slayer
-
- Member
- 25 posts
Posted 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.
Edited by Bardan the Slayer, 11 September 2003 - 04:26 PM.
