View Full Version : [fixed] Debugger Detected?
djWHEAT
21 Jan 2009, 19:52
First off, LOVE THE MODULES! That stuff is great. Even if I am using higher resolutions, I can still conserve screen space especially if you're working off a single monitor. Great stuff.
I was eager to try my PS3 Eye to see if v.40 resolved some issues. When I try to select it, I'm actually getting a weird message.
Debugger Detected - Please close it down and restart!
Windows NT users: Please note that having the WinIce/SoftIce service installed means that you are running a debugger!
If I hit OK then VB shuts down. I guess I'm already a few steps behind, but I'll do some research. Mike if you have any thoughts or suggestions that'd be great!
This is a typical message from 2 copy protections clashing. Either some program does not like VidBlaster's, or VidBlaster does not like that of another program. You do not mention which program gives the message (should be in the title bar), but the only solution is to make sure the two are not active at the same time.
In your case, if it starts when you activate the Eye, it means its driver has a copy protection that does not like VidBlaster (or vice versa). Which is weird, as I see no reason to copy protect a simple driver. I don't know this camera so can't tell. Are you sure it isn't locked to some utility which is activated simultaneously, and then causes the conflict?
NoobZaibot
26 Feb 2009, 05:00
I am getting the exact message with 0.42 just when I start VidBlaster. Btw, here's the error log :
SESSION 26/02/2009 12:58:01 a.m.
12:58:01 a.m. Monitor 0: 1024*768 0,0
12:58:01 a.m. TClock::TClock
12:58:01 a.m. TUpload::TUpload
12:58:01 a.m. VidBlaster 0.420
12:58:01 a.m. TMn::TMn
12:58:02 a.m. QuickTime 7+ found
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TMon::TMon
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TMon::TMon
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. Doing VideoSettings()
12:58:02 a.m. Found: Pinnacle DV/AV Capture
12:58:02 a.m. Found: WebcamMax Capture
12:58:02 a.m. Found: ManyCam Virtual Webcam
12:58:02 a.m. Found: Logitech QuickCam E2500
12:58:02 a.m. Found: Cirrus Logic USB-DVR2 Source
12:58:02 a.m. Found: Screen Capture
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. Doing VideoSettings()
12:58:02 a.m. Found: Pinnacle DV/AV Capture
12:58:02 a.m. Found: WebcamMax Capture
12:58:02 a.m. Found: ManyCam Virtual Webcam
12:58:02 a.m. Found: Logitech QuickCam E2500
12:58:02 a.m. Found: Cirrus Logic USB-DVR2 Source
12:58:02 a.m. Found: Screen Capture
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. Doing VideoSettings()
12:58:02 a.m. Found: Pinnacle DV/AV Capture
12:58:02 a.m. Found: WebcamMax Capture
12:58:02 a.m. Found: ManyCam Virtual Webcam
12:58:02 a.m. Found: Logitech QuickCam E2500
12:58:02 a.m. Found: Cirrus Logic USB-DVR2 Source
12:58:02 a.m. Found: Screen Capture
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TVideoSwitcher::TVideoSwitcher
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TRecorder::TRecorder
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TAudio::TAudio
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TGraphicOverlay::LoadFile
12:58:02 a.m. TGraphicOverlay::LoadFile Exit
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TMn::ModuleDo
12:58:02 a.m. TVideoEffect::TVideoEffect
12:58:02 a.m. TVideoEffect::VideoSettings
12:58:02 a.m. TVideoEffect::VideoSettings Exit
12:58:02 a.m. TVideoEffect::TVideoEffect Exit
12:58:02 a.m. TMn::ModuleDo Exit
12:58:02 a.m. TVideoEffect::VideoSettings
12:58:02 a.m. TVideoEffect::VideoSettings Exit
12:58:02 a.m. TAudio::AudioDevice("-1")
12:58:02 a.m. TCamera::CaptureArea(0, 0, 320, 240)
12:58:02 a.m. Doing VideoDevice(-1)
12:58:02 a.m. Doing VideoSettings()
12:58:02 a.m. Doing VideoSettings()
12:58:02 a.m. TCamera::CaptureArea(0, 0, 320, 240)
12:58:02 a.m. Doing VideoDevice(-1)
12:58:02 a.m. Doing VideoSettings()
12:58:02 a.m. Doing VideoSettings()
12:58:02 a.m. TCamera::CaptureArea(0, 0, 320, 240)
12:58:02 a.m. Doing VideoDevice(-1)
12:58:02 a.m. Doing VideoSettings()
12:58:02 a.m. Doing VideoSettings()
12:58:02 a.m. TClock::Start
Again, this is not coming from VidBlaster. Another program is not liking VidBlaster and therefore shuts it down. I've seen mpg codecs do this, and apparently the PS3 Eye also does it. To fix the problem find the offending codec/driver/app and remove it. Maybe eventually we can create a list of offenders..
NoobZaibot
01 Mar 2009, 22:48
Sure Mike, but do you have any idea of what is causing it ? A Video Codec, a Video Input Device, anything ? I don't have any probs with 0.40 OR VidBlaster 0.39 .
Maybe there's a way to obtain a more detailed log ?
No. It's the other program that's causing the problem and interferes. If it does not tell who or what it is, there is no way I can. However, I am working on a feature that will allow VidBlaster to start up in a more stealthy way, triggering as little other apps as possible. That means if you have a clean install of VidBlaster (ie. no cameras or files selected) there is a much bigger chance that the offending program will not complain. Which makes it easier to identify it, as it will be a matter of trying things out until it does complain. I.e. if you select a camera and the problem arises, you know it's that camera('s driver). Or if loading a file with extension xxx causes the problem, you will know the xxx codec is the source of the problem.
NoobZaibot
07 Mar 2009, 03:05
No. It's the other program that's causing the problem and interferes. If it does not tell who or what it is, there is no way I can. However, I am working on a feature that will allow VidBlaster to start up in a more stealthy way, triggering as little other apps as possible. That means if you have a clean install of VidBlaster (ie. no cameras or files selected) there is a much bigger chance that the offending program will not complain. Which makes it easier to identify it, as it will be a matter of trying things out until it does complain. I.e. if you select a camera and the problem arises, you know it's that camera('s driver). Or if loading a file with extension xxx causes the problem, you will know the xxx codec is the source of the problem.
Maybe i can clean my sources first, deleting some magic file in VidBlaster's directory ?
Btw it happened with a clean install of VidBlaster Studio 0.42 .
Don't delete files from the VB folder, they're never the problem.
Wait for the next releases.
In v0.43 you should be seeing different behaviour of this message if it's related to codecs, let me know.
slickricks
17 Mar 2009, 00:37
I googled the error message and found this -
"The problem is that Nero installs a DirectShow filter which uses a protection scheme (AsProtect) to prohibit their code being run in a debugger. It sees Visual Studio as a debugger and kills you application.
As far as I can tell the troublesome filter is NeVideo.ax, which you can find in: C:\Program Files\Common Files\Ahead\DSFilter (assuming default install directories etc...).
I renamed this file to "NeVideo.ax.old" and the problem went away.
I haven't noticed any reduced functionality in Nero Burning Rom, although I only do simple CD/DVD burning. If you use any of the multimedia functions of Nero, you might run into problems after renaming its DirectShow filter. Perhaps someone could try it and report back."
I renamed my file and it worked.
Thanks for that feedback Dave. Did you try v0.43 and if so, when did it give the warning? I've been trying, and will continue, to work around the problem.
vBulletin® v3.8.6, Copyright ©2000-2012, Jelsoft Enterprises Ltd.