Error on Update

[rootbear75]

got an error on updating...

 

Error 5

 

dont know why

 

Today's Entry in DCME.log

3/8/2008 3:39:57 AM --- Drake Continuum Map Editor (v3.1.16) @ C:\Program Files\Continuum\DCME\DCME starting...
67798 +++ OtherInstance 0
67798 +++ Settings loaded
frmMain loading
Un!@#$%^&*led 1 @ NewMap, path = '' usingDefaultTileset True
Un!@#$%^&*led 1 @ NewMap, DefaultWalltiles = 
Un!@#$%^&*led 1 @ NewMap, DefaultTileset = 
Un!@#$%^&*led 1 @ InitTileset, tilesetpath= Default usingDefaultTileset True
+++ Skipped check for updates
3/8/2008 3:39:58 AM --- DCME ready
+++ Searching for updates at [url="http://www.dcme.sscentral.com/autoupdate/dcmeupdate.txt"]http://www.dcme.sscentral.com/autoupdate/dcmeupdate.txt[/url]...
+++ Latest version available: 3.2.1 (Current version: 3.1.16)
+++ Downloading from [url="http://dcme.sscentral.com/autoupdate/dcmeupdate3201.exe"]http://dcme.sscentral.com/autoupdate/dcmeupdate3201.exe[/url] to C:\Program Files\Continuum\DCME\DCMEupdate.exe
+++ Update files successfully downloaded.
+++ Closing map Un!@#$%^&*led 1 (ID: 0)
frmMain(0) unloaded
+++ Updating with C:\Program Files\Continuum\DCME\DCMEupdate.exe
*** Error 5 (Invalid procedure call or argument) in frmGeneral.QueryUnload (update)
DCME ended successfully

Edited March 8, 2008 by rootbear75

[Samapico]

I read that Vista didn't allow renaming .dll's... could it also not allow to rename .exe files?

[rootbear75]

i !@#$%^&*ing hate vista

 

well, it updated....

had a file called DCMEbackup.exe...

 

that file is now DCME w/o me changing it

[Samapico]

Not really...

 

But yeah, it was updated correctly.

 

What the update does:

 

DCMEupdate.exe is downloaded. DCMEupdate.exe is a self-extracting archive containing the new DCME.exe.

Since DCME is still running, it renames the current DCME.exe to dcmebackup.exe <-- It's that part that didn't work

Now that dcme is renamed, it executes the self-extracting archive, which unpacks DCME.exe and starts it.

Meanwhile, the old DCME was shut down.

 

 

The renaming probably didn't work because the exe was running, now that I think about it... on XP and before it works fine though.

 

So what happened after... I'm guessing you double-clicked on DCMEupdate.exe, which unpacked the new DCME.exe and started it.