Question Locked

WinXP boot problem should be simple but has me stumped!!!!!

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Okay, I moved a client's hard drive from an old computer to a newer one I had around. Tried to boot it but past the bios it just gave me a blinking cursor. Tried a recovery console fixboot/fix mbr, still nothing. Started a repair install, when it restarted to continue, still the blinking cursor. Made a boot disk with a boot.ini
ntdetect, etc. and it booted back into the install and finished, rebooted still the blinking cursor. Used the boot disk and it loads into Windows fine. Checked to make sure the partition was active. Checked the boot.ini, etc., everything fine. Reboot and without the boot floppy in, still the blinking cursor!! Has anybody got any ideas on this? Boots fine with the floppy but not without! -Kelly

4 replies

by ozi eagle

Hi,

Moving disks with XP or W2K is difficult because they are hardware "tuned". They look for specific drivers to be able to use the ide ports to enable the boot. Having moved the HDD to another computer means that XP can't find the correct drivers and can't load.

You may be able to get around this problem by reinstalling the HDD in the original computer, booting it up and when XP is running go to device manager and change the IDE drivers to the windows default. These will run on any motherboard, but won't be as good as the specific ones for that mobo.

Install the HDD into the new computer and when (if) XP boots load the mobo specific drivers.

Good Luck

Herb

by grassiap

if using the generic IDE drivers doesn't do the trick here is what I would recommend :

- if you've not done it already make a disk image of yout client's HDD

- make sure you've got all the drivers needed for the new PC on a removable media (CD, USB stick...)

- get sysprep from MS website.

- check it doc for options, especially in order not to void the activation (or you'll just have to provide the product key and redo the activation) and run it on the old HW. When it is done, it will have removed all hardware dependencies on the current install and setup a minimal boot environment, similar to the one during the final stages of the normal install, do not reboot, just shutdown

- move the disk to the new PC

- start up.

- provide the drivers when required, reboot. Unless there are strong dependencies to the hardware all the apps should be still running. You will probably have to re define the local users, register the PC in the domain and apply policies (this can be captured or preserved when you are running sysprep the first time, but the script can be touchy to tune up)

plan 2-3 hrs for that. If it does not work, it most probably means that the original XP was an OEM that checks for some BIOS/MB tatoo and that your new PC doesn't have it. If this is the case you'd better backup the data and install from fresh on the new PC.

HTH

by imfineru

Just tor let you know I saved all data and did a fresh install (which is the way to go anyway) and everything's hunky dory. The IDE drivers were updated Intel drivers. Appreciate the response guys, The Sysprep tool will come in handy for next time. -Kelly

This discussion is closed to new replies.