NTVDM - NT Virtual Dos Machine Error

[Robert Neville]

My system is running Windows XP Pro and encounters this message
whenever double clicking on 16 bit executable. In this case, the
offending file is a self-executable archive. The error occurrence
happens with several other setup files as well.

16 bit Windows Subsystem
The NTVDM CPU has encountered an illegal instruction. CS:cf76 IP:0105
OP:c7 8b 93 86 08 Choose 'Close' to terminate the application.

My internet research has bought me some insight on situation, yet the
problem still persists. XP's compatibility wizard did not resolve my
problem either. Knowledge base article 314452 (link below) gave me the
most insight about the situation, yet the suggestions outlined here
did not remedy the situation. Now, the next step is not obvious to
me. Please let me know if anyone has suggestions about a possible
resolutions.


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

[Mark L. Ferguson]

try the "Application Compatibility Toolkit"
http://www.msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid=28000911


--
Mark L. Ferguson TabletPC MVP
Email address : Subject: "QZ" + anything
All email without "QZ" in the subject line will be automatically deleted.
marfer's notes for XP > http://www.geocities.com/marfer_mvp/xp_notes.htm
..

"Robert Neville" > wrote in message
...
> My system is running Windows XP Pro and encounters this message
> whenever double clicking on 16 bit executable. In this case, the
> offending file is a self-executable archive. The error occurrence
> happens with several other setup files as well.
>
> 16 bit Windows Subsystem
> The NTVDM CPU has encountered an illegal instruction. CS:cf76 IP:0105
> OP:c7 8b 93 86 08 Choose 'Close' to terminate the application.
>
> My internet research has bought me some insight on situation, yet the
> problem still persists. XP's compatibility wizard did not resolve my
> problem either. Knowledge base article 314452 (link below) gave me the
> most insight about the situation, yet the suggestions outlined here
> did not remedy the situation. Now, the next step is not obvious to
> me. Please let me know if anyone has suggestions about a possible
> resolutions.
>
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;314452
>

[Robert Neville]

On Mon, 7 Jul 2003 14:56:59 -0500, "Mark L. Ferguson"
> wrote:

>try the "Application Compatibility Toolkit"
>http://www.msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid=28000911

This Toolkit has a significant learning curve and exists for
developers. I gave 30 minutes; yet do not appreciate using my
disposable free time to resolve this issue.

The issue is not with the actual executables, yet rather my desktop
installation of Windows XP. Every file that returns the aforementioned
error works without incident on my laptop, which has the same XP
flavor. Thanks for the assistance.