Debugger detected [304]

[SpazzHH]

I've not ever had problems in the past, but after several clean installs of XP, I keep getting"Debugger detected [304]" error messages when trying to run DVD-RB. Anyone have any suggestions or solutions?

TIA,
Spazz

[LoRd_MuldeR]

Well, I don't know that DVD-RB program. But that error message sound like a "Debugger Protection" to me.
The author of the program doesn't want you to run the program with a debugger, you might be able to obtain too much information ;)

So, are you running a debugger or a similar development tool on your computer?

[SpazzHH]

I'm not running anything that doesn't come with a fresh Windows install. The only two settings that disable script debugging are both disabled.

[LoRd_MuldeR]

Maybe your Antivirus software or some tool like the "Process Explorer" is detected as a Debugger by DVD-RB ???

I think the best is: Contact the author and ask for support ...

[SpazzHH]

I'm at a total loss here. With these being clean installs, there is not even any anti-virus software installed yet. I've been fighting with this for a week now, and am almost too frustrated for any clean words.:confused:

[blutach]

@Lord Mulder

I routinely run Process Explorer and have no issues with DVDRB. And I think SpazzHH is precisely trying to contact the author and the support by posting here.

Regards

[LoRd_MuldeR]

I routinely run Process Explorer and have no issues with DVDRB.

I just asked because I am aware that there are some applications out there that won't run after Process Explorer has been used due to a so called "Copy Protection", namely Bioshock DEMO version. So I though maybe (just maybe) a similar thing might be the case here...

[jdobbs]

The only time I've ever gotten a report of that error was when v1.27.3 is run under Linux/WINE. It should never show on an XP system unless there actually is a debugger running.

[SpazzHH]

There is no debugger running. I get this message with no other programs installed after a re-format. Nothing on the computer but XP, AviSynth 2.56 and RB. On the Advanced tab of Internet properties, both boxes for disabling script debugging are checked.

[jdobbs]

I'm not sure what to say... something has to be different on your system -- you didn't get it before, and there are no other reports of it.

[SpazzHH]

All of the hard drives are different, brand new. Two Raptors running on raid and three 500 GB SATA storage drives. What I thought was going to be a good upgrade is turning into a nightmare. Do you think the new drives could be causing a problem somehow?

[jdobbs]

It isn't likely. Any odd processes running?

[SpazzHH]

Nothing unstandard. It looks just like the list from the old drives. Microsoft services only and the same ones as before.

[rudolfo2]

Did you download all security updates after clean install ??

[jdobbs]

I should be sending out an update soon. I've gotten beta reports that the "debugger" message no longer comes up in WINE -- so I'm guessing this release may correct your issue as well. Of course, on the other hand, I'm not really sure why you would be getting it to begin with... :confused: At least there is a logical understanding as to why an emulator would be interpreted as a "debugger".

[SpazzHH]

After fighting with things for almost two weeks, I found my problem. The data on my back-up hard-drive somehow became corrupt, and when doing the simplest things, such as installing drivers, it would then somehow corrupt Windows every time. I lost a lot of stuff, but at least I have DVD-RB back now. Thanks for all suggestions.

Spazz

[wildchild77]

I should be sending out an update soon. I've gotten beta reports that the "debugger" message no longer comes up in WINE

That is good news.:thanks: