solving the dma problem in winxp!!

if you can not set the dma mode in win xp, just click this link, it sets udma/66 right in the registry!!
http://www.tweak3d.net/tweak/win2kmem/udma66on.reg

Or you can do it manually

even after you have enabled DMA on your IDE channels, UDMA/66 is still disabled by default in Win2k. To enable it, it is necessary to play around with the registry a bit. If you would like to perform the operation manually, you can do it by browsing to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0000 key and adding a new DWORD value called EnableUDMA66. Set the value to 1 to enable UDMA/66 or to 0 to disable UDMA/66.

The title of your thread is "solving the dma problem in winxp!!"

Then you a post registry patch to fix a condition of Windows 2000 that disables UDMA 66 by default.

What does the title of this thread have to do with this fix? WinXP does not have this problem.

had this problem with my plextor that it turned back to pio from time to time, this was the way i fixed that. Normally, when i uninstalled the IDE and let xp look for them, xp sets it to multi-word dma mode 2. With this registry-setteng, xp found my plextor as an ultra DMA mode 2, and it hasn't been changed since.
Had big trouble with that problem till i found this patch

In that case, I applaud your finding this fix, for it has been a pain for many people.

All knowledge is useful, Inertia, even if it strays a bit - don't knock it.

hai die hai,

thankx for the fix!!

Hope it works for you guys, cause it was a pain in the butt for me for quite some time!!!!!!

All socalled knowledge is not useful, YogiBear, if in fact it is not knowledge but a misguided or misinterpreted source of information. It is common on the Web to have bad information passed as knowledge, with people wasting time at the least, and at worst doing harm. So I reject your gratuitous advice, which apparently was thought to be given with the benefit of hindsight.

Meniak,

I have given this "solution" to two people in the General Hardware Forum, both of whom whose devices were running in DMA MW 2 in WinXP.

It didn't work for either of them, although I don't know that their devices ever ran in UDMA mode as they should in WinXP.

Perhaps it works for you, but it will not force devices capable of running in UDMA mode to be recognized as such in WinXP. I will reserve judgment until I see more reports of successful results.

I hardly think this applies to meniaks post!

I run W2K and appreciated the extra info.

Have WinXP and a 48/24/48...didn't work for me. Every *goddamn* time i reboot I loose DMA...grrrrrrr...


Frederic

Worked for me. A guy i know had the same problem, he tried what I said, and it didn't help, sorry. But he did a clean install of winxp after a firmware update and know it is finally recognized as udma. Don't know why, but it just did!

ok here an alternative solution that worked for me i didnt try the other one but this one here is def. for xp:

you go to the reg. key :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001 or 0002 (depending on beeing primary[0001] or secondary[0002] ide channel)

there you modify the DWORD value of :
if the drive is on master: "MasterDeviceTimingModeAllowed" or
if the drive is on slave: "SlaveDeviceTimingModeAllowed"
to ffffffff

then go back to your device manager set your drive in IDE channel properties first back to pio and then, after confirming, again to dma ...that should do the trick

ps: HERE the reason why and when xp sets it back to pio-mode

After preaching and complaining for two years since XP came out, MS has FINALLY Acknowledges that this IS a BUG, The problem with this is simple:

2K and XP looks for 6 consecutive timeout periods when it queries the drive, after the 6th time it drops dma mode, and if many realize this happens over time and not right away. The removing of the IDE channel and letting XP re-detect it is one solution I came up with as well as another type for ATA cards.

But here is the bug in XP as well as 2K, it seems that even if either OS gets a response it doesnt RESET the Counters. In short, if it gets a response say at the 4th querey, then by default its suppose to reset the timeout counter, it doesnt, it leaves it at 4, and then when two more timeouts occur it drops dma, where when it gets a response, it suppose to reset to 0.

MS acknowledges this, A fix is available, it will be put into SP2. If you cant wait for SP2 then you can contact MS for get the fix.

Thanks for the info AngelDeath!

AngelDeath,

do you have the hotfix number? I get faster from the local MS support, if they don't have to look for it in their database. For some reason they are not very up to date on all fixes

Thanks for the information!

I posted this on XP forum, so here is the whole article, and the KB# in BOLD

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.


Microsoft Knowledge Base Article - 817472

IDE ATA and ATAPI Disks Use PIO Mode After Multiple Time-Out or CRC Errors Occur
The information in this article applies to:
Microsoft Windows Server 2003, Web Edition
Microsoft Windows Server 2003, Standard Edition
Microsoft Windows Server 2003, Enterprise Edition
Microsoft Windows Server 2003, 64-Bit Enterprise Edition
Microsoft Windows XP Professional SP1
Microsoft Windows XP Professional
Microsoft Windows XP Home Edition SP1
Microsoft Windows XP Home Edition
Microsoft Windows XP 64-Bit Edition Version 2002 SP1
Microsoft Windows XP 64-Bit Edition Version 2002
Microsoft Windows 2000 Server SP3
Microsoft Windows 2000 Server SP2
Microsoft Windows 2000 Server SP1
Microsoft Windows 2000 Server
Microsoft Windows 2000 Professional SP3
Microsoft Windows 2000 Professional SP2
Microsoft Windows 2000 Professional SP1
Microsoft Windows 2000 Professional

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry

SYMPTOMS
After you suspending and resume your computer several times, hard disk performance may be reduced. If you use Device Manager to view the properties of the IDE channel to which the drive is connected, the Advanced Settings tab may show that the current transfer mode for the drive is "PIO Mode."
CAUSE
After the Windows IDE/ATAPI Port driver (Atapi.sys) receives a cumulative total of six time-out or cyclical redundancy check (CRC) errors, the driver reduces the communications speed (the transfer mode) from the highest Direct Memory Access (DMA) mode to lower DMA modes in steps. If the driver continues to receive time-out or CRC errors, the driver eventually reduces the transfer mode to the slowest mode (PIO mode).
RESOLUTION
Windows 2000
A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that is described in this article. Apply it only to systems that specifically need it. This feature may receive additional testing. Therefore, if your system is not severely affected by the lack of this feature, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this feature.

To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default...EN-US;CNTACTMS

Prerequisites
Windows 2000 Service Pack 2

Restart Requirement
You must restart your computer after you apply this hotfix.
Hotfix Replacement Information
This hotfix replaces hotfixes 813908, 323153, 314695, 305176, 305098, 304912, 304572, and 298505.

File Information
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name
----------------------------------------------------
28-Apr-2003 17:38 5.0.2195.6741 86,896 Atapi.sys

Note After you install this hotfix, you must modify the registry as described in the "More Information" section in this article to change this behavior. If you do not modify the registry, the hotfix does not change the behavior.
Windows XP
A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that is described in this article. Apply it only to systems that specifically need it. This feature may receive additional testing. Therefore, if your system is not severely affected by the lack of this feature, Microsoft recommends that you wait for the next Windows XP service pack that contains this feature.

To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default...EN-US;CNTACTMS

Prerequisites
Windows XP Service Pack 1

Restart Requirement
You must restart your computer after you apply this hotfix.
Hotfix Replacement Information
This hotfix replaces hotfixes 331958 and 331895.
File Information
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name Platform
---------------------------------------------------------------
23-Apr-2003 16:29 5.1.2600.1211 87,296 Atapi.sys i386
23-Apr-2003 16:29 5.1.2600.1211 306,432 Atapi.sys IA64

Note After you install this hotfix, you must modify the registry as described in the "More Information" section in this article to change this behavior. If you do not modify the registry, the hotfix does not change the behavior.
Windows Server 2003
A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that is described in this article. Apply it only to systems that specifically need it. This feature may receive additional testing. Therefore, if your system is not severely affected by the lack of this feature, Microsoft recommends that you wait for the next Windows Server 2003 service pack that contains this feature.

To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default...EN-US;CNTACTMS

Prerequisites
No service pack required.

Restart Requirement
You must restart your computer after you apply this hotfix.
Hotfix Replacement Information
This hotfix does not replace any other hotfixes.
File Information
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name Platform
-------------------------------------------------------------
28-Apr-2003 18:09 5.2.3790.10 91,136 Atapi.sys i386
28-Apr-2003 18:09 5.2.3790.10 288,256 Atapi.sys IA64

Note After you install this hotfix, you must modify the registry as described in the "More Information" section in this article to change this behavior. If you do not modify the registry, the hotfix does not change the behavior.
WORKAROUND
To re-enable the typical, or faster, transfer mode for an affected device:
Double-click Administrative Tools, and then click Computer Management.
Click System Tools, and then click Device Manager.
Expand the IDE ATA/ATAPI Controllers node.
Double-click the controller for which you want to restore the typical DMA transfer mode.
Click the Driver tab.
Click Uninstall.
When the process completes, restart your computer. When Windows restarts, the hard disk controller is re-enumerated and the transfer mode is reset to the default value for each device that is connected to the controller.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
The hotfix that this article describes makes the following changes:
In Windows 2000 only, read requests to ATA disks are sometimes issued with a time-out value of 4 seconds. This occurs when your computer resumes from standby. This might cause a disk time-out because drives typically take more than 4 seconds to spin up. This time-out value was changed to 10 seconds.

In Windows XP and Windows Server 2003, this time-out value is always 10 seconds.
An alternate, less-aggressive policy is implemented to reduce the transfer mode (from faster to slower DMA modes, and then eventually to PIO mode) on time-out and CRC errors. The existing behavior is that the IDE/ATAPI Port driver (Atapi.sys) reduces the transfer mode after any 6 cumulative time-out or CRC errors. When the new policy is implemented by this fix, Atapi.sys reduces the transfer mode only after 6 consecutive time-out or CRC errors. This new policy is implemented only if the registry value that is described later in this article is present.
To implement the alternate behavior (reducing the transfer mode after six consecutive time-out or CRC errors instead of after six cumulative time-out or CRC errors), you must modify the registry as described below after you install the hotfix.

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 are:
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."

Guess MS finally heard enough bitching and accepted it was them and not push off the problem as someone else's

Halcyon If you get this fix, can you please share it?

For me the following worked: place the drive you want to
have running in DMA Mode 2, as slave next to your hd on
your primairy ide port.

FROM ADAMOVENICE:
THANK YOU, THANK YOU, MR. AEOLUS, ONLY IN THIS WAY I RESOLVED MY DMA/ATA PRBLMS IN XP FOR MY PREMIUM

yuhuuuu! solve it here.
Aelous God bless you!

Nice find on the fix, but again remember this everyone, this isnt a perm fix but a workaround, it seems this might be increasing the timeout period giving the controllers a chance to respond, what this line actually is doing is prolonging what will at the end be the same thing. a PIO mode, but none the less it seems MS has adapted this workaround also, as I went to check my registry, and it seems mine is already set to that value, so one of the hot fixes seems to be implimenting this. But again its only a workaround, for this to work permenantly a registry dword (ResetErrorCountersOnSuccess) has to be added as well as a new driver needs to be put into place, so be forwarned if you happen to see this happen again.

worked for me like a charm!

premium drive nforce2 mobo winxp

Could this be the hotfix you're looking for?

http://h18007.www1.hp.com/support/fi...oad/18249.html

Anyone have a link to the "real" MS fix (post SP1 Hotfix)? Trying to run the HP mix on my machine, get error message that my "machine" is not supported (prolly cuz it aint a HP/COMPAQ). MSI KT400 motherboard... Can't get my Optorite 0201 out of PIO mode, so it runs like a P.O.S. .



L

Hi there!

Just wanted to tell you, that i had the same problems although i tried everything which was recommended by other members.

But then i had the idea the check the bios if dma is enabled. of course it was disabled. so i changed the settings for primary master (hdd) and secondary master (plextor 708a) from "disabled" to "automatic" and voila...it works!

So ....i hope this helps!

My DVD-ROM is installed on the secondary channel and has this problem, but there is no key under 0002 named "SlaveDeviceTimingModeAllowed." Can I safely add this key and change the value to ffffffff?

For some reason my Secondary Channel is under 0001 not 0002. At least that's what the DriverDesc key says. So I'll change the one under 0001 and see what happens.

Update: That worked.

---

Last edited by Elder Young; 03-01-2005 at 07:50.