tommycn wrote:
> all this stuff is crazy. microsoft should fix the patch or
> discontinue it
The many more people who have not had any issue installing the patches in
this thread... I'm sure their systems are just broken in a different way
than those who have had issues. ;-)
It's not the patches - it's the systems in 99% of the cases. Not saying
that Microsoft has not released some bum patches in their day (they
have/do - most seem to center around hardware (thus my suggestion to not get
hardware patches from Microsoft for non-Microsoft hardware)) but when a
patch (or set of patches) does not present trouble on all systems and the
percentage of issues is relatively small - it is logical to perceive that
the trouble is not with the patch, but with some unique attribute (set of
circumstances) on the machines in questions.
Case in point - SP3. When installed on some HP factory installed systems
with AMD processors, bad things happened. Turns out that SP3 didn't have
problems with AMD processors or HP computers or the particular users that
chose to purchase said combination (whether or not they dutifully kept their
systems well maintained or not) - but with the original image applied to
the system by HP being based off their same systems with Intel based
processors (thus not including some things SP3 patched for when it detected
AMD processors.)
This may/may not turn out to be the same case - but so far I have not
witnessed this issue firsthand - and that is several thousand computers of
varying configurations and ages and the likes. Doesn't mean I won't,
doesn't mean much more than I am lucky not to have whatever combination of
circumstances in any of these machines that causes the issues with these
patches. However - it does mean that the problem is not universal. Pulling
the patch because something is wrong with some people's systems - doesn't
seem to be the right move. ;-)
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html