Author Topic: Updated  (Read 1288 times)

canel@tiscali.co.za

  • Traveller
  • *
  • Posts: 14
    • View Profile
Updated
« on: September 17, 2005, 05:21:39 pm »
Every time after i updated and try to luanch, it says something about a regestry error or something.Does any1 know wats wrong?

Seytra

  • Forum Addict
  • *
  • Posts: 2052
  • No system can compensate lack of common sense.
    • View Profile
(No subject)
« Reply #1 on: September 17, 2005, 11:14:47 pm »
Most important thing about asking about errors: copy down the exact error.
In your case, I assume this is not an Registry error but an exception error, most likely one with an address ending in 161. This is what I call \"chain crash error\", because it tends to come up after a previous crash.
The solution is to 1) disable sound (this will reduce likeliness of crashes in general) and to then persistently retry. It\'ll eventually not get the error if it\'s the one I assume it to be.

canel@tiscali.co.za

  • Traveller
  • *
  • Posts: 14
    • View Profile
(No subject)
« Reply #2 on: September 17, 2005, 11:40:48 pm »
I will run a update through the night and post the full message tomorrow. THank you. :)



EDIT:
Ok, it says the following:

ERROR: csInitializer::SetupConfigManager failed!
Is your CRYSTAL environment variable set?
Exiting Planeshift. Press Enter...
« Last Edit: September 18, 2005, 11:26:41 am by canel@tiscali.co.za »

Seytra

  • Forum Addict
  • *
  • Posts: 2052
  • No system can compensate lack of common sense.
    • View Profile
(No subject)
« Reply #3 on: September 18, 2005, 09:56:40 pm »
Hmm, this error is certainly not one of the common ones. At least I have no idea about it.
So you said it happened only after you updated? Does that mean that it was working before, or that you didn\'t try?
It is possible, though AFAICS unlikely, that the setup program or a configuation file was corrupted while being downloaded by the updater.

MY next step would be to move the setup program (pssetup.exe) and all configuration files (everything ending in \".cfg\" and \".xml\") into another folder, and re-run the updater (even though that will take ages right now, due to the performance problem). That should give you working versions of the files if they indeed were damaged somehow.

Another option would be to reinstall PS to a clean folder, and not update, since the .11 version still is usable, though it lacks some fixes for annoying bugs.
If you dare, you can start manually copying files from the updated version to the unupdated version and see which file causes the trouble.

canel@tiscali.co.za

  • Traveller
  • *
  • Posts: 14
    • View Profile
(No subject)
« Reply #4 on: September 25, 2005, 12:23:09 pm »
Thanks will look into that
;)