Boot from the XP CD. Ensure your BIOS is set to look for bootable devices
in the following order FDD, CD, HDD (floppy, CD hard drive).
When the message appears on the screen:
Press any key to boot from CD.....
Press a key.... any key, even the spacebar.
Let it run... ignore the F2 for the Recovery Console... go through the F8 to
accept the EULA. When Windows looks for and finds itself on thehard drive,
it will ask if you'd like to do a Repair Installation.
All the remainder of your files, folders, documents, MP3s, videos, whatever
else you have on there will be just fine. However you will have to download
and install SP1 and the rest of the Updates since the release of XP.
Cari
www.coribright.com
"Falco98" <(E-Mail Removed)> wrote in message
news:-(E-Mail Removed)...
> A few days ago after some random crash / reset, my PC seems to have
started
> having some strange problems.
> First off, I'm running XP sp1 on an Athlon XP 2000 system with 512 megs of
> ram, Audigy2, ATI video card.
> It started reporting that some essential system process had failed
(SVChost,
> i think), and that it would restart in 59 seconds. I figured out how to
> disable that mandatory restart in System Management, but that only seems
to
> buy me time and not stability. At some point, after one restart, Windows
> reported that I should throw in the XP cd, since some system files didn't
> match the originals (this is after the one time it did a ScanDisk during
> start up). I, being hasty, told it to 'ignore', but now I can't run
windows
> for more than a few minutes without svchost crashing (it simply reports
the
> error over and over again, as I told it to "restart on fail" in windows
> management). This seems to do all kinds of inconvenient things to the
file
> system, too.
> Now, my primary question is, How can I get back to the thing that asks me
to
> insert my XP cd so it can patch damaged system files? I've tried putting
> the CD in anyway and fishing through the obvious options, but that didn't
> really work. And, my secondary question is, could this error be caused by
> something else? (the SVChost crash errors are always accompanied by a
> memory address read error. it's rather intriguing).
> Thanks to anyone who can help.
> ~Mike
>
>