Guest OS: Windows XP Pro SP3
IDE: MS Visual Studio 2010 [now uninstalled]

How to fix the following ...
http://img151.imageshack.us/img151/9...ustintimed.jpg
which started popping up after installing/uninstalling MS Visual Studio
2010.

"Adam" <adam@no_thanks.com> wrote in message
news:jn6qbs$6vm$(E-Mail Removed)...
> Guest OS: Windows XP Pro SP3
> IDE: MS Visual Studio 2010 [now uninstalled]
>
> How to fix the following ...
> http://img151.imageshack.us/img151/9...ustintimed.jpg
> which started popping up after installing/uninstalling MS Visual Studio
> 2010.
>

Nevermind ... renaming the following ...

C:\WINDOWS\system32\vsjitdebugger.exe

to

C:\WINDOWS\system32\vsjitdebugger.exe.remove

did the trick.

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:0b-(E-Mail Removed)...
> From: "Adam" <adam@no_thanks.com>
>
>> Guest OS: Windows XP Pro SP3
>> IDE: MS Visual Studio 2010 [now uninstalled]
>>
>> How to fix the following ...
>> http://img151.imageshack.us/img151/9...ustintimed.jpg
>> which started popping up after installing/uninstalling MS Visual Studio
>> 2010.
>>
>
> Are you using the full version of Adobe Acrobat or just the Adobe Reader ?
>
> --
> Dave
> Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
> http://www.pctipp.ch/downloads/dl/35905.asp

I am using Adobe Acrobat but that wasn't the problem since
Acrobat has been working fine for a while now.
The two JIT messages started popping up right after
installing MS Visual Studio 2010. One JIT message displayed while
Visual Studio was installed. And, the JIT message posted is displayed after
uninstalling Visual Studio.

Adam wrote:

> Adam wrote ...
>
>> Guest OS: Windows XP Pro SP3
>> IDE: MS Visual Studio 2010 [now uninstalled]
>>
>> How to fix the following ...
>> http://img151.imageshack.us/img151/9...ustintimed.jpg
>> which started popping up after installing/uninstalling MS Visual
>> Studio 2010.
>
> Nevermind ... renaming the following ...
>
> C:\WINDOWS\system32\vsjitdebugger.exe
> to
> C:\WINDOWS\system32\vsjitdebugger.exe.remove
>
> did the trick.

But that means you are probably generating a hiccup in the operation of
the debugger as defined in the registry. When an error occurs, the
debugger will still get called but you're hiding the program.

You removed VisualStudio which means you no longer have access to its
enhanced debugger. Apparently the uninstall of VS was not complete if
the registry is still pointing at the vsjitdebugger.exe file plus that
file shouldn't have been left behind (unless you have something else
installed that put it there).

You no longer have a usable debugger because what's in the registry is
still pointing at the VS stuff that you uninstalled. You'll want to
resume to using the old Dr Watson debugger (drwtsn32.exe) that comes
bundled with Windows to catch unhandled exceptions in the software
you've installed.

http://support.microsoft.com/kb/188296
http://support.microsoft.com/kb/121434

http://support.microsoft.com/kb/308538

http://en.wikipedia.org/wiki/Dr._Watson_(debugger)