I think you were referring to his post on comparing identical HP Pavillion
machines, which I read with interest. While the only "apparent" difference
was the inclusion of an anti-virus program on the offending machine, I view
that as a trigger for what he calls the "lame-patch", rather than the root
cause. I had a web-game on one system which triggered the instant-reboot,
but again, the game was not the issue, rather 891711 was the culprit.
Frankly, I am shocked that Microsoft would release this patch to the ME
community given it's nearly 2-month adverse history on Win2k machines (my
date said 1/25/05, but another poster said it was released earlier in
January). ME machines have nowhere near the inherent stability of a Win2k
system as it is, and so to unleash a psuedo-virus into that community when
they were aware of existing problems with 891711 approaches
irresponsibility. I don't say this just to blast Microsoft, as I develop
with their tools, use their products extensively, and have had excellent
support from some of their personnel. But in this case, the ball was dropped
badly.
"Jack E Martinelli" wrote in message
...
Thank you, Earl. Jim can get it to the right people.
And see Norman Miller's very helpful recent posts about this issue.
I believe we have several reports of trouble on Celeron machines now.
Most problematic machines seem to be older, slower boxes, running Win9X or
W2K.
And we must keep in mind that there may be more than one cause.
Probable date for a new patch is April 12, if past WU history is any
guide.
--
Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS
Help us help you: http://www.dts-L.org/goodpost.htm
http://www.microsoft.com/athome/secu...t/default.aspx
In Memorium: Alex Nichol
http://www.microsoft.com/windowsxp/e...ts/nichol.mspx
Your cooperation is very appreciated.
------
"Earl" wrote in message
...
Jack,
I did copy the body of my most recent post on this subject to Jim.
I've not yet seen this issue arise on any Intel machines, yet as I
indicated
in my post, I've not seen any evidence to indicate this was an absolute
exclusion. But I've also not seen any posts that convince me that this
patch
is affecting Intel machines. Some issues that folks are attributing to
891711 are simply unrelated to this patch (I would certainly not apply
this
patch to a system that already had issues!). However, given the diversity
of
hardware that Intel has created over the years, it would not totally
surprise me. Yet the instruction sets in the processors differ more
between
Intel and non-Intel than across various generations of Intel chips. It's
been a number of years, but if I recall correctly, the interrupts are
wired
differently also on non-Intel CPUs. Whether or not that is the issue, I
doubt we'll ever hear. I suspect Microsoft will simply release an updated
patch at some point.
"Jack E Martinelli" wrote in message
...
Thank you very much, Earl.
I urge you to copy this post to Jim Eshelman using the Feedback tool at
his
website:
www.aumha.org
He has much better connections with MS than I do.
The 891711 problem is now clearly NOT confined to AMD cpu's.
I am not aware of any reported extensive correlations with the video
adapter
or its driver yet, just some vague murmerings. We should explore this
possibility.
--
Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS
Help us help you: http://www.dts-L.org/goodpost.htm
http://www.microsoft.com/athome/secu...t/default.aspx
In Memorium: Alex Nichol
http://www.microsoft.com/windowsxp/e...ts/nichol.mspx
Your cooperation is very appreciated.
------
"Earl" wrote in message
...
Jack,
The problem absolutely affects Win2k as well as WinME (see my threads
from
last month in the microsoft.public.win2000.windows_update forum).
Apparently
everyone was still oblivious to this issue in February, as not one
person
responded to any of my threads. In any event ...
Once 891711 has been installed, the problem seems to arise due to a
problem
with the hardware and or drivers not being able to process graphics
properly. It appears that 891711 is intercepting some of the graphic
data
and "re-handling" it.
Intel systems appear to be nearly, if not completely unaffected by the
problem, which tells me that the patch was most likely tested on Intel
machines only.
Non-Intel hardware appears to be solely or mostly affected by this
problem.
In particular, older AMD systems are universally afflicted. I can only
speculate that this has something to do with the way interrupts are
handled
at the processor. In any event, further testing on this patch with
non-Intel
systems needs to be done.
This is not a software issue, although many deceptive symptoms make it
appear so. Exiting game software, running your cursor over hot-links,
anti-virus activity, changing windows, stacking windows, etc. -- any
number
of graphic related events will cause the reboot or "BSOD". In many
cases,
an
891711-afflicted system will apparently reboot itself for no reason at
all.
Hopefully you can send that information "upstairs".
"Jack E Martinelli" wrote in message
...
Ditto, Bill. Thank you.
-------
May I report that I've just heard from Jim Eshelman about the
KB891711
problem.
He is unable to offer anything new to our discussion.
His recommendation is to disable or uninstall the update until MS
offers
a
new fix.
He seems to think the problem is restricted to Win9X machines, but I
think
some W2K boxes have been hit, too.
I have no idea yet what the cause may be, despite several earlier
promising suggestions.
--
Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS
Help us help you: http://www.dts-L.org/goodpost.htm
http://www.microsoft.com/athome/secu...t/default.aspx
In Memorium: Alex Nichol
http://www.microsoft.com/windowsxp/e...ts/nichol.mspx
Your cooperation is very appreciated.
------
SNIP