Zugg Software :: View topic

Newbie Joined: 08 Jan 2011 Posts: 4

Access violation at address OODF3F20 in module 'cmudpro.exe'
Read of address 65687638
I get this message when I try to open alias variable trigger or even anything package related in a session.
The package editor comes up but nothing shows when I click on the package which I shouldnt have to do
or havent had to do previous to this error showing up.

The aliases and trigger and even the buttons load but I cannot edit them with using command prompt to
input new aliases ect. (#al blah {say please help me figure this out} NEEDHELPPLEASE)

Also it seems that this certain package loads twice and by that I mean when I click on the package bar
the drop down shows this package twice in the menu. However it doesnt show anything in the editor
reguardless of which I highlight.

Thanks.

Newbie Joined: 08 Jan 2011 Posts: 4

Also just an addendum....the window which pops up for the package editor cannot be reduced in size. I had a scoll something something error but cannot replicate it althought the widow does the same thing reguardless of the error not showing up anymore.

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

Search for the SHIFT trick, the xml export/import process, and the MapConvert utility. You are going to need to use at least two of those methods to fix this.

You may also need to reconstruct your session database, which isn't nearly as convenient as the above three things. First, open up the Session Properties for each of your sessions you want to keep and write down the included packages, the host name and port, and any account names/passwords you have stored there. If you don't remember the passwords, you can open up that session offline, find the Gag lines containing password preference, and then use #PW to see it. Next, close all instances of CMud you have running and delete the sessions.db and sessionkeys.db files. Third, reopen CMud. This should have reset the sessions list to the default values. Fourth, create a new session and fill in the details, repeating this for each session you took notes for.

Usually, these four methods are enough to fix any problems like you're having, but sometimes it's just caused by a bug in your script code. For that, you will have to examine your scripts themselves to find and fix the problem.