Replacement Hard Drive Error

I put my son's hard drive into my system as I recently rebuilt a new system.
His drive worked in his older machine, but when I tried to boot after putting in my old case - (Used my existing Board, Chip, etc) I get a "Disk Read Error" - Press Cntl+Alt+Dele to reboot.
Machine will not boot at all to OS.

Any help is appreciated.
Bios Setup? - (Bios sees drive when I check Boot Sequence)
Jumpers on drive? (Has always been Master.)

How can I bypass if possible and possibly try and repair?

Thanks.

Jstut

Is this drive connected as a "Secondary Master"?
Are you just trying to read the data ? or boot to it?

Trying to boot to it.
I moved my old drive to my new machine and was trying to simply switch kids drive into my old one.

Well ordinarily unless you are very very very lucky you cannot move a harddrive on one set of hardware to another system with different hardware and boot it.
Thats a very good way to corrupt all the data on the harddrive.
If its XP you need to do a repair install.

Yes, believe I did same with my drive when replaced.
I don't think kid has his original disk.
Can I use my XP with his code from machine?
Do I just boot from disk or is there another way to effect the repair install?

Depends if the versions are the same
if you google
"Windows XP Repair Install"
Thats hould give you a tutorial.

I reset bios to boot CD first, but still getting "A disk read error occurred". Have an XP disk in drive.
How Can I get into anything for a starting point?

Make sure the drive is the first one (or the only one) in the boot sequence.
Remove any floppy/usb drives.
Leave only that drive connected to the computer. If it's IDE set the jumper(s) for cable select, put it at the end of the cable and do not connect anything else on that cable. Check that the connectors are properly inserted, try another cable.
If it's a SATA2 drive look at the documentation/issues, some REQUIRE a jumper to be set if plugged in a SATA1 port.
If it's IDE and over 138GB, some older BIOSes do not support such drives (may detect but not work).

Another note: if the drive was on a RAID controller (not necessarily in a RAID array) you may have the issue you are describing, only fix is cloning to another drive connected to a "standard" SATA/IDE port.

Not worth effort on machether.

Thanks for the attempts though.

I built my new one.
Think kid's drive is ancient.

Prob just get different HD, or help him put another sys together. Over 6 years old. In dog years, I think that's 207.

I got SIG! lol. (and Baretta). :)