Zugg Software :: View topic

Apprentice Joined: 03 Nov 2007 Posts: 132

This may just be something with my system but it seems so bizarre I'm hoping someone might have some clue what's causing it or if not then it's a pretty big bug.

So I loaded 2.10 fresh, did a couple of test functions in a blank window. Everything worked fine. Then I did some test functions in my system. It all worked fine. Then I got an out of bounds errors and I started getting this:

ERROR: Syntax error in Function: MasterHealthStandin : invalid command: RETURN

So I go into my settings and sure enough "#RETURN" is showing up in red and is not recognized in that function. I change it to "#RET" and I get:

ERROR: Function "MasterHealthStandin" did not return any result

So I created a test function for it to make sure it wasn't the contents of my function:

#FUNCTION TestFunc {#say hi;#RETURN 1}

Entered into the command line fine with no errors popping up. Did #say @TestFunc() and got:

#say hi;#RETURN 1

Went into settings editor and put #RETURN 1 on its own line and did #say @TestFunc() again and got:

ERROR: Syntax error in Function: TestFunc : invalid command: RETURN

Changed #RETURN to #RET and get:

ERROR: Function "TestFunc" did not return any result

Does anyone have any clue at all why this might be happening? I use a lot of inline functions that I haven't converted over yet. Could that be the problem? I have never seen a situation where an actual command just stops being recognized.

Apprentice Joined: 03 Nov 2007 Posts: 132

So I deleted all my inline functions and replaced them with the new #FUNCTIONS. Then I had to reinstall CMUD and once I did, #RETURN was working again and I haven't had the problem since.

But this happened multiple times to me when I was trying to use both the new functions alongside the inline ones so as far as I can tell the problem was some sort of conflict between the old and the new functions.

Apprentice Joined: 03 Nov 2007 Posts: 132

I spoke too soon. So this time I got a "list out of bounds" pop up error when I was doing a search in my settings. I continued the application but I couldn't see my settings in the settings windows at all after that. So I closed out of CMUD and reopened it again and once again #RETURN is not a recognized command. This is bizarre.

EDIT: Did more testing. Every time I get an "Access Violation" popup error (which can happen randomly when I"m searching in the settings editor for some reason) my #RETURN command is no longer recognized. This is a bit of a problem!

I'm using Vista if that helps.

SubAdmin Joined: 18 Nov 2001 Posts: 5187

Does #RETURN resume working after closing and relaunching CMud? To test this once it stops working close, relaunch, and enter at the command line

Apprentice Joined: 03 Nov 2007 Posts: 132

No, it doesn't resume working once I close it and reopen it. I'll try to find time to do all this full testing but eh, not sure I can. We'll see.

Posted: Thu Nov 08, 2007 7:32 pm

If you have a pkg file that shows the error with #return not recognized, definitely send it to me so that I can look at it.

Also, if there is something you are searching for that consistently causes the crash, let me know what to search for and also make sure you have submitted the crash dump.

Btw, using #return outside of a #function (like the #show example above) is undefined. It leaves an extra value on the stack, which might cause an error.

Apprentice Joined: 03 Nov 2007 Posts: 132

So this is happening in 2.11 as well. I'll send more packages and bug reports but basically what is happening is that every single time *any* kind of error window comes up, #RETURN will stop being a recognized command next time I open up cmud and will persist until I uninstall CMUD and reinstall it.

I have tried uinstalling everything cmud related (except for script backups) from my computer. Writing things from scratch, etc. Problem keeps happening. It's making it extremely difficult to get anything done in the 2.x versions!

Posted: Sat Nov 10, 2007 6:37 pm

As I said, I spent most of the week working on the Script Debugger and timestamp stuff and wasn't able to fix as many bugs as normal. This bug is still on my list, although I'm not sure that I've successfully received your package file yet.

Apprentice Joined: 03 Nov 2007 Posts: 132

I sent it again yesterday to [email protected] but I think I have narrowed down the problem somewhat and posted a bug topic. Hopefully that helps.

Posted: Sat Nov 10, 2007 6:50 pm

I got the email message, but there still wasn't any files attached to it. Not sure what email client you are using, but maybe you can post your PKG file to FileShack or something and email me the URL for it?

Apprentice Joined: 03 Nov 2007 Posts: 132

This problem has been continuing for me with me having to do uninstall/reinstalls several times a day as every time I would get any error at all, when I reloaded cmud it wouldn't recognize any of the new commands such as #RETURN, #SECTION, etc.

It hadn't occurred to me to check the registry to make sure that everything really was getting uninstalled. I did an uninstall and then checked my registry and there were a lot of keys in there and several duplicates from cmud. Cleaned it up, reloaded CMUD, haven't had the problem since. So apparently the problem was with the uninstall not clearing out my registry keys properly.

Posted: Tue Nov 13, 2007 7:52 pm

What version of Windows are you using? The uninstaller is supposed to delete the entire "Software\Zuggsoft\CMUD" registry tree, so maybe it's some sort of permission problem?

Apprentice Joined: 03 Nov 2007 Posts: 132

Using Vista Home Premium. By permission problem do you mean user permissions? I'm the admin and the only one who usees the computer so probably not.

Posted: Tue Nov 13, 2007 8:44 pm

What I mean is that in Vista you are never the "admin" unless you always select "Run as admin" for your programs. And only the Admin can remove certain registry entries usually. So perhaps the Uninstaller wasn't properly "running as admin". I'd be interested in knowing what duplicate registry entries that you had to manually delete.

Apprentice Joined: 03 Nov 2007 Posts: 132

Right, I did the "run as admin" option the last time I did the uninstall but prior to that I just clicked on the approval and continue windows which in theory should have given it the admin access it needed. There were several sets of duplicate IcMUD keys that I cleaned out. I remember those the most but there were a lot and I wasn't really keeping track after awhile. I'm assuming there were 1.34 keys and then the beta keys. Couldn't say for sure though.