Zugg Software :: View topic

Newbie Joined: 17 Mar 2009 Posts: 4

Hi!

I have a little problem with package file..
I was 'cleaning' my package - moving triggers to separated classes etc. When I was moving one trigger, I've dropped it on another trigger and expirienced a crash of Cmud.
I shut it down and when I rerun it, the problem appeared. The package works fine - I have all of my settings working in Mud but... I cannot see my Package in Editor! - If I run the editor, its window is blank, there is no buttons, no text, no folders - nothing. Sometimes the error appears and says: "Cannot focus a disabled or invisible window"
Can anyone help me with getting my package back?
Reinstalling of Cmud doesn't work (I suppose that I don't need to tell that rerunning program/OS etc doesn't work too). It might be some error with the package, but I don't have any other package to check if it works or not so I cannot be sure...

Posted: Sat Apr 04, 2009 10:24 pm

sounds like a corrupted package... export to xml make a new package and import it. or use the xml to start from scratch

Newbie Joined: 17 Mar 2009 Posts: 4

Thanks for help but it wasn't it.
I reinstalled cMud several times and it didn't work but the last time I cleaned up disks from every info connected with cMud and reinstalled once again - it works fine now. So it was a problem with program, not with a package...
Thanks anyway. ;)

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

I'll speak up on this. Just because reinstalling the program made it work, doesn't mean the problem was with the program. Especially if you try it once and it doesn't work, as you noted you did. Typically in those situations, whatever action took place caused the problem, and in the process it also corrupted the interface from the program(CMUD) to the process(package) being manipulated. As you also noted, it was after you cleaned up the connection info between the OS and CMUD that the problem was resolved. That was where the problem was. Now, what caused the bad interface in the first place is hard to tell, though if it was a normal CMUD crash I hope you submitted the crash report. If it was a windows crash of the program, then the problem was with nothing in the program itself.

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

After I get a huge error like that I run Scan Disk in windows Explorer C: disk > Properties > Tools > Check Now. I choose automatically fix file system errors.

I think when programs don't exit they may leave behind confusing bits of information. Probably you use this but as you re-installed the whole program before, I thought to share. It will make guesses what is good data to keep and can randomly make mistakes, but it's effective.