[SOLVED] HD in PIO mode?

Requimatic · 10-14-2008, 12:01 PM

After browsing around the device manager, it seems my HD is stuck in PIO mode, when it should support UDMA, but for some reason won't use it. I'm assuming this is part of the reason why the drive is operating so slowly..maybe the only reason.

It's a Seagate 250GB drive, ST3250620A is the device listed in the device manager.

Sorry to be so vague, I'm not really sure where to start.

**manic** · 10-14-2008, 01:27 PM

Go into bios, and set to auto, if that doesnt do it, set it manually,
in bios. Should be udma 5, if my memory serves.

Requimatic · 10-14-2008, 01:32 PM

Actually, I just managed to fix the problem. Everything was set correctly in the BIOS, and an HD Tach test was showing me an average read of 2.5MB/s..so I looked around and found some registry keys to delete, which required a restart.

I did so, and noticed that the system took MUCH less time to restart, and after logging back onto my profile, I ran HD Tach again and got an average read of 67.7MB/s.

If need be, I can post here what registry keys I deleted in order for this to work.

**manic** · 10-14-2008, 01:36 PM

Good Job!

Requimatic · 10-14-2008, 01:47 PM

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

You should see subkeys 0001, 0002, 0003, etc. (up to 0008 in my case). Look in all of them for the following: MasterIdDataChecksum and SlaveIdDataChecksum, and delete them all when found, then simply restart. If your settings were still set to "Use DMA if available," upon restart the drive(s) should be back in UDMA mode.

At least this worked for me. I've read cases of this not working for some people..but if you've tried everything else, and not this, I guess it'd be worth a shot.

10-14-2008, 12:01 PM	#1 (permalink)
Requimatic Registered User Join Date: Jun 2008 Posts: 97 OS: 98 SE/2000/XP SP3 My System	[SOLVED] HD in PIO mode? After browsing around the device manager, it seems my HD is stuck in PIO mode, when it should support UDMA, but for some reason won't use it. I'm assuming this is part of the reason why the drive is operating so slowly..maybe the only reason. It's a Seagate 250GB drive, ST3250620A is the device listed in the device manager. Sorry to be so vague, I'm not really sure where to start.

10-14-2008, 01:27 PM	#2 (permalink)
manic Mod Hardware Team Join Date: Aug 2005 Location: Florida Posts: 5,245 OS: xp	Re: HD in PIO mode? Go into bios, and set to auto, if that doesnt do it, set it manually, in bios. Should be udma 5, if my memory serves. __________________

10-14-2008, 01:32 PM	#3 (permalink)
Requimatic Registered User Join Date: Jun 2008 Posts: 97 OS: 98 SE/2000/XP SP3 My System	Re: HD in PIO mode? Actually, I just managed to fix the problem. Everything was set correctly in the BIOS, and an HD Tach test was showing me an average read of 2.5MB/s..so I looked around and found some registry keys to delete, which required a restart. I did so, and noticed that the system took MUCH less time to restart, and after logging back onto my profile, I ran HD Tach again and got an average read of 67.7MB/s. If need be, I can post here what registry keys I deleted in order for this to work.

10-14-2008, 01:36 PM	#4 (permalink)
manic Mod Hardware Team Join Date: Aug 2005 Location: Florida Posts: 5,245 OS: xp	Re: [SOLVED] HD in PIO mode? Good Job! __________________

10-14-2008, 01:47 PM	#5 (permalink)
Requimatic Registered User Join Date: Jun 2008 Posts: 97 OS: 98 SE/2000/XP SP3 My System	Re: [SOLVED] HD in PIO mode? HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318} You should see subkeys 0001, 0002, 0003, etc. (up to 0008 in my case). Look in all of them for the following: MasterIdDataChecksum and SlaveIdDataChecksum, and delete them all when found, then simply restart. If your settings were still set to "Use DMA if available," upon restart the drive(s) should be back in UDMA mode. At least this worked for me. I've read cases of this not working for some people..but if you've tried everything else, and not this, I guess it'd be worth a shot.