Digital Workshop

Hello, I have received the attached error message the last couple of times I exited Opus. Anyone know why?
Thanks,
Mike

Mike --

I've gotten the same message recently, but since OPUS works perfectly when I dial back in, I'd forgotten about it. I thought it was unique to my computer. Thanks for bringing this up. It doesn't happen every time I exit, but it's happened at least three or four times in the last two months.

DW: What does this mean?

I've received the message on a number of occasions too. Like Fred, I've found it doesn't seem to affect the subsequent running of Opus - but it would be good to allay my fears by eliminating the purported problem if possible.

I have received this error a few times and the last time scared me a bit as it had some trouble restarting. It asked to recover the last project, or something like that, I said yes and Opus 5.5 was on the task bar but would not open/restore. After a few different tries, I was able to open by hitting cancel when it asked to recover the project.

I just received the error again with no adverse effects that I can tell.

This type of error sometimes indicates a corrupt entry in the registry, try resetting Opus back to default. A procedure for this can be found at:

http://www.digitalgrapevine.info/viewtopic.php?t=471


Regards

Brenden Knifton

While scanning another forum, I ran across this explanation for the error message we have received:

"In Windows XP Service Pack 2 Microsoft introduced Data execution prevention (DEP), a set of hardware and software technologies that perform additional checks on memory to help protect against malicious code exploits. In Windows XP SP2, DEP is enforced by both hardware and software.

"Some software/application behaviours are incompatible with DEP - data execution prevention. Applications which perform dynamic code generation (such as Just-In-Time code generation) and that do not explicitly mark generated code with Execute permission might have compatibility issues with data execution prevention. Applications which are not built with SafeSEH must have their exception handlers located in executable memory regions.

"Applications that attempt to violate DEP will receive an exception with status code STATUS_ACCESS_VIOLATION (0xC0000005).

"If an application requires executable memory, it must explicitly set this attribute on the appropriate memory by specifying PAGE_EXECUTE, PAGE_EXECUTE_READ, PAGE_EXECUTE_READWRITE or PAGE_EXECUTE_WRITECOPY in the memory protection argument of the Virtual* memory allocation functions.

"If you are having issues with 0xC0000005 errors in DEP and a particular piece of software is causing the offence, contact the vendor for a resolution...

"Note: It is possible to "Turn Off" DEP in the boot.ini file but this really would be a last step!

/NOEXECUTE

"This option is only available on 32-bit versions of Windows when running on processors supporting no-execute protection. It enables no-execute protection (also known as Data Execution Protection - DEP), which results in the Memory Manager marking pages containing data as no-execute so that they cannot be executed as code. This can be useful for preventing malicious code from exploiting buffer overflow bugs with unexpected program input in order to execute arbitrary code. No-execute protection is always enabled on 64-bit versions of Windows on processors that support no-execute protection.

"There are several options you can specify with this switch:

/NOEXECUTE=OPTIN Enables DEP for core system images and those specified in the DEP configuration dialog.

/NOEXECUTE=OPTOUT Enables DEP for all images except those specified in the DEP configuration dialog.

/NOEXECUTE=ALWAYSON Enables DEP on all images.

/NOEXECUTE=ALWAYSOFF Disables DEP. (This setting doesn't provide any DEP coverage for any part of the system, regardless of hardware DEP support. The processor doesn't run in Physical Address Extension (PAE) mode unless the /PAE option is present in the boot.ini file.)

"You can read more about DEP at:

http://www.updatexp.com/data-execution-prevention.html

Hey demofred, thanks for looking that up and posting it! You are always most helpful!
Mike