|
Resiak Newbie
Joined: 17 Dec 2003 Posts: 2 Location: USA
|
Posted: Wed Sep 15, 2010 3:53 pm
'navy' is not a valid integer |
I rolled back to 2.37 from 3.22, and I've been getting this error message whenever I try to startup cmud. What can I do and how can I fix it? Cmud also ate two of my packages(or is simply not displaying their contents), and it's pretty depressing considering the number of hours I've put into them both. Can someone help me please?
|
|
_________________ There are two things a man should never be angry at. What he can help, and what he cannot.
-Japanese proverb |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Wed Sep 15, 2010 4:10 pm |
That error is a normal error when you go back to v2.37 after using the v3 Beta because the old version doesn't understand the color names used in the newer version. You need to delete the CMUD.INI and STYLES.INI files in your My Documents\My Games\CMUD directory to fix this. CMUD will automatically recreate those files with the default colors and preferences.
CMUD probably did not "eat" your packages. CMUD never deletes a package. The packages are probably just in a different directory than CMUD is looking for them in. Edit your sessions and check your full path locations to your package files.
Finally, it's always important to ALWAYS make backups of your important files. Not just for CMUD, but for anything. Hard disks *do* die and you were also playing with BETA software. Anything that you have put a large number of hours into should always be backed up. But CMUD also does create automatic backup copies of your package files, so look for files named *_bak.pkg in your session directory. |
|
|
|
Resiak Newbie
Joined: 17 Dec 2003 Posts: 2 Location: USA
|
Posted: Wed Sep 15, 2010 4:18 pm |
Thanks Zugg, that worked. I really appreciate it.
|
|
_________________ There are two things a man should never be angry at. What he can help, and what he cannot.
-Japanese proverb |
|
|
|
Tarn GURU
Joined: 10 Oct 2000 Posts: 873 Location: USA
|
Posted: Sun Sep 26, 2010 7:54 am |
Zugg wrote: |
That error is a normal error when you go back to v2.37 after using the v3 Beta because the old version doesn't understand the color names used in the newer version. |
Decloaking...
Another possible way of causing that (same root cause but not a deliberate version downgrade): The name of the executable has changed several times over the years. After quite a few updates and upgrades along the way, I have, in order of age, "cmud.exe", "cmudpro3.exe", and "cmudpro.exe" (that last apparently being the current one). A shortcut on my desktop was still pointing to one of the older executable names.
I could see that also being a problem for someone who buys an upgrade to pro at the same time as the update to 3.x. |
|
|
|
|
|