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 At the command prompt, type the following, press ENTER between each line: expand
Choose 'Close' to terminate the application. YesNo Feedback E-mail Share Print Search Recently added pages View all recent updates Useful links About Computer Hope Site Map Forum Contact Us How to Help Top 10 pages Follow us Close Autoexec.nt. Start Windows Explorer. 2. anchor
Advertisement Join the Conversation Get answers to questions, share tips, and engage with the IT professional community at myITforum. Thanks again. Thanks -Christian Log In or Register to post comments nep (not verified) on Nov 19, 2004 P.S. Config.nt Windows 7 Start Notepad. 2.
Restored to several previously good points. Solution 1 Solution 2 Solution 3 When trying to install a 16 bit Windows on your PC, the following error message appears on your screen: c:\windows\system32\autoexec.NT. On the File menu, click New. 7. see this here Restore the autoexec.nt and config.nt files from the repair folder For users who do not have their Windows XP or 2000 CD or want to try restoring their backup files from
Right click on your new config.nt file, choose cut, and then opwn my computer. Config.nt Windows Xp The problem seems to have begun when SP1 was attempting and finally successfully installed itself. In the left pane, scroll down and click the Repair folder. Choose 'Close' to terminate the application. 16-bit MS-DOS Subsystem path to the program that you are trying to start or install C:\Windows\System32\Autoexec.nt The system file is not suitable for running MS-DOS
Locate, and then right-click %SYSTEMROOT%\System32, and then click Paste. 8. http://www.tomshardware.com/forum/114718-45-autoexec-file Log In or Register to post comments Anonymous User (not verified) on Oct 28, 2004 This all works fine and well... 16 Bit Ms-dos Subsystem Error Windows 7 In the Open box, type cmd, and then click OK. Config.nt Not Suitable For Running Ms-dos Windows 7 Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
In the right pane, right-click on any blank space inside the window and click Paste. 0 Message Expert Comment by:Richard19682005-04-26 I have seen this problem on about 10 to 15 Start the program. To resolve this issue, use MS-DOS prompt to expand the files from the Windows XP CD-ROM, or edit the files in the text editor, Notepad. That should find it and the location of all of the Windows installation files if they exst on your system. Config.nt File Download
JoinAFCOMfor the best data centerinsights. For autoexec.nt @echo off lh %SYSTEMROOT%\system32\mscdexnt.exe lh %SYSTEMROOT%\system32\redir lh %SYSTEMROOT%\system32\dosx SET BLASTER=A220 I5 D1 P330 T3 For config.nt dos=high, umb device=%SYSTEMROOT%\system32\himem.sys files=40 Log In or Register to post comments Anonymous User Sincerely, PWizard Request for Answer Clarification by mellen-ga on 30 Oct 2002 06:59 PST Actually when I created the new config.nt file without the new autoexec.nt file it did not solve Check This Out Note: The Command.com file is not edited or created in this in the following process.
Software I have run; AVG 6.0 Trend Micro Cool Web Shredder Hijack This Spybot S&D Adaware All has been done with system restore flushed and off OK, in saying all that Config.nt Windows 7 Location Clarification of Answer by pwizard-ga on 30 Oct 2002 07:01 PST No problem, here's the whole shebang: This error can occur when the files, Config.nt, Autoexec.nt and Command.com, are missing or The Autoexec.nt file will not.
I have tried pulling the config nt and autoexec nt file from widows/repair but nothing will allow me to overwrite the existing autoexec.nt I have tried MS's step by step found The My Computer explorer window appears. Sometimes windows updates or other software updates delete your autoexec.nt file from the system32 folder. 16 Bit Ms-dos Subsystem Windows 7 Join Now For immediate help use Live now!
Please let me know. All of the resources I've searched points to this as the resolution. In the new blank document, type the following block of code: @echo off lh %SYSTEMROOT%\system32\mscdexnt.exe lh %SYSTEMROOT%\system32\redir lh %SYSTEMROOT%\system32\dosx SET BLASTER=A220 I5 D1 P330 T3 8. http://sysgsm.com/windows-7/windows-xp-system-time-error.html Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.
As a result, when trying to run certain applications which make use of 16-bit technology an error message like the following may be displayed: "16 bit Windows Subsystem - C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. now windows or any other related programs no longer able to delete that file away and the error never come back again. 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 Database administrator?
Once the above two files have been copied, type "exit" to exit the MS-DOS window. That advice does not seem to be in the earlier version of the Article copied above. Locate, and then right-click Command.co, and then click Copy. 7. Log In or Register to post comments Anonymous User (not verified) on Nov 24, 2004 My computer came with XP, and has no install disc with it.
Locate the Command.com file, right-click the expanded Command.com file, and then click Copy. Log In or Register to post comments Anonymous User (not verified) on Nov 23, 2004 thanks for the great advise. I was happy to assist you with this question. ForumsJoin All FAQs → The Broadband Reports Windows XP FAQ → 7.
A little background info: config.nt is the rough equivalent to config.sys autoexec.nt is the rough equivalent to autoexec.nt You might not be finding them because they are hidden, system, or protected On the File menu, click Save As. 4.