Zugg Software :: View topic

Wanderer Joined: 19 Nov 2004 Posts: 70

An error occurred in the application.

Access violation at address 00C5D3D5 in module 'cMUD.exe'. Read of address 0020013D.

Wanderer Joined: 19 Nov 2004 Posts: 70

creating a new session allows me to log onto the mud.

Wanderer Joined: 19 Nov 2004 Posts: 70

also getting null pointers (read of address 00000000) everywhere. the tabbed/floating windows problem has been consistant across versions for me. I recently tried to import the xml that I was able to export from the beta version, and I now have reoccuring crashes. Can someone please explain what the correct settings are in the package explorer for different windows?

Currently, I have 4 windows. My main window which has a status bar, a command line, and is visible. The other 3 windows are to capture text, be it clan channel communications/public channels, group talk, and one to capture improves. Those three windows are supposed to be without a command line, status bar, and should be visible. I get multiple versions of the same windows popping up seemingly randomly. When I create a new session and import the xml (instead of loading the package), I get the same behavior.

I take it the export all to xml/import stuff is still not working?

Anyway, as I'm completely unable to mud in any way other than manually, can someone please take a look at the call stack and see if there's a way I can modify the xml so I can import it and log on? Meanwhile, I'll manually start looking through the xml for the windows section and see what I can find out on my own.

Wanderer Joined: 19 Nov 2004 Posts: 70

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

With three windows all named gtells and two named tells, doesn't it get confusing? And, I'm fairly sure that the host=-2 is what tells CMUD whether the window uses it's connection, no connection, or the master connection, but not certain about which one -2 is, if that is the case.

Wanderer Joined: 19 Nov 2004 Posts: 70

Wanderer Joined: 19 Nov 2004 Posts: 70

is there any way to recover the setup I had before I upgraded? This "upgrade" is removing my desire to mud completely. I can't believe I lost over 100 new triggers and haven't been able to completely start up cmud without these errors or just some weird windowing problem. Frankly, I prefer the previous beta.

Wanderer Joined: 19 Nov 2004 Posts: 70

Wow. Now I can't even import the xml (after removing all window entries except the main one) without cmud hanging (no call stack this time -- cmud doesn't get that far before the task has to be killed).

SubAdmin Joined: 18 Nov 2001 Posts: 5182

It sounds like you have a corrupted layout. I would suggest deleteing the .xly and .tbz files for that specific session then reopening it. Removing the window settings that are using the corrupted data only keeps it from doing immediate damage when the session is loaded, but the bad data from those 2 files is still around waiting like a bomb.

Beginner Joined: 02 Oct 2004 Posts: 20 Location: Florida

I'm having a similar problem. After starting the application, I open my session and get the error. It happens for every session I load. I even got the error when opening a connection without a session. After rebooting, I can open a connection but not a session without getting the error.

I tried Vijilante's solution, but it didn't work.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Chewbacon, your crash and error is different from the one haiku originally presented. Also some of the the things in your crash dump don't quite add up for the procedure your saying. From your description the procedure you are using is:
1. Launch CMud
2. Select session from Sessions window
3. Click Open Offline in the Sessions window

If you are using a different procedure to generate the crash we would need that detail. Also after you reply I will split this off into a seperate topic.

Wizard Joined: 14 Oct 2000 Posts: 1368