How to get this Hotfix?

  • Thread starter Thread starter Terry Pinnell
  • Start date Start date
T

Terry Pinnell

At this page
http://support.microsoft.com/?kbid=817472
there is a description of a 'hotfix' for the problem I've described in
a separate thread 'Uninstall/reinstall HD to recover DMA?'

It tells me to contact MS to get the fix. On following the convoluted
procedure to do that, I soon hit the obstacle that, as XP Home was
already installed on this (OEM) MESH Athlon 1800 PC, I have to
"contact your supplier for support". Fat chance of any help there,
based on previous experience.

Anyone have this fix or know where I can download it please? Darned if
I see why it should be so hard to get a patch for an OS bug!
 
The only way to get it Terry, is to contact MS as it states. Sorry, but
that's how they do the hotfixes.

Tom
 
Tom [Pepper] Willett said:
The only way to get it Terry, is to contact MS as it states. Sorry, but
that's how they do the hotfixes.

Tom
Terry Pinnell said:
At this page
http://support.microsoft.com/?kbid=817472
there is a description of a 'hotfix' for the problem I've described in
a separate thread 'Uninstall/reinstall HD to recover DMA?'

It tells me to contact MS to get the fix. On following the convoluted
procedure to do that, I soon hit the obstacle that, as XP Home was
already installed on this (OEM) MESH Athlon 1800 PC, I have to
"contact your supplier for support". Fat chance of any help there,
based on previous experience.

Anyone have this fix or know where I can download it please? Darned if
I see why it should be so hard to get a patch for an OS bug!
Click to expand...
Click to expand...

Thanks Tom, but as I said, I'm persona non grata as an OEM purchaser,
and apparently therefore excluded!
 
Rot!

I download Hotfixes all the time as an OEM purchaser -- but I have a LEGAL
copy of Windows XP Pro.

Perhaps you don't have a Legal Copy of Windows XP.

DSH
 
D. Spencer Hines said:
Rot!

I download Hotfixes all the time as an OEM purchaser -- but I have a LEGAL
copy of Windows XP Pro.

Perhaps you don't have a Legal Copy of Windows XP.

DSH
Click to expand...

And perhaps you should refrain from insulting posts like that?
 
Terry said:
And perhaps you should refrain from insulting posts like that?
Click to expand...

And perhaps you should both quote what you're replying to in entirety.
No one else knows WTF you're talking about and the thread is orphaned.

Steve N.
 
Terry said:
At this page
http://support.microsoft.com/?kbid=817472
there is a description of a 'hotfix' for the problem I've described
in a separate thread 'Uninstall/reinstall HD to recover DMA?'

It tells me to contact MS to get the fix. On following the
convoluted procedure to do that, I soon hit the obstacle that, as
XP Home was already installed on this (OEM) MESH Athlon 1800 PC, I
have to "contact your supplier for support". Fat chance of any help
there, based on previous experience.

Anyone have this fix or know where I can download it please? Darned
if I see why it should be so hard to get a patch for an OS bug!
Click to expand...
The only way to get it Terry, is to contact MS as it states. Sorry, but
that's how they do the hotfixes.
Click to expand...

Terry said:
Thanks Tom, but as I said, I'm persona non grata as an OEM
purchaser, and apparently therefore excluded!
Click to expand...

D. Spencer Hines said:
Rot!

I download Hotfixes all the time as an OEM purchaser -- but I have
a LEGAL copy of Windows XP Pro.

Perhaps you don't have a Legal Copy of Windows XP.
Click to expand...

Terry said:
And perhaps you should refrain from insulting posts like that?
Click to expand...
And perhaps you should both quote what you're replying to in
entirety. No one else knows WTF you're talking about and the thread
is orphaned.
Click to expand...

There you are, Steve.
 
It tells me to contact MS to get the fix. On following the convoluted
procedure to do that, I soon hit the obstacle that, as XP Home was
already installed on this (OEM) MESH Athlon 1800 PC, I have to
"contact your supplier for support". Fat chance of any help there,
based on previous experience.
Click to expand...

You're calling tech support, correct? Press whatever key you have to press
to get a live person. Explain to them that you're calling about a hotfix.
OEM or not, it shouldn't matter where these are concerned.
 
Terry,
from the very same KB817472:
" This problem was first corrected in Microsoft Windows XP Service Pack 2."
What service pack do you have? I just don't see any reason for you to be
after this outdated fix, if you can install SP2.

File version in the fix: 5.1.2600.1211
In SP2: 5.1.2600.2180
 
Mak said:
Terry,
from the very same KB817472:
" This problem was first corrected in Microsoft Windows XP Service Pack 2."
What service pack do you have? I just don't see any reason for you to be
after this outdated fix, if you can install SP2.

File version in the fix: 5.1.2600.1211
In SP2: 5.1.2600.2180
Click to expand...

Thanks. Yes, I could install SP2 as a way of avoiding the need for
this 'special' hotfix. But I installed SP2 a year or so ago, hit
serious problems, and promptly reverted to SP1. I have my share of
quirks etc, but with the exception of this exasperating DMA problem,
right now I have a pretty sweetly-running and secure system here, and
am reluctant to upgrade at present. Within a year I'll be moving up to
a newer, faster PC (this is over 4 years old), and that's when I'd
planned to go to SP2.

That aside, *if* I could be reasonably confident that doing so would
fix my immediate problem, that would swing it. I have the full SP2 CD
standing by. But I'm far from sure about that. I've already tried
every potential solution I've found or had suggested so far, (MS
'hotfix' apart). These include reinstallation of the IDE controller,
alternative drivers, extensive registry changes, etc. From advice in
the storage group, it's looking as if the problem of this PIO
persistent re-setting might be down to some hardware issue. I'm going
to look into that more closely today.

Sharon: On a Sunday night in the UK? No, I haven't yet tried calling
MS. Yesterday I tried to follow the e-mail route, but - as I reported
- it was not allowed. My system came with XP Home built-in, which
apparently throws at least that level of support back on the OEM.
http://support.microsoft.com/oas/default.aspx?ln=en-us&prid=3219&gprid=37013
"If the product was already installed on your computer when you
purchased it, contact your computer manufacturer."
 
Mak said:
OK. I didn't see SP level of your system in any of your recent posts.

1 min of google brings this:
you can probably try:
http://h18007.www1.hp.com/support/files/hpcpqdt/us/download/21870.html
or (dodgy source, but you can make a decision yourself):
http://erpman1.tripod.com/current/atapi-xp.html
if nothing better shows up.
(I would try SP2)
Click to expand...

Thanks Mak, appreciate your taking the time. That first one looked SO
promising. But this is what I got on running it:
"Hewlett-Packard Setup:
This Computer System is not supported. Installation canceled."

I suppose that's simply because this is a MESH (OEM) PC, not an HP
model.

Turning to the second link, if I look at Event Viewer, as the article
recommends, it confirms that the drive is generating many of the type
of entries underlying this problem.

I'll study this one further, back up my existing atapi.sys files, and
tentatively experiment.

FWIW, here are the XP Home registry entries directly after
uninstalling the IDE Controller and letting XP reinstall it (which
takes 2 reboots). Reminder: The 200 GB drive under discussion is the
'Primary Slave', on which CHKDSK was recently run from XP.

SCREENSHOT:
-----------
http://www.terrypin.dial.pipex.com/Images/DMA-Registry1.jpg

DETAIL:
------
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}]
"Class"="hdc"
@="IDE ATA/ATAPI controllers"
"Icon"="-9"
"Installer32"="SysSetup.Dll,HdcClassInstaller"
"TroubleShooter-0"="hcp://help/tshoot/tsdrive.htm"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0000]
"InfPath"="mshdc.inf"
"InfSection"="aliide_Inst"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
"DriverDate"="7-1-2001"
"DriverVersion"="5.1.2600.1106"
"MatchingDeviceId"="pci\\ven_10b9&dev_5229"
"DriverDesc"="ALi M5229 PCI Bus Master IDE Controller"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001]
"InfPath"="mshdc.inf"
"InfSection"="atapi_Inst_primary"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
"DriverDate"="7-1-2001"
"DriverVersion"="5.1.2600.1106"
"MatchingDeviceId"="primary_ide_channel"
"DriverDesc"="Primary IDE Channel"
"MasterDeviceType"=dword:00000001
"SlaveDeviceType"=dword:00000001

"SlaveDeviceDetectionTimeout"=dword:00000001 <-- I wonder if
this is the entry that causes the drop back to PIO mode? And if so,
whether I could safely change it to dword:00000000, or delete it?

"MasterDeviceTimingMode"=dword:00010010

"SlaveDeviceTimingMode"=dword:00000010 <-- I wonder if
this specifies 'PIO' (and the line above 'DMA')?

"MasterIdDataCheckSum"=dword:00014d8d
"SlaveIdDataCheckSum"=dword:00019948
"EnumPropPages32"="storprop.dll,IdePropPageProvider"
"MasterDeviceTimingModeAllowed"=dword:ffffffff

"SlaveDeviceTimingModeAllowed"=dword:0000001f <-- I read
somewhere that another thing to try is looking for low values like
this and restoring them to default (presumably like the entry above).
But it refused to accept this change when I tried it!

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002]
"InfPath"="mshdc.inf"
"InfSection"="atapi_Inst_secondary"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
"DriverDate"="7-1-2001"
"DriverVersion"="5.1.2600.1106"
"MatchingDeviceId"="secondary_ide_channel"
"DriverDesc"="Secondary IDE Channel"
"MasterDeviceType"=dword:00000002
"SlaveDeviceType"=dword:00000002
"MasterDeviceTimingMode"=dword:00002010
"MasterIdDataCheckSum"=dword:000207ff
"SlaveDeviceTimingMode"=dword:00002010
"SlaveIdDataCheckSum"=dword:00019485
"EnumPropPages32"="storprop.dll,IdePropPageProvider"
"MasterDeviceTimingModeAllowed"=dword:ffffffff
"SlaveDeviceTimingModeAllowed"=dword:ffffffff
 
bleh.. the first one, from HP:
1. use WinZip to unzip it.
it will create folder structure with different lanuages. Find the one called
US. Inside you will find setup.dat file.
2. Use WinZip again on this file.
go into Update folder, run update.exe or right click on update.inf and
choose install.


Terry Pinnell said:
Mak said:
OK. I didn't see SP level of your system in any of your recent posts.

1 min of google brings this:
you can probably try:
http://h18007.www1.hp.com/support/files/hpcpqdt/us/download/21870.html
or (dodgy source, but you can make a decision yourself):
http://erpman1.tripod.com/current/atapi-xp.html
if nothing better shows up.
(I would try SP2)
Click to expand...

Thanks Mak, appreciate your taking the time. That first one looked SO
promising. But this is what I got on running it:
"Hewlett-Packard Setup:
This Computer System is not supported. Installation canceled."

I suppose that's simply because this is a MESH (OEM) PC, not an HP
model.

Turning to the second link, if I look at Event Viewer, as the article
recommends, it confirms that the drive is generating many of the type
of entries underlying this problem.

I'll study this one further, back up my existing atapi.sys files, and
tentatively experiment.

FWIW, here are the XP Home registry entries directly after
uninstalling the IDE Controller and letting XP reinstall it (which
takes 2 reboots). Reminder: The 200 GB drive under discussion is the
'Primary Slave', on which CHKDSK was recently run from XP.

SCREENSHOT:
-----------
http://www.terrypin.dial.pipex.com/Images/DMA-Registry1.jpg

DETAIL:
------
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}]
"Class"="hdc"
@="IDE ATA/ATAPI controllers"
"Icon"="-9"
"Installer32"="SysSetup.Dll,HdcClassInstaller"
"TroubleShooter-0"="hcp://help/tshoot/tsdrive.htm"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0000]
"InfPath"="mshdc.inf"
"InfSection"="aliide_Inst"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
"DriverDate"="7-1-2001"
"DriverVersion"="5.1.2600.1106"
"MatchingDeviceId"="pci\\ven_10b9&dev_5229"
"DriverDesc"="ALi M5229 PCI Bus Master IDE Controller"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001]
"InfPath"="mshdc.inf"
"InfSection"="atapi_Inst_primary"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
"DriverDate"="7-1-2001"
"DriverVersion"="5.1.2600.1106"
"MatchingDeviceId"="primary_ide_channel"
"DriverDesc"="Primary IDE Channel"
"MasterDeviceType"=dword:00000001
"SlaveDeviceType"=dword:00000001

"SlaveDeviceDetectionTimeout"=dword:00000001 <-- I wonder if
this is the entry that causes the drop back to PIO mode? And if so,
whether I could safely change it to dword:00000000, or delete it?

"MasterDeviceTimingMode"=dword:00010010

"SlaveDeviceTimingMode"=dword:00000010 <-- I wonder if
this specifies 'PIO' (and the line above 'DMA')?

"MasterIdDataCheckSum"=dword:00014d8d
"SlaveIdDataCheckSum"=dword:00019948
"EnumPropPages32"="storprop.dll,IdePropPageProvider"
"MasterDeviceTimingModeAllowed"=dword:ffffffff

"SlaveDeviceTimingModeAllowed"=dword:0000001f <-- I read
somewhere that another thing to try is looking for low values like
this and restoring them to default (presumably like the entry above).
But it refused to accept this change when I tried it!

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002]
"InfPath"="mshdc.inf"
"InfSection"="atapi_Inst_secondary"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
"DriverDate"="7-1-2001"
"DriverVersion"="5.1.2600.1106"
"MatchingDeviceId"="secondary_ide_channel"
"DriverDesc"="Secondary IDE Channel"
"MasterDeviceType"=dword:00000002
"SlaveDeviceType"=dword:00000002
"MasterDeviceTimingMode"=dword:00002010
"MasterIdDataCheckSum"=dword:000207ff
"SlaveDeviceTimingMode"=dword:00002010
"SlaveIdDataCheckSum"=dword:00019485
"EnumPropPages32"="storprop.dll,IdePropPageProvider"
"MasterDeviceTimingModeAllowed"=dword:ffffffff
"SlaveDeviceTimingModeAllowed"=dword:ffffffff
Click to expand...
 
Mon, 06 Feb 2006 00:26:56 +0000 from Terry Pinnell
And perhaps you should refrain from insulting posts like that?
Click to expand...

If he could refrain from insulting posts, he wouldn't be Spencer
Hines.
 
Terry said:
And perhaps you should refrain from insulting posts like that?
Click to expand...

[Courtesy of Kelly Theriot, MVP]
Call Microsoft Professional Customer Service @ 1-800-936-4900 (this line
is 24/7), there is an option for hotfix. A rep will email you a link to
the fix.
 
Rock said:
Terry said:
And perhaps you should refrain from insulting posts like that?
Click to expand...

[Courtesy of Kelly Theriot, MVP]
Call Microsoft Professional Customer Service @ 1-800-936-4900 (this line
is 24/7), there is an option for hotfix. A rep will email you a link to
the fix.
Click to expand...

Many thanks Rock. That number is now in my Key Contacts list for
possible future use. But happy to report that I won't need to use it
on this issue.

I just finished replacing the newish 200 GB with its 4-year old 60 GB
predecessor - and UDMA 5 is back!

So, although I suppose it *could* still be some obscure software issue
connected with the very large size of the drive, the most likely
explanation appears to be a faulty drive.

Only bought it in October (from Misco, UK). About to call *them* to
see if I have any hope of a replacement!

So, more than two entire days (and most of the night) fiddling and
faffing around with all sorts of obscure software stuff, and all
unnecessary! I suppose I should have tried that first, but that's with
the benefit of hindsight <g>.

Many thanks for all the help here.
 
Terry said:
Terry Pinnell wrote:

Rot!

I download Hotfixes all the time as an OEM purchaser -- but I have a LEGAL
copy of Windows XP Pro.

Perhaps you don't have a Legal Copy of Windows XP.

DSH


And perhaps you should refrain from insulting posts like that?
Click to expand...

[Courtesy of Kelly Theriot, MVP]
Call Microsoft Professional Customer Service @ 1-800-936-4900 (this line
is 24/7), there is an option for hotfix. A rep will email you a link to
the fix.
Click to expand...


Many thanks Rock. That number is now in my Key Contacts list for
possible future use. But happy to report that I won't need to use it
on this issue.

I just finished replacing the newish 200 GB with its 4-year old 60 GB
predecessor - and UDMA 5 is back!

So, although I suppose it *could* still be some obscure software issue
connected with the very large size of the drive, the most likely
explanation appears to be a faulty drive.

Only bought it in October (from Misco, UK). About to call *them* to
see if I have any hope of a replacement!

So, more than two entire days (and most of the night) fiddling and
faffing around with all sorts of obscure software stuff, and all
unnecessary! I suppose I should have tried that first, but that's with
the benefit of hindsight <g>.

Many thanks for all the help here.
Click to expand...

You're welcome Terry, and thanks for posting back with the resolution.
 
Back
Top