|
|
 |
|
|
Pages: 1
A little toughie for ya...
(Click here to view the original thread with full colors/images)
Posted by: Tomcat-
Ok, I had this problem a while ago but I have since solved it. The reason I am posting anything about it is because I don't know exactly WHY it worked. Allow me to explain...
I had taken a 40GB hard drive out of an old Compaq, and was planning on inserting it into my desktop. This desktop had, at the time, two hard drives (an 80GB deskstar, and a 3GB fireball (  )). So I replace the 3GB Hard Dive with the 40Gb hard drive. When I reboot, it loads the old Win98 from the 40GB (I had forgotten that the 80GB was on cable select and had been moved to slave, while the 40GB was no occupying the master (0) slot). So I rearrange the two hard drives so that all of the pins and the cables and such are in the proper position to boot from the 80GB hard drive, with the 40GB being a slave.
I boot up, and I get the scary message "Broadcom... No bootable media detected". I panic. As many of you can understand, that 80GB hard drive felt like my LIFE! So I took out the 40GB, and prayed to God for it to work. No such luck. It was set as master, it was all by itself, and therefore should have worked. Yet, it did not. But the odd thing is that whenever I set it up so that the 80GB was device 0, and the 3GB was my slave, it worked like a charm! Confused and determined to get that 40GB in there, I back up my stuff onto a laptop via LAN. At this point I was willing to try anything, so after fiddling around in the BIOS for a while, I decide to reset the BIOS settings. I do this, with just the 80Gb hard drive in, it works!!! It loads perfectly, no errors or bugs (besides the fact that it gave me the blue screen twice because of the fact that the hard drive was situated in such a way that the spinning was being affected  ).
So WHY did resetting the BIOS settings allow me to rearrange the configuration of my hard drives (so that in the future, I will look MUCH MUCH more knowledgeable)?
Posted by: redwench
theres a few settings in the bios that could do it, from the boot sequence to the autodetect. also, the master/slave/cable select settings are touchy as well. if its alone on the cable, it might require cs rather than master. its a mystery which combination was the problem 
|
|
|
|
|
