Crashman, Here's what happened:
I startet this entire spiel again, formatting, copying files over, preparing for Win XP to start and reboot. I took the CD out and set the BIOS to boot with the HDD. Result: disk read error, restart. Tried it 3 times, same result. The HD is about 4 weeks old, ran the Maxtor utility, no problems with the drive. For some reason, the hdd can not be read.
This is exactly the same message that I got about a month ago, when my old HDD crashed. I installed this new one and had not problems to install win XP pro. It ran for about a week and then the PC froze and could not be started again. That was when I posted the message about the ongoing beeping. Now that I have the Asrock board and the Athlon installed it seems that the HDD is crashed again. Is it possible that a bad CPU can damage a drive so it cannot be read anymore? Would a low-level format help? Thanks for all the help.
Ed
I startet this entire spiel again, formatting, copying files over, preparing for Win XP to start and reboot. I took the CD out and set the BIOS to boot with the HDD. Result: disk read error, restart. Tried it 3 times, same result. The HD is about 4 weeks old, ran the Maxtor utility, no problems with the drive. For some reason, the hdd can not be read.
This is exactly the same message that I got about a month ago, when my old HDD crashed. I installed this new one and had not problems to install win XP pro. It ran for about a week and then the PC froze and could not be started again. That was when I posted the message about the ongoing beeping. Now that I have the Asrock board and the Athlon installed it seems that the HDD is crashed again. Is it possible that a bad CPU can damage a drive so it cannot be read anymore? Would a low-level format help? Thanks for all the help.
Ed