XP Problem
Thread Starter
Join Date: Apr 2004
Location: The 245 bulkhead
Posts: 62
Likes: 0
Received 0 Likes
on
0 Posts
XP Problem
Hi,
I'm wondering if anyone can help please. We have an Acer Desktop PC at home P4 3.2ghz, 1gb of ram with Xp home ed updated with SP2. The pc has an OEM disc with it, not an XP disc.
The problem is every time the pc starts a pop up box appears titled 16 bit MS-DOS Subsystem, that contains the following:
C: \WINDOWS\system32\Debug.exe
C: \WINDOWS\SYSTEMS32\AUTOEXEC.NT. The stystem file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
There is a close and ignore button.
Clicking either of the buttons will make the box go away, but at next startup its back. We've done a google search and tried several of the suggestions but none seem to help. The problem appered about 2 weeks ago all by itself, and before the SP2 upgrade.
Does anyone have any ideas or cures for this one?
Thanks in advance.
LPS
I'm wondering if anyone can help please. We have an Acer Desktop PC at home P4 3.2ghz, 1gb of ram with Xp home ed updated with SP2. The pc has an OEM disc with it, not an XP disc.
The problem is every time the pc starts a pop up box appears titled 16 bit MS-DOS Subsystem, that contains the following:
C: \WINDOWS\system32\Debug.exe
C: \WINDOWS\SYSTEMS32\AUTOEXEC.NT. The stystem file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
There is a close and ignore button.
Clicking either of the buttons will make the box go away, but at next startup its back. We've done a google search and tried several of the suggestions but none seem to help. The problem appered about 2 weeks ago all by itself, and before the SP2 upgrade.
Does anyone have any ideas or cures for this one?
Thanks in advance.
LPS
The Oracle
Join Date: Aug 2001
Location: Naples, Florida U.S.A.
Posts: 2,902
Likes: 0
Received 0 Likes
on
0 Posts
LPS500,
It could be that there was an error on your Hard Drive. I have seen using Recovery Console and running the command:
chkdsk drive /p /r (where Drive is the Drive Letter for your Hard Drive with your system on it.)
Can fix the problem.
Take Care,
Richard
It could be that there was an error on your Hard Drive. I have seen using Recovery Console and running the command:
chkdsk drive /p /r (where Drive is the Drive Letter for your Hard Drive with your system on it.)
Can fix the problem.
Take Care,
Richard