PDA

View Full Version : how to fix DMA/PIO problem here


NightMare
19th October 2003, 14:41
this is stight from microsoft

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Follow these steps, and then quit Registry Editor:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001

On the Edit menu, point to New, and then click DWORD Value.
Type ResetErrorCountersOnSuccess, and then press ENTER.
On the Edit menu, click Modify.
Type 1, and then click OK.
Follow these steps, and then quit Registry Editor:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002

On the Edit menu, point to New, and then click DWORD Value.
Type ResetErrorCountersOnSuccess, and then press ENTER.
On the Edit menu, click Modify.
Type 1, and then click OK.
Note The numbered subkeys that are listed earlier correspond to the primary and secondary IDE channels on a computer that contains a single IDE controller. If your computer contains two IDE controllers, the numbered subkeys for the primary and secondary IDE channels for each of the two controllers may be:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0003

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0004

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0005

To verify that you have located the correct subkey, verify that the DriverDesc value for the subkey contains the string value "Primary IDE Channel" or the string value "Secondary IDE Channel."

mrbass
19th October 2003, 21:06
I assume your talking about winxp and how it flips back to PIO mode at times. Well it's inevitable no matter what you do. So when it happens the easiest way instead of all that stuff is to:

a) simply delete your primary and/or secondary IDE channel in Device Manager.
b) reboot, let it redetect it
c) reboot and your set

NightMare
19th October 2003, 21:39
Originally posted by mrbass
I assume your talking about winxp and how it flips back to PIO mode at times. Well it's inevitable no matter what you do. So when it happens the easiest way instead of all that stuff is to:

a) simply delete your primary and/or secondary IDE channel in Device Manager.
b) reboot, let it redetect it
c) reboot and your set

what this dose from what i know that it dosent allow windows xp to switch to PIO mode no mater how much errors u get

GrofLuigi
20th October 2003, 03:20
Microsoft article:

http://support.microsoft.com/?kbid=817472

It appears you need new atapi.sys driver from August 2003, but I can't find direct link for d/l. :(

GL

TEB
20th October 2003, 11:50
or for those of u with intel chipsets, just install the 2.3 Intel Appliaction accelerator... My ripping went up from 2.1x to 8x

angelleye
24th October 2003, 01:20
when this was happening to me I discovered that there was a BIOS firmware upgrade that needed to be applied. After I did that I've never had it switch to PIO mode on me since.