Debugger detected - Please close it down and restart!

[Baardsman]

After a long time working without any problems this week Autoplay Media Studio started with giving an "Protection error message". Everytime my project opens a MediaPlayer object.

Debugger detected - Please close it down and restart!

Due to this message I am not able to use AutoPlay Media Studio anymore. Everytime this message comes up. I tried to find out which program causes the problem, but nothing helps (Closing every possible background running program in Windows, Uninstalling programs I've installed the last weeks, etc., etc.)
As the problem only comes up when a Mediaplayer object opens, I've tried to open the files in MediaPlayer directly, but this works without a scratch. Searching in the Microsoft MediaPlayer website, showed the problem is known to Microsoft.

http://support.microsoft.com/default.aspx?scid=kb;en-us;812759

But non of the given possible solutions did help solve this problem.

Has anyone else had the same problem with Media Studio??? Does anyone have a solution to solve this problem???
Please help me out!!!

Baardsman

P.S. I'm using AMS4.004; Windows-XP Pro; Media Player 9.

[rhosk]

Re: Debugger detected - Please close it down and restart!

Well, this is a longshot, but I'm sure you'll take anything right now, right? Right-click "My Computer" and go into "Properties" and select the "Advanced" tab. Down at the bottom is settings for "system startup, system failure, and debugging information" - select "Settings" and make "Write debugging information" NONE (if it isn't already) and restart. Like I said, a longshot, but hope it helps!

[Lorne]

Re: Debugger detected - Please close it down and restart!

AutoPlay includes protection to prevent it from running if there are any debugging tools in use, to make it more difficult for hackers to inspect and manipulate the program code. (Tools such as SoftICE allow you to step through the execution of any program that is running, change values in it, and other such things.)

You might want to investigate what programs and services are running in the background on your system when this happens.

[rhosk]

Re: Debugger detected - Please close it down and restart!

That's just it. I had a program "dumprep 0 -k" that somehow got into my startup programs after a severe memory dump problem. If you look in your msconfig, you may see, either that service starting or something else peculiar.

[Baardsman]

Re: Debugger detected - Please close it down and restart!

Thanks for your help sofar!

I've checked the things you've mentioned here, but none of the mentioned settings or programs were on. At the moment I do not know what to do as I dón't know which program is causing this problem.
Stopping programs from within the Windows System Manager didn't help sofar.

Does anyone know about a list of programs which could cause this error message???
Could it be a virus???'

Baardsman

[Colin]

Re: Debugger detected - Please close it down and restart!

If you haven't installed anything recently on your system and you've just started getting this message, I'd certainly recommend running some anti-virus scans. Something that is trying to intercept system calls is *definitely* running on your computer.

[Baardsman]

Re: Debugger detected - Please close it down and restart!

Problem solved!!!

It had to do with the new 5.1 DivX Codec I had recently installed. Switching back to the 5.05 version solved the problem.

Thanks to all for your great help!!!

Baardsman

[Lorne]

Re: Debugger detected - Please close it down and restart!

After doing a bit of research, I've uncovered the cause of the mysterious error message.

Our software is protected by a third-party software protection system. Apparently the people who built the divx package in question copied or otherwise duplicated some of the code from that software in order to protect divx. It's actually divx that is preventing the video from playing in AutoPlay, and not the other way around.

In fact, it's divx that was displaying the error. The error message was misleading because it was exactly the same as it would have been if the system protecting AutoPlay had generated the error. (It seems the divx 5.1 people "borrowed" the error message as well.)

The good news is that this has already been fixed. The current version of divx 5.1 includes a fix for this problem. Note that the version number has not changed; if you currently have divx 5.1 and you encounter this problem, download divx 5.1 again and the problem should be solved.