Demise: Rise of the Ku'tan: Demise patch 353

Demise patch 353

gold dragon
posted 05-28-2001 11:44 AM
Before installing patch 353 and the coresponding DLL file, I saved(by renaming) the Demise.exe file. After installing the 2 patches, I found that the build 319 exe file worked, but the 353 exe file Doesn't. What Am I doing wrong? I installed the r3.1 patch rebooted, renamed the demise.exe file, installed 353 patches, rebooted, but it wouldnt even start up the demise renderer(tho the renderer COULD work if started manually). even trying to run demise between installing 3.1 & 353 didn't work. When I saved the Renamed file, I saved it to a Different location, and only ran the exe from its normal location. I only had 1(one) demise.exe in the folder Artifact Entertainment tree.

Decklin
posted 05-28-2001 06:30 PM
This is tricky ... I posted elsewhere with the same question. Did you 'uncheck' auto backup in the game options section off the main menu when you originally installed? There are apparently security certificate files way deep in the resource sub folder that are written every time the game backs up. From the first install I unchecked autobackup because it backed up whenever you started the program - which means if you have corrupted files they are saved, overwriting good backups. In addition, if these are used for detecting hacking (indistinguishable from genuine attempts to rescue a problem situation) you are screwed. I do not think 'powering down' is a good idea - particularly if there's a risk of problem files being 'saved'. I prefer manual backups where I am "in control" ! I tried to write up a process of applying patches in my own site, and I had no problems of the kind you describe, but I am concerned that maybe this 'power up backup' may complicate things

I am guessing here ... but what was/is the setting in your game options menu?

Frostbite
posted 05-28-2001 09:54 PM
hiya gold dragon, same happened to me. The ding bug fix solved also this (and 2 other problems as well)

gold dragon
posted 05-29-2001 08:53 AM
I'm glad to hear that frostbite. I have the ding fix, but it DIDN'T work, so maybe I'm missing some other registry entry(ies)? I can check, and I have another program that will fix the entries that are wrong(Norton Util. Integrator) so that the fact that I installed Demise in a different location won't matter. I had the ding bug with the install of the r3.1 patch, I installed the ding fix & used the integrator to fix the entries, and it works like a charm! Now if I can get the 353 to work.....

gold dragon
posted 06-09-2001 08:19 PM
Working now, But I think I was running too much in the background. Thank you all for the help!