Alan T said:
My XP SP2 has a serious problem:
It got hang a couple of times and I need to 'reset' it, now when it pass
the POST and prompt me the following file is corrupted, told me to press
'r' to repair the system file using the original XP CD.
I boot from my XP cd and run the setup until came up to the selection
screen. I chose 'R' and got to the dos screen.
I have no idea how to do the repair in this dos screen.
Colin Barnhorst said:
You need to go past that to the second "R". The first is not what you
want.
Alan T said:
So are you saying I should go to the 'XP install'? Then 'Repair' at some
point during the 'Installation'?
Just wonder if I choose 'Install' to the partition C, will it overwrite my
original Windows?
GreenieLeBrun said:
Alan T...
Hopefully the information you rec'd from the above responders has solved
your problem but just let me add a bit more info concerning the XP Repair
process as it pertains to your situation...
First of all, the following assumes that your problem lies with a corrupted
XP OS and no hardware-type issues are involved that are causing your
problem.
But before getting to the Repair install...
In your original post you stated that during the boot you get a message that
"the following file is corrupted". What "file" is that?
In any event, before you undertake a Repair install of the OS, try the
following...
Access the Recovery Console see -
http://support.microsoft.com/kb/314058
and enter the chkdsk /r command. Perhaps you'll be lucky and the chkdsk
repair process will correct any existing OS corruption to the point where
the drive will become bootable & functional once again.
Assuming the chkdsk command does not correct the problem, it probably would
be wise to run a Repair install of the XP OS. I assume you've never done
this before so here's some general info on the process...
Undertaking a Repair install of the OS is a relatively straightforward
process. It would be roughly akin to making a fresh install of the OS, but
in nearly every case your existing programs & user-created data would be
retained. Notice I said "nearly". While it would be a rather rare situation
where data would be lost or corrupted as a result of the Repair install
(even if the Repair install failed), and as unlikely as it may be, it
*could* happen. As a matter of fact it's not unheard of that further data
corruption could be caused by using the chkdsk command referred to above.
Again, it's a relatively rare event that a loss or corruption of data will
occur even when the chkdsk /r command or Repair install is unsuccessful, but
it *can* happen. So I want you to be aware of this.
There are a number of websites that contain step-by-step instructions for
undertaking a Repair install. Let me assure you that it's not a difficult
process and not terribly time-consuming. It's roughly similar to making a
fresh install of the XP OS. If you do a Google search on "XP repair
install", you'll be pointed to many of these sites. Here are a few more
besides the Michael Steven's site GreenieLeBrunone provided you with...
http://www.webtree.ca/windowsxp/repair_xp.htm
http://www.geekstogo.com/forum/index.php?showtopic=138
http://www.windowsreinstall.com/winxppro/installxpcdrepair/indexfullpage.htm
Assuming the chkdsk process or Repair install is successful (or you're able
to use some other process to get back your HDD to a bootable, functional
state), you should use your A-V program to immediately check out your PC for
any virus infestation. Also, you will need to download/install *all* the MS
critical updates since SP2 following a successful Repair install. (I'm
assuming that if you undertake this Repair install of the XP OS, you will be
doing so with a XP installation CD that contains SP2). That, of course, is
one of the downsides re undertaking a Repair install in that it's usually a
onerous task to download all the Critical Updates from MS especially if you
have a dialup phone connection rather than broadband.
Just one other thing...
It is conceivable that you're dealing with some hardware-type problem here
and not just a corruption of the OS. Where a hardware-type problem is the
culprit in cases like the one you describe, it's usually the HDD that's
defective although it's entirely possible some other major component of your
system may be at the root of the problem you're experiencing. In any event,
it's possible that you may be dealing with a defective HDD so it probably
would be wise at this point to check out the HDD with a HDD diagnostic
utility you can (usually) download from the website of the disk's
manufacturer. It's very easy to use - the downloaded program allows you to
create either as a bootable floppy disk or bootable CD containing the HDD
diagnostic program. So give that some consideration.
Anna
