Weird Problem!

[Imperialmajesty]

Alright, just got a new SATA HDD. Before that, I had (and still have) a 320gb SATA drive and a 500gb drive still using an IDE cable, which it shared with the DVD drive.

This is the problem, when I connect the new drive, the computer reboots, then when it gets to the detecting drives screen in the bios, it simply freezes when detecting the IDE components.
If I disconnect the 500gb IDE drive, the problem goes away, same if I disconnect the DVD drive and leave the 500gb.

So... what the hell? I guess I can simply rely on my external DVD drive and keep the 500gb drive, and switch the IDE cable when I need the DVD burner, but that isn't exactly a solution, lol.

 

[Zelig]

Try swapping all the IDE and SATA cables and/or updating the BIOS.

 

[Genocidicbunny]

Seems like its having a conflict between the slave on the IDE bus and one of the SATA devices. Try moving the new HDD to a different SATA port, looking in the BIOS for settings ( Such as SATA X functions as IDE Y or something along those lines) and try what Zelig suggested.

 

[Imperialmajesty]

Try swapping all the IDE and SATA cables and/or updating the BIOS.

First thing I always do when I have these type of problems.

 

[Imperialmajesty]

Seems like its having a conflict between the slave on the IDE bus and one of the SATA devices. Try moving the new HDD to a different SATA port, looking in the BIOS for settings ( Such as SATA X functions as IDE Y or something along those lines) and try what Zelig suggested.

Will do, hopefully it will work.

 

[Zelig]

First thing I always do when I have these type of problems.

Just to be sure, by swapping, I meant to try different cables, not to switch the current ones around... you did try different cables, right?

What's the motherboard model?

 

[Imperialmajesty]

Seems like its having a conflict between the slave on the IDE bus and one of the SATA devices. Try moving the new HDD to a different SATA port, looking in the BIOS for settings ( Such as SATA X functions as IDE Y or something along those lines) and try what Zelig suggested.

Alright, switching the port fixed the problem. Thanks a ton!!!