IDE Delay

[B@TM@N]

IDE Startup Delay in Gigabyte board.Plz Help

 

[Nodsu]

Erm..
What about it?
You want to know what it's for?
You want to know where it is?

You know, not everyone can afford the Telepathy(TM) modules for their computers

 

[Blakhart]

If you're running a sata and a pata drive on that mobo I've seen this before. Usualy if you reboot it it will detect the pata fine. I got sick of this happening so I got rid of the pata drive and it runs just great sata only.

 

[B@TM@N]

B@tm@n

Well I've got a Gigabyte GA-8IPE1000G Mobo,everything works
fine but after memory test it takes about 6-8sec to detect any SATA
& IDE Devices..more like a delay.It's not Bios settings,Already got the latest
Bios update.Even if u disable the SATA controller and dont connect any
IDE Devices it still has a delay? Why? I've seen other ppl on the net with
the same problem.

My System Specs:

P4 3Ghz Prescott 800FSB 1mb Cache (C.I.A 7%)
Gigabyte GA-8IPE1000G-3.0 GT Edition (Intel 865PE)
2x256 DDR 400 Kingmax CL 2.5
Pixelview Prolink GeForce 6600GT AGP
120Gb Western Digital SATA
LG 4120B DVDRW

 

[RealBlackStuff]

Are all your drivers 'signed' by Windows? Would you have XP-Pro by any chance?
That mobo seems to have an issue with unsigned drivers.
Other than that, not a clue.

 

[Justin]

What would software drivers have to do with something that occurs before OS boot?


"B@TM@N": During this delay, are you seeing the diagnostics for onboard SATA raid? Is there anything you are seeing at all? Also, in BIOS, are the IDE devices set to autodetect or are they manually set?

 

[B@TM@N]

Watching over Gotham City...hey it's dark out here

No Diags
IDE Set to Autodetect
It looks like this

512Mb Dual Channel Detected
then
(6-8Sec Pause)

Primary Master - WD 120Gb
Secondary - Blah Blah

it's the pause I hate...there's is no fast boot option
in the bios

 

[Nodsu]

Set only those devices to autodetect that you actually have connected.

 

[B@TM@N]

Sigh

Sorry tried that but no luck
mayby it's a flaw in the boards design
I give up

 

[Justin]

I would suggest contacting gigabyte to see if this is a known issue with the board.