HDD detection time

On Tue, 15 Feb 2005 13:55:25 -0600, - HAL9000 wrote:

 > Are you asking how long a motherboard's bios will wait on a hard disk
 > before the bios declares that a drive is not connected?
 >
 > Forrest
 >
 > Motherboard Help By HAL web site:
<font color=purple> > <a style='text-decoration: underline;' href="http://home.comcast.net/~mobo.help/</font" target="_blank">http://home.comcast.net/~mobo.help/</font</a>>
 >
From above link.

My Hard Disk won't boot. What do I try next?

The first thing to do is isolate a Hard Disk problem from a
Motherboard problem. Try booting from a Win95/DOS floppy boot disk.
You have made a boot disk haven't you? If it successfully boots to
the floppy disk then your Motherboard is ok and you now know that the
problem is the Hard Disk or the ribbon cable leading to it. Once
booted, try a "dir c:" and see if you can read it. Ribbon cables,
especially the new 80 wire ATA66 ones, are delicate. If you have a
spare, even a spare 40 wire cable spare, try it.
----

I admire your willingness to help, but this is not right. All booting from
floppy proves is that the floppy and floppy controller works. It doesn't
test the ide controller at all which in most cases is on the MB. The
onboard IDE controller could still be bad and there's many otther reasons
why the system won't boot from the HD. None of which this test. One good
example was with some Seagate 540Meg drives I had about 10 of a while back
mostly on socket 7 MB's. Unless I left bootup floppy seek turned on in the
bios, the drives wouldn't get recognized. Turning on floppy seek delayed
the access to them long enough for the to spin up and respond. Even today
this still applies to some CD/DVD drives. Put them as the first boot
device and sometimes they won't boot properly. unless you set a delay in
the bios.

--
Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
My server <a style='text-decoration: underline;' href="http://wesnewell.no-ip.com/cpu.php" target="_blank">http://wesnewell.no-ip.com/cpu.php</a>
Verizon server <a style='text-decoration: underline;' href="http://mysite.verizon.net/res0exft/cpu.htm" target="_blank">http://mysite.verizon.net/res0exft/cpu.htm</a><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: HDD detection time 

Wes,

Thanks for the feedback. I've updated the page. With Google, detailed
comments can be added easily.

On a related note, there are a lot of new common problems that aren't
on the web page but have been discussed extensively on the newsgroup
as of late. Meaning, the page is outdated and needs to be revised.
If anyone would like to contribute please feel free to email me. My
(disposable, will only good until I start receiving spam on it) email
address is 0904spam.DeleteThis@comcast.net.

Thanks,
Forrest

Motherboard Help By HAL web site:
<a style='text-decoration: underline;' href="http://home.comcast.net/~mobo.help/" target="_blank">http://home.comcast.net/~mobo.help/</a>


On Tue, 15 Feb 2005 22:23:15 GMT, Wes Newell
<w.newell.DeleteThis@TAKEOUTverizon.net> wrote:

< snip >
 >
 >My Hard Disk won't boot. What do I try next?
 >
 > The first thing to do is isolate a Hard Disk problem from a
 > Motherboard problem. Try booting from a Win95/DOS floppy boot disk.
 > You have made a boot disk haven't you? If it successfully boots to
 > the floppy disk then your Motherboard is ok and you now know that the
 > problem is the Hard Disk or the ribbon cable leading to it. Once
 > booted, try a "dir c:" and see if you can read it. Ribbon cables,
 > especially the new 80 wire ATA66 ones, are delicate. If you have a
 > spare, even a spare 40 wire cable spare, try it.
 >----
 >
 >I admire your willingness to help, but this is not right. All booting from
 >floppy proves is that the floppy and floppy controller works. It doesn't
 >test the ide controller at all which in most cases is on the MB. The
 >onboard IDE controller could still be bad and there's many otther reasons
 >why the system won't boot from the HD. None of which this test. One good
 >example was with some Seagate 540Meg drives I had about 10 of a while back
 >mostly on socket 7 MB's. Unless I left bootup floppy seek turned on in the
 >bios, the drives wouldn't get recognized. Turning on floppy seek delayed
 >the access to them long enough for the to spin up and respond. Even today
 >this still applies to some CD/DVD drives. Put them as the first boot
 >device and sometimes they won't boot properly. unless you set a delay in
 >the bios.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: HDD detection time 

"what" <nospam.forsong74.RemoveThis@hotmail.com> wrote in message
news:curoiq$c62$1@news.kreonet.re.kr...
 >I know that hdd detection times are different by mainboard.
 > Anyone knows where i can find these information?

Sorry, but that's not the sort of thing you're going to find a record of.

Apart from anything else, the detection time of some motherboards varies
according to how BIOS options are set, which controller you use, and so-on.

It might help you more if you told us exactly why you want to know. Are you
worried that your board is taking longer to POST than it should? Are you
trying to find a board that POSTs quickly, or what?
--


Richard Hopkins
Cardiff, Wales, United Kingdom
(replace nospam with pipex in reply address)

The UK's leading technology reseller <a style='text-decoration: underline;' href="http://www.dabs.com" target="_blank">www.dabs.com</a><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: HDD detection time