Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


16 bit MS-DOS Subsystem Error Box ?

  • Please log in to reply
1 reply to this topic

#1 Keyboarder


  • Members
  • 20 posts
  • Local time:12:03 PM

Posted 17 January 2009 - 11:22 AM

I have XP Pro 32 bit OS installed. I had just started to install TrendMicro PRO internet security, replacing Norton Internet Security 2009. At the beginning of the TrendMicro installation it indicated that it was incompatible with NIS 2009 and did I want it to uninstall NIS 2009, and I let it remove it. Based upon not ever having the below error box come up before, I am wondering if this method of removal of the NIS 2009 program caused a file to be removed that should not have been removed, or ?

The error box indicates:

C:\PROGRA~1\AGI\common\BOOTST~1.EXE. The NTVDM CPU has encountered an illegal instruction. CS"051f IP:01bf OP:63 72 6f 3c 2f Choose 'Close' to terminate the application.

It gives a 'Close' or 'Ignore' option to close out the box. This error box comes up each time the computer is turned on or restarted.

Has anyone ever seen this type of error box before?

Does anyone have any ideas as to how to resolve this?

Thanks for any inputs that you may have.

BC AdBot (Login to Remove)


#2 Guest_Jay-P VIP_*

Guest_Jay-P VIP_*

  • Guests

Posted 17 January 2009 - 11:27 AM

This is an access violation. Windows XP/Vista based computers can give these types of error messages. What happens is that the application itself has not initialized the transfer of files correctly, and it caused another process to terminate itself, so the setup can continue. To work out these issues, always make sure you have the appropriate Microsoft Windows Updates.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users