Hi all. I've an ASUS A7V based computer with a Duron 900, Maxtor 30GB HD,
GeForce video card, Afreey CD-ROM, SoundBlaster Live!, PowerMan 235W PSU
and a NetGear NIC. Recently, it started to fail to boot with a Disk Boot
Failure message (does not detect the drive) and will emit a beep-beep
followed by a pause, then another beep-beep, and so on. I've tried the
onboard Promise ATA 100 controller as well as the "standard" controller with
equal results: It will boot a few times and then resort to the failure
message and beeps. I also got the same results after replacing the IDE
cable. S.M.A.R.T. does not report any problems when the drive is detected,
and when it does boot, it runs WinXP just fine. Temps and voltages seem to
be OK in the BIOS.

Any ideas? I'd like to get some feedback before I start throwing new parts
at it. Thanks for any replies.

WW

If you have important information on that drive make sure you back it up
because very soon you will need a new Hard Drive!
"WaterWatcher" <(E-Mail Removed)> wrote in message
news:EQx3c.532435$na.1320699@attbi_s04...
> Hi all. I've an ASUS A7V based computer with a Duron 900, Maxtor 30GB HD,
> GeForce video card, Afreey CD-ROM, SoundBlaster Live!, PowerMan 235W PSU
> and a NetGear NIC. Recently, it started to fail to boot with a Disk Boot
> Failure message (does not detect the drive) and will emit a beep-beep
> followed by a pause, then another beep-beep, and so on. I've tried the
> onboard Promise ATA 100 controller as well as the "standard" controller
with
> equal results: It will boot a few times and then resort to the failure
> message and beeps. I also got the same results after replacing the IDE
> cable. S.M.A.R.T. does not report any problems when the drive is
detected,
> and when it does boot, it runs WinXP just fine. Temps and voltages seem
to
> be OK in the BIOS.
>
> Any ideas? I'd like to get some feedback before I start throwing new
parts
> at it. Thanks for any replies.
>
> WW
>
>

"Geek" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> If you have important information on that drive make sure you back it up
> because very soon you will need a new Hard Drive!

Well, the drive slaves to a Western Digital in another computer and seems
just fine. I ran diagnostics including Maxtor's PowerMax and all came up
OK. I did back up the critical data.

I'm now thinking it's the motherboard. I've never heard of another
component that would cause a hard disk to not be detected.

WW

> "WaterWatcher" <(E-Mail Removed)> wrote in message
> news:EQx3c.532435$na.1320699@attbi_s04...
> > Hi all. I've an ASUS A7V based computer with a Duron 900, Maxtor 30GB
HD,
> > GeForce video card, Afreey CD-ROM, SoundBlaster Live!, PowerMan 235W
PSU
> > and a NetGear NIC. Recently, it started to fail to boot with a Disk
Boot
> > Failure message (does not detect the drive) and will emit a beep-beep
> > followed by a pause, then another beep-beep, and so on. I've tried the
> > onboard Promise ATA 100 controller as well as the "standard" controller
> with
> > equal results: It will boot a few times and then resort to the failure
> > message and beeps. I also got the same results after replacing the IDE
> > cable. S.M.A.R.T. does not report any problems when the drive is
> detected,
> > and when it does boot, it runs WinXP just fine. Temps and voltages seem
> to
> > be OK in the BIOS.
> >
> > Any ideas? I'd like to get some feedback before I start throwing new
> parts
> > at it. Thanks for any replies.
> >
> > WW
> >
> >
>
>

"WaterWatcher" <(E-Mail Removed)> wrote in message
news:Ixb4c.11100$C51.68633@attbi_s52...
>
> "Geek" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > If you have important information on that drive make sure you back it up
> > because very soon you will need a new Hard Drive!
>
> Well, the drive slaves to a Western Digital in another computer and seems
> just fine. I ran diagnostics including Maxtor's PowerMax and all came up
> OK. I did back up the critical data.
>
> I'm now thinking it's the motherboard. I've never heard of another
> component that would cause a hard disk to not be detected.
>
New motherboard fixed it.

WW