On Wed, 10 Sep 2003 12:03:11 GMT,
(E-Mail Removed)lid wrote:
>
>
>Brian Groose wrote:
>> I'm having a problem trying to get my "old" Western Digital 120GB
>> (WD1200BB) drive to work in my new system. If the drive is connected,
>> then the BIOS hangs while trying to detect it. If I don't power on
>> the drive until after I enter the BIOS setup, then it is detected just
>> fine, and everything works until the next time I completely turn off
>> the system.
>>
>> - I've tried several power supplies, 250W, 300W, and 380W, and that
>> didn't matter.
>> - The drive is jumpered correctly, as a single master, and WDC
>> diagnostics didn't find anything wrong.
>> - There are no other drives or cards installed in the system, just the
>> Motherboard, CPU and 120GB drive.
>> - The same problem occurs if I use an add-on ATA card.
>> - This drive still works fine if I put it in my old Athlon 650 system.
>> - A 40GB 5400RPM Maxtor drive does not exhibit this problem in the
>> system, it is detected right away.
>>
>> Right now, the system consists of:
>> - Soltek 75MRN-L motherboard
>> - Athlon XP 2500+ Barton CPU
>> - Centon 512MB PC2700 RAM
>> - WD1200BB Western Digital 120GB hard drive
>>
>> Has anyone run into a problem like this before? Any other ideas on
>> what parts to swap? I RMA'd the original motherboard because it did
>> this, but since the second one does it, I'm guessing it's something
>> else. The drive is one of the early WD 120GB drives, and not under
>> warrantly anymore.
>>
>> Thanks for any help!
>>
>> Brian
> I have seen where some hard drives do not get up to speed fast enough
>for the bios to detect the drive when looking for a hard drive. That
>might be happening here if you can detect the drive AFTER it is once
>running. If the drive is consistently detected properly after once
>having been detected by BIOS, leave power on and do a Ctrl+Alt+Del.
>Since the drive never stopped, the speed will already be up and it might
>detect it every time. If so, it would support the drive speed theory.
>One way you might overcome such a problem is to remove the Fast Boot
>option in CMOS so that it allows the drive more time to get up to speed.
>
>Ken
I don't have a Fast Boot option in this particular BIOS (that I could
find, at least). But when I power the system on, and it hangs trying
to detect the drive, then I reboot it, it still hangs after that, even
though the drive is clearly powered up at that point.
If I power the system on with auto detect disabled, I can go into the
BIOS and try to auto detect the drive manually. It still hangs in
this case, and the drive has had plenty of time to power up by then.
I've never seen anything like this before, and it's really confusing
me!
Brian