DB2 学习笔记 - AIView.com

I check my System Events, there's following error continually detected. 

Event Type:    Error
Event Source:    atapi
Event Category:    None
Event ID:    9
Date:        1/20/2006
Time:        11:05:39 AM
User:        N/A
Computer:    IBM-ALEX
Description:
The device, \Device\Ide\IdePort0, did not respond within the timeout period.

 

Accounding to the artical in refference, I found the related entry in my registry:

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

I deleted this dword value, then reboot.

MasterIdDataCheckSum

The tools Everest and Sandra Lite say the 1st hdd is working on UDMA 5, but the windows device manager still says PIO mode, I made a test of copying file, the speed is slow as before.

I checked the the dword value MasterDeviceTimingModeAllowed, it's less 0xFFFFFFFF, so I set it back to 0xFFFFFFFF, and deleted MasterIdDataCheckSum again, then reboot.

It works, this time the 3rd part tools and windows device manager both say it's on UDMA 5 mode.

I re-tested 1st hdd by copying files, it's as fast as 2nd hdd now. 

refer to: 

• DMA reverts to PIO
  http://winhlp.com/WxDMA.htm

The dvd-rw comes with my thinkpad has the maximum UDMA 2, and it's using UDMA 2 mode now.

The native hdd still keeps reducing to PIO mode after a few days.

I found this topic which descibe why this mess happens again and again.

• IDE ATA and ATAPI disks use PIO mode after multiple time-out or CRC errors occur
  http://support.microsoft.com/kb/817472/

The hotfix has been included in winxp sp2 which I have patched.
The step in the MORE INFORMATION section seems will help me. I take this step.

Add a new DWORD value, use 1 as the Data.

ResetErrorCountersOnSuccess

at following each Registry key:

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

then reboot. 

The last solution seems worked, I don't meet the problem of reverting to PIO mode for a week. there're also a few atapi timeout errors, but the chksum should be reset on next success.