IDE HD getting put in PIO mode

[araczynski]

setup:

IS7/2.4@3.3/1GB Geil/6800gt/audigy2zs/cdburner/dvd/IDE seagate 160 on SATA1/IDE Maxtor 160 on SATA2/XPproSP2

The seagate (c:\) works perfectly whether in 'normal' mode or in safe mode. The Maxtor gets pushed down to PIO in normal mode and seems to show up fine when windows is in safe mode. HDTach confirms findings for the normal mode, haven't bothered with HDTach yet in safe mode. PIO mode is being determined by the Device Manager's Primary/Secondary IDE channel advanced settings.

At least the safe mode findings tell me that there's nothing wrong hardware wise.

I have the latest IS7 bios and drivers according to their site, as well as latest drivers for everything else.

Haven't looked in event viewer yet to see if anything fishy's in there...

funny thing is that i noticed my work computer is doing the same damn thing now, in normal mode all my drives show as PIO, dagnabit....

there's a really detailed registry editing page out there that i followed to clean out a few registry keyes to force windows to reevaluate the channells and hopefully find them as UDMA, but it hasn't seemed to help anythign in my case.

Could there be some issue with the Abit Seriallel converters I'm using? but then again why would only one be working, and even then the other one seems to work fine in safe mode, according to windows...

I've tried IDE Bus Mastering both on and off in the bios, as well as selecting between the different SATA modes in the bios, currently its on auto.

I notice that in Device Manager, under IDE ATA/ATAPI controllers, the main controller drivers is from 7/1/2001 v5.1.2600.0 is this normal? or shoudl the intel INF drivers/files or IS7 mobo drivers have put in a newer one?

anyone ran into this mess before? maybe its SP2?

TIA

 

[LTC8K6]

Usually, deleting the controller and allowing XP to redetect it will cure this problem by resetting Xp's error detection. If XP detects errors, it progressively slows down the channel. If it keeps happening then you may need to look into why the errors are occurring.

 

[araczynski]

The link i was referring to is http://users.bigpond.net.au/ni...tserviceduck/udma_fix/
i believe the main focus here is to reset teh error detection as you were referring to. i followed this and it found everythign the same.

I did delete the primary ide channel in the device manager, but that didn't help either. i haven't tried deleting the whole controller yet however...

can anyone who has no problems and a similar setup confirm that the controller drivers i have are even the correct ones?

mine seem to be generic micrsoft drivers, not sure if this is fine or not in light of the intel INF files and/or any Abit drivers that should perhaps take precendence?