I recently started my PC and immediately got into a black text screen with
the message "Can not read file \windows\system32\config\system". I ran
chkdsk once with no arguments then chkdsk /r. It reported one error. I
still could not boot my system, but after another reboot it started again
and its been running with no problems since then. I ran "Check disk local
disk (C" from "My Computer", with "Scan for and attempt recovery of bad
sectors" and no errors were reported.

Incidentally I was also unable to format a new FAT32 partition on the same
disk, to copy my backed up files to, but was able to create an NTFS
partition.

Is this likely to be a temporary glitch or should I back up (using Norton
Ghost), buy an new HD and restore my system to it? I can't afford to have a
system meltdown in the middle of a busy day.

--

MS have a work round to hopefully allow your PC to boot:
http://support.microsoft.com/default...b;en-us;307545

I have had this before myself but ended up doing a repair install:
http://www.michaelstevenstech.com/XPrepairinstall.htm

I have used the MS method on other peoples PC's and have at least recovered
data for them.
Neil
"Robert S" <robert_s@emailme.net.au> wrote in message
news:ejgNMnm7FHA.3048@TK2MSFTNGP10.phx.gbl...
>I recently started my PC and immediately got into a black text screen with
>the message "Can not read file \windows\system32\config\system". I ran
>chkdsk once with no arguments then chkdsk /r. It reported one error. I
>still could not boot my system, but after another reboot it started again
>and its been running with no problems since then. I ran "Check disk local
>disk (C" from "My Computer", with "Scan for and attempt recovery of bad
>sectors" and no errors were reported.
>
> Incidentally I was also unable to format a new FAT32 partition on the same
> disk, to copy my backed up files to, but was able to create an NTFS
> partition.
>
> Is this likely to be a temporary glitch or should I back up (using Norton
> Ghost), buy an new HD and restore my system to it? I can't afford to have
> a system meltdown in the middle of a busy day.
>
> --
>
>
>

remove_s wrote:

> MS have a work round to hopefully allow your PC to boot:
> http://support.microsoft.com/default...b;en-us;307545
>
> I have had this before myself but ended up doing a repair install:
> http://www.michaelstevenstech.com/XPrepairinstall.htm
>
> I have used the MS method on other peoples PC's and have at least
> recovered data for them.

Thanks. I'll print that out and keep it in a safe place. What do you think
the cause of the problem was in the first place? Is it likely to be a
software gremlin or is my hard drive going to go down the gurgler? It's
been working fine since I got it going again.

Those problem as I understand it is down to a corruption in the registry.
When I had the problem I had just installed a cable modem, which registered
no problem. When I restarted sometime later I got the message you had on a
black screen.
I don't think it is a failing disk mine has been OK ever since which was
around 2 years ago.

best of luck
Neil
"Robert S" <robert.spam.me.senseless@gmail.com> wrote in message
news:OBAo4Oo7FHA.3760@TK2MSFTNGP14.phx.gbl...
> remove_s wrote:
>
>> MS have a work round to hopefully allow your PC to boot:
>> http://support.microsoft.com/default...b;en-us;307545
>>
>> I have had this before myself but ended up doing a repair install:
>> http://www.michaelstevenstech.com/XPrepairinstall.htm
>>
>> I have used the MS method on other peoples PC's and have at least
>> recovered data for them.
>
> Thanks. I'll print that out and keep it in a safe place. What do you
> think
> the cause of the problem was in the first place? Is it likely to be a
> software gremlin or is my hard drive going to go down the gurgler? It's
> been working fine since I got it going again.

remove_s wrote:

> Those problem as I understand it is down to a corruption in the registry.
> When I had the problem I had just installed a cable modem, which
> registered no problem. When I restarted sometime later I got the message
> you had on a black screen.
> I don't think it is a failing disk mine has been OK ever since which was
> around 2 years ago.

Thanks. I think I'll use it as an excuse to brush up my backup system
anyway.

Robert, did you run chkdsk from the Recovery Console? That error is
usually a problem with the Registry. One of the
solutions is here in this MSKB Article.
http://support.microsoft.com/default...b;EN-US;307545

"Robert S" <robert_s@emailme.net.au> wrote in message
news:ejgNMnm7FHA.3048@TK2MSFTNGP10.phx.gbl...
>I recently started my PC and immediately got into a black text screen with
>the message "Can not read file \windows\system32\config\system". I ran
>chkdsk once with no arguments then chkdsk /r. It reported one error. I
>still could not boot my system, but after another reboot it started again
>and its been running with no problems since then. I ran "Check disk local
>disk (C" from "My Computer", with "Scan for and attempt recovery of bad
>sectors" and no errors were reported.
>
> Incidentally I was also unable to format a new FAT32 partition on the same
> disk, to copy my backed up files to, but was able to create an NTFS
> partition.
>
> Is this likely to be a temporary glitch or should I back up (using Norton
> Ghost), buy an new HD and restore my system to it? I can't afford to have
> a system meltdown in the middle of a busy day.
>
> --
>
>
>

Robert S wrote:
> I recently started my PC and immediately got into a black text screen with
> the message "Can not read file \windows\system32\config\system". I ran
> chkdsk once with no arguments then chkdsk /r. It reported one error. I
> still could not boot my system, but after another reboot it started again
> and its been running with no problems since then. I ran "Check disk local
> disk (C" from "My Computer", with "Scan for and attempt recovery of bad
> sectors" and no errors were reported.
>
> Incidentally I was also unable to format a new FAT32 partition on the same
> disk, to copy my backed up files to, but was able to create an NTFS
> partition.
>
> Is this likely to be a temporary glitch or should I back up (using Norton
> Ghost), buy an new HD and restore my system to it? I can't afford to have a
> system meltdown in the middle of a busy day.
>


How to Recover from a Corrupted Registry that Prevents Windows XP from
Starting
http://support.microsoft.com/default...b;en-us;307545

Once you've recovered, you might want to look here, as well:

How to Troubleshoot Registry Corruption Issues
http://support.microsoft.com/default...b;en-us;822705


--

Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH