TheBackShed.com

Forum Index : Microcontroller and PC projects : MM Edit Error

Author

Message

Phil23
Guru

Joined: 27/03/2016
Location: Australia
Posts: 1664

Posted: 07:41pm 15 Jun 2016

Copy link to clipboard

Print this post

Probably for Jim.

Figured I'd load MMedit on my Office PC, yesterday.

Didn't have any luck.

Returns this error when I try & launch it.

Attached is the contents of AppData.....

Removed the help file so it wasn't to big to upload.

Thanks

Phil.

2016-06-16_053757_MMedit.zip

Edit:-

Forgot the log file....

2016-06-16_054345_ERROR.zip Edited by Phil23 2016-06-17

TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 5950

Posted: 07:49pm 15 Jun 2016

Copy link to clipboard

Print this post

Phil,
This is the standard reply I give for this error message:

Quote A non-continuable protection violation is Windows' way of protecting us from rouge software and to make life difficult for program developers.
Visa made the setting too tight but they relaxed things a bit for Windows7.
My W7 had the default setting and all is well but some PC suppliers had things set tight.
You can either change your settings or install MMedit into a folder that is NOT in 'Program Files'
Please check you DEP settings and if is not set to essential Windows programs only, that is the problem. If you want to leave it set for all programs you can add MMedit as an exception or go the other folder method.

The easiest way to find DEP is to search Windows Help for DEP.

DEP stands for Data Execution Prevention.

I did add a "manifest" which is supposed to stop this from happening but as you have seen, Windows wins the battle some times.

It has worked every time so far...

For the record, what version of Windows?

Jim

VK7JH
MMedit MMBasic Help

Phil23
Guru

Joined: 27/03/2016
Location: Australia
Posts: 1664

Posted: 10:33pm 15 Jun 2016

Copy link to clipboard

Print this post

TassyJim said Phil,

For the record, what version of Windows?

Jim

Sorry Jim,

Intended to add that, W7Pro SP1

I'm familiar with DEP

Thanks

Phil

Phil23
Guru

Joined: 27/03/2016
Location: Australia
Posts: 1664

Posted: 10:41pm 15 Jun 2016

Copy link to clipboard

Print this post

Must be one of those days.....

MS ran some updates last night, every PC logged off this morning.

Just put my feet up in the lounge chair, MM Edit was fine this morning.

Launched it, had a look at the console with Chat, all good.

Made a few code changes & received an error following upload when chat tries to open.
Can't get chat to open at all.

Same OS, W7Pro SP1 64 bit.

Phil.

2016-06-16_084057_error.zip

Edit:-

DEP Exclusion fixed the laptop issue.

Cheers.Edited by Phil23 2016-06-17

TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 5950

Posted: 12:27pm 16 Jun 2016

Copy link to clipboard

Print this post

Glad you have the DEP problem solved.

The subscript out of range looks like MMEdit received a positioning command that sent the cursor position into la-la land.
That could have been a comms error or a bug in MMEdit.
To fix it, you need to shut down MMEdit fully, not just the Chat window.

You may need to check with task manager to see if there are any leftover instances of MMEdit running.

The usual Windows Help Desk motto "Have you tried turning it of and back on again" applies here.

Jim

VK7JH
MMedit MMBasic Help

Phil23
Guru

Joined: 27/03/2016
Location: Australia
Posts: 1664

Posted: 02:15am 22 Jun 2016

Copy link to clipboard

Print this post

Received this one again tonight.

Similar scenario to last time...

[Quote]
Put my feet up in the lounge chair again.

Launched it, had a look at the console with Chat, all good.

Made a few code changes & received an error following upload when chat tries to open.
Can't get chat to open at all.[/quote]

TassyJim said The subscript out of range looks like MMEdit received a positioning command that sent the cursor position into la-la land.

Turned out the error was being caused by a syntax error in my code that was outputting an error message string that was too long for MMchat (I think).

That's probably what was sending the cursor out of bounds.

Fixed the typo in my code & then all was fine.

Cheers

Phil.

Print this page

To reply to this topic, you need to log in.