Zugg Software :: View topic

Posted: Tue Jan 19, 2016 8:02 pm

Recent development I have had. I am going to assume it's just corrupted settings, but I thought i would throw it out here.
When I right click on a setting in the settings editor, as if to disable it, CMUD locks up on me entirely.
I end up having to kill it with Task Manager.

Lets see if I remember how to do this properly.

Hmm, it is doing the same when i try to access the menu bar to export my settings to XML.
Yet it's only doing it when i have a session loaded, any session, online or off.
If I just hit escape and run with no package, things are fine.
My sessions have no shared packages other than the default packages.

Posted: Tue Jan 19, 2016 8:08 pm

Is there a command to export to XML from the command line?

Apprentice Joined: 17 May 2005 Posts: 108

It's probably pretty safe to say you've already tried everything I would have tried to fix the issue, so I only have one off-the-wall suggestion.

Open the sessions offline, start a log, then use the commands #TRIGGER, #ALIAS, #VARIABLE, etc.

Then delete the packages, layouts, and, you know, everything. Then reinstall CMUD and write a script to convert the contents of the log files into the triggers and aliases and so forth that you had before, or, ideally, into a corresponding xml file.

It's far from ideal, but... it's something.

Sounds like it has to be something in CMUD itself is corrupted, or maybe sessions.db/sessionkeys.db (if only because they are relevant to every session. I really hate having to recreate those...). Odd that a reinstall and/or recreation of those DBs doesn't fix the issue though.

Posted: Wed Jan 20, 2016 3:13 pm

I don't think it is CMUD itself, I uninstalled and reinstalled and the issue persists.
Though it only seems to still affect my main session

Apprentice Joined: 17 May 2005 Posts: 108

Yeah I assumed you had done all the basic stuff.

That's a particularly unfortunate problem to have, seems like most of the troubleshooting I do begins with "export to xml."

You have a "<session>_bak.pkg" file you can switch to to see if it fixes the problem? Or old xml backups?

On a side note, I've never figured out what prompts the creation of a backup package, so I make them myself now. Faster than re-importing and all that.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

I am going to guess that a package file got damaged or corrupted in some way. The package files are SQLLite databases, so you can use a different program to view and extract information from the package. You might use CMud to save a blank package to provide the structure and then use the external program to copy records from a damaged package into the new empty one.