GLO Posted September 5, 2004 Share Posted September 5, 2004 i now get this message window that says16 bit MS-DOS SubsystemC:\windows\system32\command.comC:\Windows\SYSTEM32\CONFIG.NT. The system file is not suitable for running MS-DOS and Microsfot Windows applications.Choose 'Close' to terminate the application.Close IgnoreIt came up after installing Asus Wifi driver, but it never happened before??? Link to comment Share on other sites More sharing options...
GLO Posted September 5, 2004 Author Share Posted September 5, 2004 i have un-installed the Asus Wifi driver but the warning still comes up???Help.Thanks Link to comment Share on other sites More sharing options...
N1K Posted September 6, 2004 Share Posted September 6, 2004 what app are you trying to launch when this error occurs?If this problem is because of Asus driver and uninstall of the driver didn't help, try to run system restore.. Link to comment Share on other sites More sharing options...
GLO Posted September 6, 2004 Author Share Posted September 6, 2004 this problem occurs at start up,As mentioned earlier, it appeared after installing the Asus Wifi driver, but in my previous install it came up (hence another reason for the rebuild)I have done a system restore, which has momentarily saved me from another rebuild, but im just not sure what is triggering off the error! Link to comment Share on other sites More sharing options...
N1K Posted September 6, 2004 Share Posted September 6, 2004 Maybe some component stayed in registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Runor in windows startup folder...Check that, you shoud find the solution there... Link to comment Share on other sites More sharing options...
GLO Posted September 8, 2004 Author Share Posted September 8, 2004 the error is definitely related to the Asus Wifi driver, as I installed it again only to find the error again, then uninstall removed the error.BUT.... this driver worked fine under XP sp1. What could SP2 have changed to give that error now? Link to comment Share on other sites More sharing options...
N1K Posted September 8, 2004 Share Posted September 8, 2004 this is XPSP2 compatibility issue for sure Link to comment Share on other sites More sharing options...
Providence Posted September 8, 2004 Share Posted September 8, 2004 only missing config.ntyou can copy a config.nt to windows\system32 to fix it Link to comment Share on other sites More sharing options...
GLO Posted September 8, 2004 Author Share Posted September 8, 2004 only missing config.ntyou can copy a config.nt to windows\system32 to fix itwould that be a sure fix? I sure hope so...Please let me know!EDIT: I searched for it, but cant find it. Where else can i locate a copy of it? Can i just copy it from a nother PC??? Link to comment Share on other sites More sharing options...
Providence Posted September 9, 2004 Share Posted September 9, 2004 only missing config.ntyou can copy a config.nt to windows\system32 to fix itwould that be a sure fix? I sure hope so...Please let me know!EDIT: I searched for it, but cant find it. Where else can i locate a copy of it? Can i just copy it from a nother PC??? of coz you can copy it from another computer(be sure of the same system version)also you can expand it from installation cd Link to comment Share on other sites More sharing options...
GLO Posted September 9, 2004 Author Share Posted September 9, 2004 now its asking for me for the AUTOEXEC.NT fileI will transfer that file too. Any idea how many files its going to ask for??? Link to comment Share on other sites More sharing options...
GLO Posted October 29, 2004 Author Share Posted October 29, 2004 well i managed to get it all working by copying the config.nt and autexec.nt files from a sp1 install!But now, after almost 2months of it working fine, i get the Autoexec.nt error again! What makes this even stranger is that i have once again copied the autoexec.nt file back to the system32 folder and reboot, only for it to dissappear, time and time again???Why is it deleting the autoexec.nt file? Link to comment Share on other sites More sharing options...
GLO Posted January 1, 2005 Author Share Posted January 1, 2005 is there a legitimate fix for this? I couldnt find anything on the MS site. Link to comment Share on other sites More sharing options...
madsc Posted January 2, 2005 Share Posted January 2, 2005 Start=>Run=>cmd [Enter] expand F:\i386\config.nt_ c:\windows\system32\config.nt [Enter] expand F:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt [Enter] expand F:\i386\command.co_ c:\windows\system32\command.com [Enter] Where F: the drive with ur xpsp2 cd in/sc Link to comment Share on other sites More sharing options...
Drewdatrip Posted January 2, 2005 Share Posted January 2, 2005 Did you use Nlite and remove 16bit support?|Drew| Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now