KB891711.EXE

At this time, it appears the issue is common to systems running AMD
processors.

Thanks, that's something I didn't know. My Win Me boxes are an old Intel
PII 450 and a Celeron 400 plus various VMs on PCs running XP. My two AMD
boxes are only used to run XP Pro and XP Pro 64.
--
http://www.microsoft.com/windowsxp/e...ts/nichol.mspx
In memory of a very dear friend, Windows MVP Alex Nichol

Mike Maltby MS-MVP



Earl wrote:

Actually I'm fortunate enough to be running many systems in several
different configurations, with both old and new hardware.
Unfortunately, I'm also the guy that many people have called about
this issue when it occurred on their systems. I'm only curious how
the relatively uninformed could be aware of such a debacle with
891711 since January, with Microsoft so unaware that they would then
release the same patch upon unsuspecting ME users.
At this time, it appears the issue is common to systems running AMD
processors (now aint that a surprise), although the interaction of
various video cards may actually be at fault. Regardless, at this
time, I see no workaround except to remove 891711.

"Earl" wrote in message
...
At this time, it appears the issue is common to systems running AMD
processors (now aint that a surprise),

Both of my machines here run AMD Athelon XP processors. The machine at my son's
apartment is a AMD on an accellerator card that replaced the Pentum (one) in an
old Micron Millenium.

although the interaction of various video cards may actually be
at fault.

Hmmm. This one has a RADEON 9000 AGP, the other a VIA/S3G KM400 (on-board
video), the one over there is an S3, but I don't recall the details at the
moment.

Regardless, at this time, I see no workaround except to remove 891711.

All these are running without any problems.

- Bill

I don't have the full answer Bill; wish I did. Right now all I have to go on
is the commonality of the error to the machines that it has affected
adversely. Thus, the problem with KB891711:

Affects:
Windows ME (1 system on an AMD processor with the reboot issue)
Windows 2000 (6 systems running; 3 on Intel processors/motherboards with no
issues; 3 with old AMD processors with the reboot issue)

Does not affect:
Windows XP Pro (3 systems running on Intel processors, no issues)
Windows XP Home (5 systems running on Intel processors; no issues)

Probably does not affect:
Windows Server 2003 (one system running Win2003 Server OS on Intel; no
issues with that system)

Potentially affects:
Windows Server 2000 (one system running Win2k Server on Intel; no issues
with that system)

I suspect this also affects NT4.0 Server, but I am not sure. Spontaneous
reboots was one of the issues that caused us to replace what was admittedly
a dying machine (hardware from 1997-1998). Nor am I certain that the AMD
processors are the issue -- however strong that evidence looks from this
end. However, I am certain that NAV is not the problem.








"Bill Leary" wrote in message
...
"Earl" wrote in message
...
At this time, it appears the issue is common to systems running AMD
processors (now aint that a surprise),

Both of my machines here run AMD Athelon XP processors. The machine at my
son's
apartment is a AMD on an accellerator card that replaced the Pentum (one)
in an
old Micron Millenium.

although the interaction of various video cards may actually be
at fault.

Hmmm. This one has a RADEON 9000 AGP, the other a VIA/S3G KM400 (on-board
video), the one over there is an S3, but I don't recall the details at the
moment.

Regardless, at this time, I see no workaround except to remove 891711.

All these are running without any problems.

- Bill

"Earl" wrote in message
...
I don't have the full answer Bill; wish I did. Right now all I have to go on
is the commonality of the error to the machines that it has affected
adversely.

I see on a reread that it may have sounded like I was trying to refute your
point. Sorry about that. Rather, since you were investigating, I was trying to
add to your data points.

Thus, the problem with KB891711:

Affects:
Windows ME (1 system on an AMD processor with the reboot issue)
Windows 2000 (6 systems running; 3 on Intel processors/motherboards with no
issues; 3 with old AMD processors with the reboot issue)

Ah. OK, in that vein, the two machines here are "new" AMDs. I've just given my
son a call, since he has an "old" AMD (400MHz) and he reports that since he's
applied the update he's had a couple of surprise reboots of his machine. He's
using the Opera browser, and when he hit a link on a page the machine just
rebooted as if he'd hit the reset button.

I'll have him kill KB891711 and see if it makes a difference.

Does not affect:
((..omitted..))

Nor am I certain that the AMD processors are the issue -- however
strong that evidence looks from this end.

You may be on to something about age, or generation, though.

- Bill

Yup, that's me.

--
Andrew Bowie

www.users.on.net/abowie


At this time, it appears the issue is common to systems running AMD
processors.

Earl wrote:
I don't have the full answer Bill; wish I did. Right now all I have to go on
is the commonality of the error to the machines that it has affected
adversely. Thus, the problem with KB891711:

Affects:
Windows ME (1 system on an AMD processor with the reboot issue)
Windows 2000 (6 systems running; 3 on Intel processors/motherboards with no
issues; 3 with old AMD processors with the reboot issue)

Does not affect:
Windows XP Pro (3 systems running on Intel processors, no issues)
Windows XP Home (5 systems running on Intel processors; no issues)

Probably does not affect:
Windows Server 2003 (one system running Win2003 Server OS on Intel; no
issues with that system)

Potentially affects:
Windows Server 2000 (one system running Win2k Server on Intel; no issues
with that system)

I suspect this also affects NT4.0 Server, but I am not sure. Spontaneous
reboots was one of the issues that caused us to replace what was admittedly
a dying machine (hardware from 1997-1998). Nor am I certain that the AMD
processors are the issue -- however strong that evidence looks from this
end. However, I am certain that NAV is not the problem.








"Bill Leary" wrote in message
...

"Earl" wrote in message
...

At this time, it appears the issue is common to systems running AMD
processors (now aint that a surprise),

Both of my machines here run AMD Athelon XP processors. The machine at my
son's
apartment is a AMD on an accellerator card that replaced the Pentum (one)
in an
old Micron Millenium.


although the interaction of various video cards may actually be
at fault.

Hmmm. This one has a RADEON 9000 AGP, the other a VIA/S3G KM400 (on-board
video), the one over there is an S3, but I don't recall the details at the
moment.


Regardless, at this time, I see no workaround except to remove 891711.

All these are running without any problems.

- Bill





Earl,

You've struck paydirt. Older processors are not compatible
with that fix. Only Athlon 700mhz up and newer Intel
processors are compatible. Its not the OS, Its the chip.

--
Lester Stiefel
In Romans 1 there are qualities of Unregenerate man listed
which describe him in the last days.
Is your quality found on this list??

"Lester Stiefel" wrote in message
...
You've struck paydirt. Older processors are not compatible
with that fix. Only Athlon 700mhz up and newer Intel
processors are compatible. Its not the OS, Its the chip.

Where did you come by this information, please?

It looks like I'll have to have my son disable KB891711, since he's got a 400MHz
AMD in his system and *is* having problems. The two machines here have 1700 and
1900 AMDs and are having no problems.

- Bill

The KB891711 update worked fine on my WinMe PIII 1GHz system. I have it
listed in Add/Remove and the KB891711 runs at startup. BTW: I'm also running
NAV2005.

Steve

"Bill Leary" wrote in message
...
"Lester Stiefel" wrote in message
...
You've struck paydirt. Older processors are not compatible
with that fix. Only Athlon 700mhz up and newer Intel
processors are compatible. Its not the OS, Its the chip.

Where did you come by this information, please?

It looks like I'll have to have my son disable KB891711, since he's got a
400MHz
AMD in his system and *is* having problems. The two machines here have
1700 and
1900 AMDs and are having no problems.

- Bill

I appreciate that some machines may be "too old" to use the patch but many of
us can't afford to upgrade our PCs on a regular basis.
Now I am using Winme version 4.90.3000 with an 866 pentium lll with 256ram.I
have tried unchecking in startup with some success as regards
opening/shutting down but system still "hung" and froze so I uninstalled it
using add/rempve. The system still freezes for several minutes especially
when on the internet (some of these messages actually took several minutes to
appear and the screen stopped responding although I could still run other
operations on the PC. The total freeze seems to have stopped to be replaced
by this shorter freeze (and the PC access light doesn't flash - it just does
nothing).Another peculiar thing that has started is my USB disc (I have 2
used for storage purposes). I am now (although not every time) getting a
scandisc run on startup saying that one of the drives was not shut down
correctly. Now, as the patch has been removed from the system, why should it
still be causing problems? It was the correct patch (downloaded from the
Windows update site on 11th March 2005). Does it leave something lurking on
the PC? Alas, as it decided to also remove all my restore points, I cannot
roll back the system. Has anyone looked through say, the registry, to see if
something gets left behind after using the add/remove program to get rid of
it which may be causing problems? I have seen mention of problems removing it
with the add/remove although they gave no solutions.
I can say with reasonable certainty that it is the patch causing the
problems as I downloaded and installed it and shut down for the night and the
problems appeared the next time I switched on.is there a list anywhere of
what the patch actually puts into the pc so we can check that they have all
been removed (not just the folder items)?
Hillneerg

"Bill Leary" wrote:

"Lester Stiefel" wrote in message
...
You've struck paydirt. Older processors are not compatible
with that fix. Only Athlon 700mhz up and newer Intel
processors are compatible. Its not the OS, Its the chip.

Where did you come by this information, please?

It looks like I'll have to have my son disable KB891711, since he's got a 400MHz
AMD in his system and *is* having problems. The two machines here have 1700 and
1900 AMDs and are having no problems.

- Bill

The patch runs fine on my 5 yr old PIII, 700Mhz. I had many of the
symptoms you describe but it turned out to be something unrelated to
the patch.
-------
On Mon, 14 Mar 2005 07:21:05 -0800, Hillneerg
wrote:

I appreciate that some machines may be "too old" to use the patch but many of
us can't afford to upgrade our PCs on a regular basis.
Now I am using Winme version 4.90.3000 with an 866 pentium lll with 256ram.I
have tried unchecking in startup with some success as regards
opening/shutting down but system still "hung" and froze so I uninstalled it
using add/rempve. The system still freezes for several minutes especially
when on the internet (some of these messages actually took several minutes to
appear and the screen stopped responding although I could still run other
operations on the PC. The total freeze seems to have stopped to be replaced
by this shorter freeze (and the PC access light doesn't flash - it just does
nothing).Another peculiar thing that has started is my USB disc (I have 2
used for storage purposes). I am now (although not every time) getting a
scandisc run on startup saying that one of the drives was not shut down
correctly. Now, as the patch has been removed from the system, why should it
still be causing problems? It was the correct patch (downloaded from the
Windows update site on 11th March 2005). Does it leave something lurking on
the PC? Alas, as it decided to also remove all my restore points, I cannot
roll back the system. Has anyone looked through say, the registry, to see if
something gets left behind after using the add/remove program to get rid of
it which may be causing problems? I have seen mention of problems removing it
with the add/remove although they gave no solutions.
I can say with reasonable certainty that it is the patch causing the
problems as I downloaded and installed it and shut down for the night and the
problems appeared the next time I switched on.is there a list anywhere of
what the patch actually puts into the pc so we can check that they have all
been removed (not just the folder items)?
Hillneerg

"Bill Leary" wrote:

"Lester Stiefel" wrote in message
...
You've struck paydirt. Older processors are not compatible
with that fix. Only Athlon 700mhz up and newer Intel
processors are compatible. Its not the OS, Its the chip.

Where did you come by this information, please?

It looks like I'll have to have my son disable KB891711, since he's got a 400MHz
AMD in his system and *is* having problems. The two machines here have 1700 and
1900 AMDs and are having no problems.

- Bill




ET