[Solved] New harddrive installation issue

LittleT85

Junior Member
Apr 1, 2006
1
0
0
So I bought a new Seagate Barracuda 7200.9 500GB SATAII hard-drive, however the installation was a little bit more tricky.
When I connect it and enter the BIOS (pressing del during boot), after a boot without it, everything seems fine. The new harddrive shows up in the bios and even the capacity is shown correctly. However if I don't enter BIOS and the boot continues all I get is a black screen (no Windows XP start-up bar), but the display is still getting a signal.

If after this I reeboot the computer the boot halts on "Detecting IDE devices...", however only after the real IDE devices have been identified (2x IDE harddrive and 2x IDE DVD-ROM/RW), the error identification led on the motherboard shows error 75; "Detect & Install all IDE devices: HDD, LS120, ZIP, CDROM...". So basically, the bios has no problem detecting the new HD during the first boot, but hangs on the second boot trying to identify the same (new) HD.

The SATA drivers should be up-to-date, since the nForce driver I have are version 5.10 and the latest on nVidias site are 5.10. I also have a SATAI drive already connected to the mobo, and that works just fine. SATAII HD:s should work with SATAI mobos, but with lower transfer speeds, correct?
Anyway my system setup (BIOS channels).

Epox 8RDA + PRO nForce 2 Ultra 400
AMD Athlon XP 3000+ Barton @ 2167 MHz
Club 3D Radeon 9700 Pro
2x 512 MB Corsair DDR400
Hitachi Deskstar 120 GB (IDE0 Master)
Maxtor DiamondMax Plus II 250 GB (IDE0 Slave)
Plextor PX130A DVD-ROM (IDE1 Master)
LG 4163B DVD+/-RW DL (IDE1 Slave)
Seagate Barracuda 7200.8 400 GB (IDE2 Master) SATA1
Seagete Barracuda 7200.9 500 GB (IDE3 Master) SATA2
Antec P160 E
Antec Neo HE 550 - 550W

If anyone has any ideas on how to fix this, please help soon.

Solution: For some unknown reason, by switching the SATA harddrives (old one to SATA2-cahnnel, the new one to the SATA1-channel) Windows booted without a glich and I was able to format the new drive. I have no idea why this worked, but as long as it keeps working, it doesn't really matter does it.
 

tw1164

Diamond Member
Dec 8, 1999
3,995
0
76
Does the problem stop when you remove the new drive? Have you tried to boot up w/o being OC'd?