Thank you Duzzy for refocusing us on the BIOS - we could have spent years trying to figure out something that would not solve the issue. 
I also agree that spending money, even a few dollars/euros/yen, on a few second delay with obvious limited future use might not be worth it. I offered it as a solution if ptbg simply could not live with the prompt.
I also thought a bit more about it. Will a new IDE controller actually solve the issue or will it just be a different controller displaying a similar message?
So, here's the scoop on IDE detect timeout courtesy of Techarp. You're basically stuck with the message, although I think you might be able to limit the detect time somewhere in BIOS. I think ptbg's BIOS detect time is 5 seconds (based on a post stating a 10 second 'delay' - 2 drives, 5 seconds each). In the case of JMicron, it is 5 second increments, not 1 second. Also note that I could only find a definitive setting for AMI BIOS, not Award, so maybe there is no setting in Award.
I also agree that spending money, even a few dollars/euros/yen, on a few second delay with obvious limited future use might not be worth it. I offered it as a solution if ptbg simply could not live with the prompt.
I also thought a bit more about it. Will a new IDE controller actually solve the issue or will it just be a different controller displaying a similar message?
So, here's the scoop on IDE detect timeout courtesy of Techarp. You're basically stuck with the message, although I think you might be able to limit the detect time somewhere in BIOS. I think ptbg's BIOS detect time is 5 seconds (based on a post stating a 10 second 'delay' - 2 drives, 5 seconds each). In the case of JMicron, it is 5 second increments, not 1 second. Also note that I could only find a definitive setting for AMI BIOS, not Award, so maybe there is no setting in Award.
Cite Techarp: IDE Detect Time Out
Common Options : 0 to 15 or 0 to 30, in 1 second steps
Motherboards are capable of booting up much faster these days, with the initialization of IDE devices now take place much earlier. Unfortunately, this also means that some older IDE drives will not be able to spin up in time to be initialized! When this happens, the BIOS will not be able to detect those IDE drives and make them available to the operating system even though there's nothing wrong with them.
This is where the IDE Detect Time Out BIOS feature comes in. It allows you to force the BIOS to delay the initialization of IDE devices for up to 30 seconds (although some BIOSes allow for even longer delays). The delay gives your IDE devices more time to spin up before the BIOS initializes them.
If you do not use old IDE drives and the BIOS has no problem initializing your IDE devices, it is recommended that you leave the delay at the default value of 0 for the shortest possible boot time. IDE devices manufactured in the last few years will have no problem spinning up in time for initialization. Only older IDE devices may have slower spin-up times.
However, if one or more of your IDE devices fail to initialize during the boot up process, start with a delay of 1 second. If that doesn't help, gradually increase the delay until all your IDE devices initialize properly during the boot up process.
I have to agree - this has been a great collaborative effort. Thanks all around (I can't afford drinks all around)Common Options : 0 to 15 or 0 to 30, in 1 second steps
Motherboards are capable of booting up much faster these days, with the initialization of IDE devices now take place much earlier. Unfortunately, this also means that some older IDE drives will not be able to spin up in time to be initialized! When this happens, the BIOS will not be able to detect those IDE drives and make them available to the operating system even though there's nothing wrong with them.
This is where the IDE Detect Time Out BIOS feature comes in. It allows you to force the BIOS to delay the initialization of IDE devices for up to 30 seconds (although some BIOSes allow for even longer delays). The delay gives your IDE devices more time to spin up before the BIOS initializes them.
If you do not use old IDE drives and the BIOS has no problem initializing your IDE devices, it is recommended that you leave the delay at the default value of 0 for the shortest possible boot time. IDE devices manufactured in the last few years will have no problem spinning up in time for initialization. Only older IDE devices may have slower spin-up times.
However, if one or more of your IDE devices fail to initialize during the boot up process, start with a delay of 1 second. If that doesn't help, gradually increase the delay until all your IDE devices initialize properly during the boot up process.
Last edited:
My Computer
- Computer type
- Laptop
- Computer Manufacturer/Model Number
- HP Pavilion dv6-6c10us
- OS
- x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
- CPU
- AMD A6-3420M APU with Radeon(tm) HD Graphics
- Motherboard
- Hewlett-Packard 1805
- Memory
- 6.00 GB
- Graphics Card(s)
- AMD Radeon(TM) HD 6520G
- Sound Card
- (1) AMD High Definition Audio Device (2) IDT High Definiti
- Monitor(s) Displays
- HP W2072a 20" LCD (1600 x 900) @ 60 Hz
- Screen Resolution
- 1366 x 768 x 32 bits (4294967296 colors) @ 60 Hz
- Hard Drives
- ST640LM0 00 HM641JI SATA Disk Device
- Keyboard
- Logitech k520 wireless KB
- Mouse
- Logitech m320 wireless mouse (bundled with KB)
- Internet Speed
- 15/5 | 54 MB Wireless 'n'
- Antivirus
- Realtime: Defender or Avast | On-demand: Malwarebytes, ESET
- Browser
- IE 11 on Win8, IE 10 on win 7
- Other Info
- Media: [Gimp, Audacity, VLC] || Comm: [WEmail 2012, Skype] || Productivity: [OpenOffice,| Textpad] || Utils: [Sysinternals, cCleaner, Speccy, Defraggler]