MS-DOS
Started by
K33N4N
, Apr 27 2005 02:36 AM
#1
Posted 27 April 2005 - 02:36 AM
#2
Posted 27 April 2005 - 03:47 PM
is any 1 nit able to help me? if yiu can plz hola bk!!
#3
Posted 27 April 2005 - 05:39 PM
here's something you can try while waiting for a better idea:
try deleting the printer from Printers and Faxes
start>Printer and Faxes>left click on printer>file>delete
try deleting the printer from Printers and Faxes
start>Printer and Faxes>left click on printer>file>delete
#4
Posted 28 April 2005 - 02:58 PM
Hey tried that already it didn't work this is the error message that come up
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running MS-DOS and
Microsoft Windows applications. Choose 'Close' to terminate the application
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running MS-DOS and
Microsoft Windows applications. Choose 'Close' to terminate the application
#5
Posted 28 April 2005 - 03:14 PM
That error message is normally caused by one of the following 3 files being corrupted : autoexec.nt, config.nt or command.com.
All 3 reside in the windows\system32 folder.
The easiest way to repair autoexec.nt & config.nt, is to copy them from the windows\repair folder into system32 folder. Once you've copied them into system32, right click on one of the 2 files, select properties & enable the read only attribute. Repeat for the second file.
Try & uninstall your printer again. If you still have problems, let me know & I'll tell you how to repair command.com as well, plus a different method for repairing autoexec & config, in case the ones in the repair folder were also corrupt.
All 3 reside in the windows\system32 folder.
The easiest way to repair autoexec.nt & config.nt, is to copy them from the windows\repair folder into system32 folder. Once you've copied them into system32, right click on one of the 2 files, select properties & enable the read only attribute. Repeat for the second file.
Try & uninstall your printer again. If you still have problems, let me know & I'll tell you how to repair command.com as well, plus a different method for repairing autoexec & config, in case the ones in the repair folder were also corrupt.
#6
Posted 29 April 2005 - 02:16 PM
tried that but the task keeps not responding is there any other way to get rid of it?
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users