I've got an ECS nforce3-a mobo, with a brand new Raptor HDD plugged into the SATA plug.
I have a DVD R/W as Master and DVD-RAM as Slave on IDE-1
I have a WD 160gb HDD with jumper set as "master no slave present" on IDE-2
I was able to start up the PC successfully and format and partition the WD 160gb drive into 2 partitions, then did a complete backup of the Raptor drive into one of the partitions. Everything seemed to go fine.
Then, I rebooted again and it went through the normal startup stuff - detecting IDE drives (it showed the two DVD drives on IDE1, the WD160 on IDE2 and the Raptor drive on the Sata... then it goes to the black "Microsoft Windows XP" screen with the blue 'progression' bar. Then, it comes up to the blue screen "Starting Windows".. which is NORMALLY follwed by the "welcome" screen. However, it just hangs on the 'Starting Windows' screen.
If I unplug the IDE cable with the WD160 HDD, the computer starts up fine (the Raptor is the boot drive).
It's a new IDE cable (I replaced it because I thought that might have been the problem)
Is it possible that it's a problem with the mobo?
Please help!
I have a DVD R/W as Master and DVD-RAM as Slave on IDE-1
I have a WD 160gb HDD with jumper set as "master no slave present" on IDE-2
I was able to start up the PC successfully and format and partition the WD 160gb drive into 2 partitions, then did a complete backup of the Raptor drive into one of the partitions. Everything seemed to go fine.
Then, I rebooted again and it went through the normal startup stuff - detecting IDE drives (it showed the two DVD drives on IDE1, the WD160 on IDE2 and the Raptor drive on the Sata... then it goes to the black "Microsoft Windows XP" screen with the blue 'progression' bar. Then, it comes up to the blue screen "Starting Windows".. which is NORMALLY follwed by the "welcome" screen. However, it just hangs on the 'Starting Windows' screen.
If I unplug the IDE cable with the WD160 HDD, the computer starts up fine (the Raptor is the boot drive).
It's a new IDE cable (I replaced it because I thought that might have been the problem)
Is it possible that it's a problem with the mobo?
Please help!