- Feb 28, 2006
- 4
- 0
- 0
The daughter of a friend has an XP Home that now hangs during boot-up with
"Windows could not start because the following file is missing or corrupt:
\WINDOWS\SYSTME32\CONFIG\SYSTEM
You can attempt to repair this file by starting Windows Setup using the original Setup CD-ROM.
Select 'r' at the first screen to start repair."
It doesn't give an actual file name, just the directory.
She doesn't have an "original Setup CD-ROM". She has a
"Quick Restore CD
For Distribution Only With A New CTL PC.
V.WXPHome2002"
("CTL" == Computer Technology Link)
The CD warns that its use "will result in the loss of all programs, configuration & data currently on your computer. ...".
The PC (a hand-me-down from her step sister) worked well for her for a year or two, but recently began giving her error messages at start-up (perhaps mentioning a driver problem (? She can probably clarify this 7/29 when she returns from runners' camp)). Now it has escalated to the point that it will not boot-up.
So far as can be recalled, no software was installed or modified immediately prior to the messages' appearance.
She has stuff on it that she doesn't want to hose (including hundreds of $ in iTunes) or re-install (quite a few apps) via a new XP installation.
She doesn't have any Recovery disk(s) -- didn't know they are can be made. One of the first things we'll do once her system is working properly again.
I've been able to plug the HD into another XP Home system. The programs I've tried running from it work OK.
Examining the HD with Explorer shows that the ONLY possible way to complete the directory\filename portion of the boot-up error message is "\WINDOWS\SYSTME32\CONFIG\SYSTEMPROFILE" etc, so it's probably hit a buffer length limit which trims it to "\WINDOWS\SYSTME32\CONFIG\SYSTEM".
Would this error message be written to disk somewhere also? It might not be truncated there. If so, having the entire path+filename, might enable me to place the file there (if missing) or replace it (if corrupt).
If it's written somewhere, where would that be?
If not, is there some other way to get at the full path+file string from the error message?
Another possibile fix would be to run a disk scan on the HD from the malfunctioning system. Is this a good idea?
System Information lists both HDs -- the working system's & the "transplanted" one -- as running NTFS. If this is true (I'd heard that XP Home does not support NTFS), might NTFS's log contain helpful info?
If so, where would that log be?
If there are other options for us, what are they?
If we could borrow someone else's XP Home "Setup CD-ROM" could we attempt a repair? Would it have to be a CTL Setup CD?
(An aside: Is the CTL "Quick Restore CD" an OEM CD?)
Sorry if this is too basic. I guess you all were noobs at some point also.
Anyway, thanks for any advice anyone gives.
Warren
"Windows could not start because the following file is missing or corrupt:
\WINDOWS\SYSTME32\CONFIG\SYSTEM
You can attempt to repair this file by starting Windows Setup using the original Setup CD-ROM.
Select 'r' at the first screen to start repair."
It doesn't give an actual file name, just the directory.
She doesn't have an "original Setup CD-ROM". She has a
"Quick Restore CD
For Distribution Only With A New CTL PC.
V.WXPHome2002"
("CTL" == Computer Technology Link)
The CD warns that its use "will result in the loss of all programs, configuration & data currently on your computer. ...".
The PC (a hand-me-down from her step sister) worked well for her for a year or two, but recently began giving her error messages at start-up (perhaps mentioning a driver problem (? She can probably clarify this 7/29 when she returns from runners' camp)). Now it has escalated to the point that it will not boot-up.
So far as can be recalled, no software was installed or modified immediately prior to the messages' appearance.
She has stuff on it that she doesn't want to hose (including hundreds of $ in iTunes) or re-install (quite a few apps) via a new XP installation.
She doesn't have any Recovery disk(s) -- didn't know they are can be made. One of the first things we'll do once her system is working properly again.
I've been able to plug the HD into another XP Home system. The programs I've tried running from it work OK.
Examining the HD with Explorer shows that the ONLY possible way to complete the directory\filename portion of the boot-up error message is "\WINDOWS\SYSTME32\CONFIG\SYSTEMPROFILE" etc, so it's probably hit a buffer length limit which trims it to "\WINDOWS\SYSTME32\CONFIG\SYSTEM".
Would this error message be written to disk somewhere also? It might not be truncated there. If so, having the entire path+filename, might enable me to place the file there (if missing) or replace it (if corrupt).
If it's written somewhere, where would that be?
If not, is there some other way to get at the full path+file string from the error message?
Another possibile fix would be to run a disk scan on the HD from the malfunctioning system. Is this a good idea?
System Information lists both HDs -- the working system's & the "transplanted" one -- as running NTFS. If this is true (I'd heard that XP Home does not support NTFS), might NTFS's log contain helpful info?
If so, where would that log be?
If there are other options for us, what are they?
If we could borrow someone else's XP Home "Setup CD-ROM" could we attempt a repair? Would it have to be a CTL Setup CD?
(An aside: Is the CTL "Quick Restore CD" an OEM CD?)
Sorry if this is too basic. I guess you all were noobs at some point also.
Anyway, thanks for any advice anyone gives.
Warren