I have a Precision 370 and am consistently unable to get reasonable disk performance out of two drives on the single IDE channel that is present. I've tried an optical drive and a hard drive, two hard drives and tried various IDE cables, various drives, cable select, master/slave, different positions, etc. I am running the "Fresh Diagnose" disk benchmarking utility and am consistently getting a ~20MB/sec read/write from one drive and apparent nonsense performance from the other (e.g. 1MB/sec write, 800MB/sec read). I have a single SATA drive for a my boot/system drive.
I know I can avoid all this by using exclusively SATA hard drives, but I don't want to have to go and by new drives.
I had a 360 prior to this and never had his problem.
Go into your device manager, and check the properties of your Secondary IDE Channel.
Under Advanced settings, make sure that your 'Current Transfer Mode:' for each device is At least DMA (Ultra DMA preferred). If it failed over to PIO mode check this great page regarding how to fix it.
http://users.bigpond.net.au/ninjaduck/itserviceduck/udma_fix/
• For repeated DMA errors. Windows XP will turn off DMA mode for a device after encountering certain errors during data transfer operations. If more that six DMA transfer timeouts occur, Windows will turn off DMA and use only PIO mode on that device.
In this case, the user cannot turn on DMA for this device. The only option for the user who wants to enable DMA mode is to uninstall and reinstall the device.
Windows XP downgrades the Ultra DMA transfer mode after receiving more than six CRC errors. Whenever possible, the operating system will step down one UDMA mode at a time (from UDMA mode 4 to UDMA mode 3, and so on).
If the mini-IDE driver for the device does not support stepping down transfer modes, or if the device is running UDMA mode 0, Windows XP will step down to PIO mode after encountering six or more CRC errors. In this case, a system reboot should restore the original DMA mode settings.
All CRC and timeout errors are logged in the system event log. These types of errors could be caused by improper mounting or improper cabling (for example, 40-pin instead of 80-pin cable). Or such errors could indicate imminent hardware failure, for example, in a hard drive or chipset.
To enable DMA mode using the Device Manager
1. Open Device Manager.
2. Double-click IDE ATA/ATAPI Controllers to display the list of controllers and channels.
3. Right-click the icon for the channel to which the device is connected, select Properties, and then click the Advanced Settings tab.
4. In the Current Transfer Mode drop-down box, select DMA if Available if the current setting is "PIO Only."
If the drop-down box already shows "DMA if Available" but the current transfer mode is PIO, then the user must toggle the settings. That is:
• Change the selection from "DMA if available" to PIO only, and click OK.
• Then repeat the steps above to change the selection to DMA if Available.
The Scary fix is this
This behaviour occurs with the following conditions:
Windows XP is the operating system
A CD-ROM or DVD-ROM drive, which is known to support DMA mode now works only in PIO mode.
The drive controller is set to use "DMA if available" but reports to be only in PIO mode.
Following is the mechanism that has worked for me, please try it at your own risk, it involves hacking the registry:
Open RegEdit
Find the following KEY:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\000x
The last four digits will be 0000, 0001, 0002, 0003, and so on.
Under each key, delete all occurences of the following values:
MasterIdDataChecksum
SlaveIdDataChecksum
Reboot the computer. Windows will now redetect DMA settings.
BiSiE
5 Posts
384
0
Posted February 16th, 2005 19:00
Under Advanced settings, make sure that your 'Current Transfer Mode:' for each device is At least DMA (Ultra DMA preferred). If it failed over to PIO mode check this great page regarding how to fix it.
http://users.bigpond.net.au/ninjaduck/itserviceduck/udma_fix/