Advertisement Join the Conversation Get answers to questions, share tips, and engage with the IT professional community at myITforum. Log In or Register to post comments Anonymous User (not verified) on Jan 18, 2005 I've been trying to figure this out for a while. Ramakrishnan S. Cancel Submit Need more help? this content

At the beginning of each existing line of text, type: REM and add a space. For example: lh %SYSTEMROOT%\system32\mscdexnt.exe becomes REM lh %SYSTEMROOT%\system32\mscdexnt.exeEnter the text listed below Step 10. You may Looking to get things done in web development? This error is typically the result of an invalid entry in the command.com, autoexec.nt, or config.nt files, which NT maintains for compatibility with 16-bit applications. Print reprints Favorite EMAIL Tweet Discuss this Article 69 Anonymous User (not verified) on Nov 3, 2004 someone experienced the similiar problem after applying MS hotfix KB840987 on win2k server. https://support.microsoft.com/en-us/kb/305521

Last week I replace all those files but after a reboot this weekend the 16 Bit issue came back which I did not discover until this morning, only hours after Norton Are you a data center professional? CAUSE This issue may occur if one or more of the following files are missing or damaged:• Config.nt• Autoexec.nt• Command.com SOLUTION See the following Microsoft Knowledge Base article for more information Config.nt Windows 7 now i can't even use my scanner anymore.

Run a scan from Safe Mode with fully updated anti-virus reference files. Config.nt The System File Is Not Suitable For Running Ms-dos And Microsoft Windows Applications Thank You Log In or Register to post comments Anonymous User (not verified) on Nov 26, 2004 OH, and by the way, I tried the method above to get this point, Log In or Register to post comments Anonymous User (not verified) on Mar 10, 2005 "@ECHO OFF" "lh %SystemRoot%\system32\mscdexnt.exe" "lh %SystemRoot%\system32\redir lh %SystemRoot%\system32\dosx.exe" "SET BLASTER=A220 I5 D1 P330 T3" each of https://support.cch.com/kb/solution.aspx/kb4544 Thanks -Christian Log In or Register to post comments nep (not verified) on Nov 19, 2004 P.S.

If you're unable to run anti-virus program locally, use the Online virus scan services listed in this page. 16 Bit Ms-dos Subsystem Windows 7 Skip to Navigation Skip to Content Windows IT Pro Search: Connect With Us TwitterFacebookGoogle+LinkedInRSS IT/Dev Connections Forums Store Register Log In Display name or email address: * Password: * Remember me You are amazing. Choose 'Close' to terminate the applicationIssue An operating system file required to run the installation or application is missing, corrupt, or does not contain required entries.FixPerform a search for the file

Fix the file(s) again, and then do a clean boot in Windows XP If the problem then is gone, you could add more and more (booting in between each change) to

Config.nt The System File Is Not Suitable For Running Ms-dos And Microsoft Windows Applications

Loading... Application running is not safe. 16 Bit Ms-dos Subsystem Error Windows 7 Expand the original files from the NT installation CD-ROM by typing expand command.co_ %systemroot%\system32\command.com expand autoexec.nt_ %systemroot%\system32\autoexec.nt expand config.nt_ %systemroot%\system32\config.nt Restart your computer, and run your 16-bit application again. Config.nt The System Is Not Suitable Windows 7 Choose 'Close' to terminate the application.16-bit MS-DOS Subsystempath to the program that you are trying to start or installconfig.nt The system file is not suitable for running MS-DOS and Microsoft Windows

Right-click on the Autoexec.nt file and choose Copy. news Windows 7 A. Go to Start.B. In the Search programs and files field, type: autoexec.ntC. Autoexec.nt should appear at the top of the list.D. Right-click Autoexec.nt and choose Open file location.E. Thank You!!! Log In or Register to post comments Anonymous User (not verified) on Dec 14, 2004 Followed the Instructions from above to the letter and it would not work for me with Config.nt File Download

Error message regarding Autoexec.nt or Config.nt when trying to install Laplink applications. Thank you! Log In or Register to post comments Anonymous User (not verified) on Apr 3, 2005 http://www.visualtour.com/downloads/xp_fix.exe Log In or Register to post comments bipin (not verified) on Feb 15, 2003 John have a peek at these guys Log In or Register to post comments Please Log In or Register to post comments.

Yes No Article Feedback Your feedback about this article will help us make it better. 16 Bit Ms Dos Subsystem Error Ntvdm Cpu Many organizations today are exploring adoption of Windows 10. I've been fighting with that stupid thing for ages, and I didn't have the Windows disk to fix it.

For further information and other solutions regarding this error see the following Microsoft document:Error message when you install or start an MS-DOS or 16-bit Windows-based program Solution Tools Email Print Attachments

Computer will not accept any of these suggestion. However a reboot will reestablish the problem. Document relates to:PDAsync, FileMover, LapLink Everywhere, PCMover,Laplink Gold SUMMARY When trying to install one of our Laplink products, you get a error message like one of the following:16-bit MS-DOS Subsystempath to Config.nt Windows 7 Location As far as I can tell from the various post, for most people it's just a timing coincidence around their recent install/up of SP2 and the proliferation of this Trojan Furthermore,

Restart PC. In the document, type the following: "@ECHO OFF lh %SystemRoot%\system32\mscdexnt.exe lh %SystemRoot%\system32\redir lh %SystemRoot%\system32\dosx.exe SET BLASTER=A220 I5 D1 P330 T3" Then save the file as autoexec.nt making sure that you do error 451 temporary local problem windows nt error number 1450 occurred. When you attempt to run a 16-bit application under NT, you might receive the following message: Application popup: 16 bit Windows Subsystem : An application has attempted to directly access the

This may cause the application to function incorrectly. Choose 'Close' to terminate the application. This issue may occur if one or more of the following files are missing or damaged: Config.nt Autoexec.nt Command.com Restoring the missing files To restore these files, download the above three Log In or Register to post comments Anonymous User (not verified) on Dec 16, 2004 I solvet this problem with this file (there was no autoexec.nt file in my computer) http://www.atsoft.fi/tiedostot/win/xp/autoexnt.exe

Nov 25, 2001 John Savill | Windows IT Pro EMAIL Tweet Comments 69 Advertisement A. Three cheers for your help!! This was a huge relief from months of stressing over installs! I cant tell youhow happy you have made me!!!

This will stop the autoexec.nt file from being removed during the reboot process. Please click to close or ignore. Thank you so much!!! Most Popular Blog windows error messages windowsystem32d autoexec nt kernerl_data_inpage_error visual basic 6 on error goto inherent error com error message Celebrity Blog Network Home all posts billing due error underpayment

Thank you. In the System32 folder window, right-click a blank area and choose Paste. Autoexec.nt should appear in the System32 folder. Close the folder. Reboot the computer and attempt the operation which caused Advertisement Advertisement WindowsITPro.com Windows Exchange Server SharePoint Virtualization Cloud Systems Management Site Features Contact Us Awards Community Sponsors Media Center RSS Sitemap Site Archive View Mobile Site Penton Privacy Policy Terms Using My Computer, Computer or File Explorer navigate to and open the C:\Windows\System32 folder.