I attempted to install Windows XP in the second partition, but I wasn't able
to make the second partition the active partition without deleting the the
first partition, so I aborted.
I then brought up the Recovery Console and used the FIXBOOT command to try
to re-create the MBR on the first partition. When I executed the MAP
command, I could see the first partition now identifying itself as being
formatted in NTFS but it still wouldn't boot up. I then ran CHKSK /R-
several times, but it kept aborting at around 70%. When I reran MAP, the C:
drive wasn't visible at all. I reran FIXBOOT then MAP and it was again
visible as an NTFS partition. I then tried to re-install Windows XP on the
C: drive hoping I would get the Repair Option, but the only options I was
given were to either Quick or Full Format the drive.
I have another unused PC with a 25gb Maxtor HDD in it. My next approach is
to remove the Maxtor and install it in the broken PC as the Master Primary
and install Windows XP on that drive and attempt to use the Data Recovery
apps GTS suggested to try and save my daughter's Power Point project.
Linda, I'm sorry but I don't have a clue as to how to resolve your problem.
I do suggest however, that you separately post your problem in this forum.
That way you might get a specific response from someone who can help.
Thanks again to the rest of you.
Russ
Linda Creole said:
I had the same problem but got rebooted from Window XP boot disk and typed
R. I had to do it twice for the computer to boot up, but now I get the
following error on my program called megamud (just a script program to play
majormud):
[Telnet Error 0000274D (Connect)]
[Connection refused.]
WSOCK32.DLL loaded.
[Telnet Error 0000276B (CreateSocket)]
[Network subsystem is unavailable.]
Not sure what is causing it. Anyone have any ideas?
Russ said:
Booting from the hard drive is impossible right now (at least I sure don't
know how to do it). Once the BIOS info is displayed, then next screen has
the following:
"windows could not start
because the following file is missing or corrupt:
\windows\system32\config\system"
So I'm booting from the Windows XP OEM Home CD and entering "R" once the
Windows XP install screen comes up to get to the Recovery Console.
My current plan is to make the 2nd partition on that hard drive, which is
the D: drive, the active partition and to install Windows XP into that
partition. After the Win XP install (if all goes well), I'll establish an
Internet Connection and download the Data Recovery application you
suggested.
Hopefully the data recovery Help Files are explanatory enough to guide me
through the process.
I don't have time to do that tonight so I'm probably take on the task
tomorrow. But whatever happens, I'll repost here and let you and Carey
know
what the outcome was.
Thanks again.
Russ
:
A hacker could cause damage to data (including registry files) if a PC is
not properly secured, but could not physically damage the hard drive.
The
behavior you describe of the chkdsk is unusual. Are you booting from an
XP
CD or from a hard drive installation of RC?
--
Since the time I posted this, I've rebooted to the Win XP Recovery
Console
and ran CHKDSK /R-. In fact I've run it three times because the
command
keeps aborting and stating that the disk has unrecoverable errors. The
CHKDSK status bar will climb to around 70% then revert back to 50% then
abort
at around 58%. I know this sounds like my daughter crashed the hard
drive
and that may be true, but the circumstances just seem too coincedental
to
me.
She was in a Chat Room where some idiot kept making sexual remarks to
her.
She finally had had enough a typed a rude comment back to this
individual.
He/she said that they would fix her wagon, minutes later her PC locked
up
and
then spontaneously rebooted. That's when the Corrupt Config File
messages
began showing up. Could some talented(?) PC person actually crash and
damage
a hard drive by hacking into someone else's computer? Anyways, I'm
still
stuck and would surely appreciate any help that anyone in this
community
could provide me with.
Thanks. Russ
:
While starting Windows XP error message appears, "windows could not
start
because the following file is missing or corrupt:
\windows\system32\config\system"
I've printed article 307545 "How to recover from a corrupted registry
that
prevents Windows XP from starting", but the article warns those with
OEM
installations to not use this approach for recovery. I have an OEM
Windows
XP installation. Am I just tough out of luck? Would I be foolish to
try
the
recovery process as detailed in this article? The article states that
if
I
use this procedure, I MAY not be able to log back into the Recovery
console.
My daughter has a college assignment on that PC that wasn't backed up,
and to
her it's priceless. Can someone help me??