Slowdown on K8NE-Deluxe bootup

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

I just switched over from a SATA drive (Seagate 120GB) using the NVidia
SATA/IDE controller to an IDE (WD 80GB) drive. With the Seagate SATA the
boot time was 40 seconds. With the WD IDE the boot time is literally minutes
(4-5 minutes plus). The BIOS is basically the same for both drives since
they use the onchip controller. The ONLY difference is the drives!
Specifically it is the POST that is so very slow. It "hangs" on the opening
screen with the drive listing, then it "hangs" with the flashing cursor just
before W2K loads. W2K loads just fine (and fast) and everything runs just
fine. Is it the IDE drive that slows the POST or is it the fact that this is
a WD drive? Just wondering. Any ideas?

Skippi

PS I have gone into the BIOS to check any settings that might be affecting
this. I specifically have "fast boot" enabled.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

skippi wrote:
> I just switched over from a SATA drive (Seagate 120GB) using the NVidia
> SATA/IDE controller to an IDE (WD 80GB) drive. With the Seagate SATA the
> boot time was 40 seconds. With the WD IDE the boot time is literally minutes
> (4-5 minutes plus). The BIOS is basically the same for both drives since
> they use the onchip controller. The ONLY difference is the drives!
> Specifically it is the POST that is so very slow. It "hangs" on the opening
> screen with the drive listing, then it "hangs" with the flashing cursor just
> before W2K loads. W2K loads just fine (and fast) and everything runs just
> fine. Is it the IDE drive that slows the POST or is it the fact that this is
> a WD drive? Just wondering. Any ideas?
>
> Skippi
>
> PS I have gone into the BIOS to check any settings that might be affecting
> this. I specifically have "fast boot" enabled.
>
>

Check the drive jumpers - I think some WD drives have a different jumper
setting for "master, slave present" and "single drive", and if you set
it to the former without a slave drive, it may cause this due to the
drive waiting for the non-existent slave to complete diagnostics.

--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Thank you, thank you, thank you!!!

That solved it! I don't remember ever having a WD be so picky (i.e., slowing
down the system) before, but setting it to "single" did the trick. Now the
system boots up in 30 seconds.

Skippi