20 replies to this topic

[Rastor]

I'm uncertain whether this is a bug or an incompatibility with my system, but the old system of renaming WeiDU.exe to setup-MyMod.exe no longer works to create a mod installation program.

I'm running Windows 98SE, and I'm aware that WeiDU sometimes has problems with that OS, but it usually seems to work just fine.

Anyway, what happens is that whenever I run the renamed WeiDU setup program, I get the same results as if I had clicked on WeiDU.exe (ie, it runs the compiler, not the installer.)

[Kish]

Yes, I had this same exact problem just now. And to make sure that the .tp2 exists and all, I redownloaded the entire mod (Valen), unzipped it, and then replaced Setup-Valen.exe with a (properly renamed, of course) copy of WeiDU 134.

Windows 98.

[Jessayla]

Bleah. My computer won't run XP/2000 properly and still let me run any of my games. Damned ancient system. Ah well.

[Bardan the Slayer]

Yep, just to be the first ME voice to post here, I'm getting exactly the same thing.

[weimer]

OK, here's the plan -- I don't have Win 98 / ME, so I can't test things out.

I am putting a new beta version of WeiDU up at

http://www.cs.berkel...u/~weimer/test/

Actually, there will be two versions there (so that you can run experiments and see if the update happens correctly). The versions include copious debug info and I need people out there to try it and copy it back to me verbatim.

Here are the steps:

(1) Download files.
(2) Do whatever is necessary to make sure that 135-2 is NEWER.
(3) Run Setup-WeiDU-135-1 and verify that it works (copy output to me here).
(4) Download files again (or restore from backup copies or whatever).
(5) Make sure 135-2 is NEWER.
(6) Run Setup-WeiDU-135-2 and verify that it works (copy output to me here).

For me, part (3) is:

tani-no-yuri:/cygdrive/c/src/weidu$ ./Setup-WeiDU-135-1.exe 
[c:\src\weidu\Setup-WeiDU-135-1.exe] WeiDU version 135-BETA-1
WeiDU files in date order:
        Setup-WeiDU-135-2.exe
        Setup-WeiDU-135-1.exe
Newest WeiDU is [Setup-WeiDU-135-2.exe], updating!
Unlinking [WeiDU-Backup.exe]: false
Unlinking [c:\src\weidu\Setup-WeiDU-135-1.exe]: false
Unlinking [Setup-WeiDU-135-1.exe]: false
Renaming [c:\src\weidu\Setup-WeiDU-135-1.exe] -> [WeiDU-Backup.exe]: true
Renaming [Setup-WeiDU-135-1.exe] -> [WeiDU-Backup.exe]: false
        Unlinking [Setup-WeiDU-135-2.exe]: true
        Copying [Setup-WeiDU-135-2.exe] -> [Setup-WeiDU-135-2.exe]
        Unlinking [Setup-WeiDU-135-1.exe]: false
        Copying [Setup-WeiDU-135-2.exe] -> [Setup-WeiDU-135-1.exe]
Rerunning [Setup-WeiDU-135-1.exe] ...
[Setup-WeiDU-135-1.exe] WeiDU version 135-BETA-2
WeiDU files in date order:
        Setup-WeiDU-135-2.exe
        Setup-WeiDU-135-1.exe


** ERROR ** [SETUP-WEIDU-135-1.TP2] not found.

This is the expected behavior (note that it eventually becomes 135-BETA-2 and then complains that the TP2 file is not found).

Here's the code for my run of the other experiment:

tani-no-yuri:/cygdrive/c/src/weidu$ ./Setup-WeiDU-135-2.exe 
[c:\src\weidu\Setup-WeiDU-135-2.exe] WeiDU version 135-BETA-2
WeiDU files in date order:
        Setup-WeiDU-135-2.exe
        Setup-WeiDU-135-1.exe
Newest WeiDU is [Setup-WeiDU-135-2.exe], updating!
Unlinking [WeiDU-Backup.exe]: true
Unlinking [c:\src\weidu\Setup-WeiDU-135-2.exe]: false
Unlinking [Setup-WeiDU-135-2.exe]: false
Renaming [c:\src\weidu\Setup-WeiDU-135-2.exe] -> [WeiDU-Backup.exe]: true
Renaming [Setup-WeiDU-135-2.exe] -> [WeiDU-Backup.exe]: false
        Unlinking [Setup-WeiDU-135-2.exe]: false
        Copying [Setup-WeiDU-135-2.exe] -> [Setup-WeiDU-135-2.exe]
        Unlinking [Setup-WeiDU-135-1.exe]: true
        Copying [Setup-WeiDU-135-2.exe] -> [Setup-WeiDU-135-1.exe]
Rerunning [Setup-WeiDU-135-2.exe] ...
[Setup-WeiDU-135-2.exe] WeiDU version 135-BETA-2
WeiDU files in date order:
        Setup-WeiDU-135-2.exe
        Setup-WeiDU-135-1.exe


** ERROR ** [SETUP-WEIDU-135-2.TP2] not found.

Here we see it updating 135-1 with itself, and a quick check off to the side verifies that 135-1 is now really 135-2.

Anyway, I would appreciate it if someone with 98/ME would try this.

[Kish]

Whenever I go there and click on either link, I get, "Sorry, Access Denied." Apparently they can only be downloaded by members of the EECS department...or at least trying to click on either link leads to something only members of the EECS department can do.

[weimer]

Try again, let me know.

[weimer]

Grr, this is one of those times when Windows vastly annoys me (the problem here has to do with their poor choice for how to deal with the file associated with an open process). Boy do I wish we were all just using unix.

OK, if Kish is feeling generous let's play this game again with 135-3 and 135-4. Note that this time the logs may not be as helpful since WeiDU-Old will actually spawn a copy of WeiDU-other in order to have Other update Old.

[weimer]

Kish, did it actually work? I mentioned that the logs would be unrevealing and they seem to be -- what did you see on the screen? Did it actually update everything correctly in both cases?

[Kish]

Sorry, my technical ignorance rears its head again, I didn't realize that wouldn't tell you what you needed to know. It appears, from installing and uninstalling Valen, that it worked. Her Setup program certainly uses Weidu 135-4 and encountered no problems.

[weimer]

Thanks, Kish. I'll assume that it's working -- v135 is available now. Let me know if problems persist.

[Rastor]

You assume correctly. Version 1.35 does indeed work properly on Windows 98SE. I can't confirm for sure other Windows variants, but I strongly suspect that the same is true of them.