Hi all

My son ran a repair instal on his pc because it was bluescreening rather too much. His machine runs an up-to-date genuine XP with a Norton AV/internet security suite installed. Like a typical teen it was used for gaming and college work.

When he ran the repair instal option the machine loaded file to the machine, restarted and began the instal. About 10 minutes into the instal the machine froze he left it for a while and repeated the steps, noting that the instal now detected an earlier incomplete instal.

Eventually it started but all he has is a black background with a moveable cursor. Alt+ctr+del does nothing and safe mode does basically the same bar the blurb that tells you it's safe mode.

I ran the recovery console and tried to use bootcfg to see if we could find a way of firing to a more workable windows but to no avail. I tried running the instal again using the XP based drivers for the SATA drive and also using the F6 to use the Promise driver supplied with the MB.

The machine laods files to the drive to start the instal, resarts but then attempts to load Windows, bypassing the installation process.

How can I either

1 Complete the instal without destroying his data. He has a backup device but neglected to keep it up to date. He is 12 weeks out of date, with important(college) work on there which could lead him to failing his college course.

2 Remove the data safely to do a format/instal?

any help gratefully received



10 Years
Discussion Span
Last Post by Suspishio

The current HDD can be placed into an external USB enclosure, attached to a second PC and the data you need can be streamed off by normal windows copy means.

Then you can format the drive on the second PC and do the clean install from the Windows CD in the PC concerned.



It is an option as you rightly point out, i'd need to pick up an external enclosure(not a problem).

Still curious why it wont restart the repair instal option though. I wonder if there is a file or folder I can delete to allow the process to restart?




This is the big problem di\gnosing at a distance. We don't have the PC in our hands.

Blue screens occur for a variety of reasons, including:

- Kernel Memory clashes with a device driver
- Damaged software like due to a virus/trojan
- Damaged boot sector for any reason

You could spend the rest of this month sorting it out. So You were on the right track; get the data off, wipe the disk properly and rebuild your software environment.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.