C;\WINDOWS\SYSTEM32\AUTOEXEC.NT. Thanks, sparky4ca Important Disclaimer: Answers and comments provided on Google Answers are general information, and are not intended to substitute for informed professional medical, psychiatric, psychological, tax, legal, investment, accounting, or Close Config.nt. 6. The CONFIG.NT file is a critical system file akin to the command.com file. Source
The 16-bit components described in this article will not work on Windows Vista or Windows 7.This condition does not apply to Amiga Forever 2005 and higher, which use a new installer, Restart your computer. 9. I have searched and searched resources, support groups, knowledgeable IT professionals, etc. Try run 16 bit application (Start, Run, Command.com) you might not able to open it. https://support.microsoft.com/en-us/kb/305521
Choose 'Close' to terminate the application. Why do I receive an error when I attempt to run the Windows .NET Server (Win.NET Server) 2003 Administration Tools under Windows XP? Log In or Register to post comments Anonymous User (not verified) on Jul 9, 2005 I have the similar problem that requires DOSX.EXE in AUTOEXEC.NT (The Win16 Subsystem is unable to
After following the above instructions this should resolve your issue. now the .txt should be there. In the new blank document, type the following block of code: dos=high, umb device=%SYSTEMROOT%\system32\himem.sys files=40 3. If you need the files autoexec.nt or config.nt, copy and paste the following code into notepad and save into the %SYSTEMROOT%\System32 folder.
Please let me know. Method 1: Expand the Files From the Windows XP CD-ROM ----------------------------------------------------- 1. Log In or Register to post comments Anonymous User (not verified) on Nov 23, 2004 thanks for the great advise. Choose 'Close' to terminate the application.
Locate, and then right-click %SYSTEMROOT%\System32, and then click Paste. 8. right click on it and select paste. The system file is not suitable for running MS-DOS and Microsoft Windows applications.
If you get an error naming the AUTOEXEC.NT as not being suitable, it is an indication the AUTOEXEC.NT file Locate, and then right-click Autoexec.nt, and then click Copy. 5.
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. Once I got onto my errous ways and typed the correct CD Rom Cdrive Letter....All the above worked 100% and on re-boot the 16-Bit Cd Rom prgm Installed like Clockworks. To do this you must have the Microsoft Windows XP CD. Locate, and then right-click %SYSTEMROOT%\System32, and then click Paste. 6.
On the File menu, click New. 7. this contact form Click Start, and then click Run. 2. Is there any hope to fix it without the cd-rom? Locate, and then right-click Autoexec.nt, and then click Copy. 5.
when notwepad opens, copy and paste the following into it: dos=high, umb device=%SystemRoot%\system32\himem.sys files=40 then close the window, saving when you are prompted. 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 Another possibility: Programs have the ability to have a custom config.nt and autoexec.nt specified.
Close Config.nt. 6. I have since removed SP1 and then re-installed it. Click Start, Run, type cmd and press enter to open the MS-DOS window. What do I do?\WINDOWS\SYSTEM32\CONFIG\SYSTEM is corrupt.
On the File menu, click Save As. 4. On the File menu, click Save As. 4. You may want to virus-check your system with one of the following free tools:Symantec Virus DetectionPanda ActiveScanMicrosoft has several Knowledge Base articles on this issue, including the following:Error message when You Check This Out Nov 25, 2001 John Savill | Windows IT Pro EMAIL Tweet Comments 69 Advertisement A.
Please let me know if I can be of any further assistance on this question. 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 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 this is what im getting from my pc.
This may cause the application to function incorrectly. Method 2: Create the Files In Notepad And Copy the Files To the System32 Directory ---------------------------------------------------------------------------------- NOTE: The file, Command.com is not edited or created in this Part. 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 Restored to several previously good points.
See the expand command page for additional help and information about the expand command. I used the notepad instuctions, since XP came installed on this PC and I don't have a separate XP installtion CD. Choose 'Close' to terminate the application.16-bit MS-DOS Subsystempath to the program that you are trying to start or installC:\Windows\System32\Autoexec.nt The system file is not suitable for running MS-DOS and Microsoft Windows This will also happen if this file is corrupted.
Search Free Sign Up Login Home Forum How To Download News Encyclopedia High-Tech Health Free Sign Up Language English Español Deutsch Français Italiano Português Nederlands Polski हिंदी Bahasa Indonesia Login Subscribe try your install program again. Thanks for nothing.