Zugg Software :: View topic

Beginner Joined: 08 Feb 2005 Posts: 18

I can't seem to connect to my main session anymore. Suddenly now when i double click on it, it crashes the application (or at least, asks me first - I've sent in a few error logs).

Any ideas here? I tried switching out to another package file, and it stops crashing, but of course, no settings are there anymore. I switched back to the one I used before, and the crashes begin again.

Beginner Joined: 08 Feb 2005 Posts: 18

Posted: Wed Nov 15, 2006 10:14 pm

Email the corrupted .pkg and sessions.db to support@zuggsoft.com would be what Zugg would say, I imagine. These corruption errors are the ones he seems to hate, since the whole point of the new SQL format is that they don't get corrupted.

Wanderer Joined: 09 Nov 2006 Posts: 55

Mine did too. worked great, shut down for the night, woke up, tried to log in - bzzp
I emailed it also to support

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

When you close out of a session instead of closing cMud it corrupts the package. It is EXTREMELY anoying I know.

To deal with it the best way is to delete your package file, and reimport your stuff. There are of course several ways of reImporting. Then untill Zugg gets the close session bug fixed just exit from cMud instead of your session.

Beginner Joined: 08 Feb 2005 Posts: 18

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Without a .MUD or similar zmud file, or an xml export of the .pkg file, you're basically looking at starting over from scratch. If you want to get really (and dangerously?) extreme, since the .pkg file is an SQLite database you could simply try to load it in an application that supports that format and maybe salvage the information that way. I have no idea if that'd work, and the information probably isn't very user-friendly anyways so I'd probably treat it with the extreme caution of messing with the registry.

I'd just consider it a lesson learned and do things the easy way, though.

Wanderer Joined: 09 Nov 2006 Posts: 55

I backed up my settings PKG in a separate folder as well but even that file has the same corrupted junk as the one in the cmud folder. (must have saved that after the files got screwed) anyhow, I deleted the Cmud completely, re-installed, and opened a new session. I went in the settings editor and OPENed the old (screwed) package fine. - I cant use any of the settings but every one of them is still there! maybe just try to do that and then copy/paste settings into your new pkg...??

dunno

Wanderer Joined: 09 Nov 2006 Posts: 55

Yeah Chandler Mike, try this, it worked for me temporarily while my corrupted package is 'in the mail' to support

I copied the corrupted .pkg in another folder, uninstalled, deleted the directory, re-installed Cmud and logged on to the horrid green text mud. Shocked

Then from settings editor, FILE - OPEN - selected my corrupted.pkg - SAVE AS - pointed to the cmud folder where the fresh pkg is. Then in the setting editor, click the all tab so you see both your package and the new one, make your settings the same as the default (check the window visible box, and use main session) - save - select the default pkg, uncheck the enable box, save, exit editor. Go back in settings editor, select the default pkg, rightclick - DELETE setting. exit editor

now you have a working session, a package of your old settings, and should be fine - cept edit the session with character and password if you autologin...

I'll let you know how it goes when i shutdown and start again. Going to take a stress break and go KILL people!!!

Posted: Thu Nov 16, 2006 6:41 pm

Just so people don't get their hopes up...when you email me a corrupted PKG file, I probably can't fix it for you. So don't wait for me to fix it and send it back to you...that probably won't happen. Sometimes I can determine why a pkg file is corrupted and fix a bug, which is why I request corrupted files.

But also, you never mentioned what version of CMUD you are using either in your topic subject (put [1.15] or whatever your version is in your subject line), or in the message body.

The 1.13 version had several bugs that could cause corrupted packages. So if you were using this version of CMUD, I recommend that you reintall a fresh copy of 1.15 and re-import your old zMUD files.

But ALWAYS tell us what version you are using when you get a problem.

Wanderer Joined: 09 Nov 2006 Posts: 55

my version was [1.15]
I did use close session to close it before it stopped working

A better way I got the corrupt settings to work was ->

start a new session on a fresh install
edit settings
open -> point to corrupt settings
convert to module
publish

then ALL the settings worked in the new not-crashing session
just need to change the preferences again for the session window

HEY, how do I get module settings to show up in the settings window?
It just shows settings for the new package but not the module unless I go into settings editor...

Beginner Joined: 08 Feb 2005 Posts: 18

Posted: Mon Nov 20, 2006 3:15 pm

Posted: Mon Nov 20, 2006 3:18 pm

I think he means the session fly-out window and how it doesn't seem to include settings from more than one package.

Posted: Mon Nov 20, 2006 3:48 pm

Ahh, ok, if that is the case then Yes, the fly-out settings editor only shows you the settings for the currently selected window. To edit other modules you have to open the main settings editor.