Archived from groups: alt.sys.pc-clone.gateway2000 (
More info?)
Great rant! Couldn't have ranted better myself! I agree completely. Today I
just rolled back a relatively new Dell Centrino-powered notebook to SP1, because
it got all hosed up by SP2 and could not connect to the internet. My suspicion
is that a computer needs to be absolutely clean and free of viruses, malware,
spyware and other nasties to have a snowball's chance in hell of working with
SP2. I will also guess that there was much discussion in the corridors of
Redmond about how to con more people into using SP2, and that Microbloat's
recent acquisition of Giant anti-spyware and some threat removal tools is an
attempt to paint a picture (caricature? cartoon?) of a company that has taken
security and reliability to heart. Horsefeathers! ... Ben Myers
On Fri, 14 Jan 2005 18:26:58 GMT, ".@." <.@.net> wrote:
>On Fri, 14 Jan 2005 12:40:45 GMT, "WDS" <WDS@reply.via.newsgroup.only>
>wrote:
>
>>I don't know if this problem is common to these machines
>
>The SP2 Abortion is a common cause of system destruction to many
>systems and is not just brand, chipset, etc. specific. M$ tech
>themselves have been quoted as telling crashed system owners that they
>just don't know why SP2 will not work with their system.
>
>The biggest problem is an arrogant attitude by M$ and those cloned
>little mouthpieces of theirs out there running around trying to put a
>warm fuzzy face on SP2. M$ and those MVP clones keep pushing their
>idea that they put a piece of software out on the market and if
>existing systems that are already running just fine crash because of
>their upgrade, then it is the system's fault, not the upgrade. If
>existing software already on the market that is and has been running
>just fine fails with the installation of SP2, then the fault is the
>existing software that was already running just fine, NOT SP2. See
>the attitude I am talking about?
>
>Go onto M$ NG's and see what most of these cloned M$ MVP's say when
>SP2 brings a system to its knees. "Well, your system must have
>problems" or "your system is incompatible with SP2" or other sorted
>displays of M$ bull. Never does it ever enter their cloned little
>brains that Hey!, the system/software was running just fine before
>SP2, then it must be SP2 that was not compatible with the
>system/software instead of the system/software not being compatible
>with SP2. And..... If you point that obvious observation out to
>them, then get ready for a good bucket of M$ flaming and character
>assassination coming back at you. Then after you complain about the
>personal attacks, then come back and say "what attacks" even when
>quoting the actual attack.
>
>If you developed a piece of software and when putting it on the
>market, found that it brought a big amount of systems to their knees,
>do you think the public would buy the argument that it was the fault
>of their systems, systems that were already running just fine? You
>could if you had a bunch of mindless clones (M$ calls them MVPs) out
>their trying to brain wash an already easily manipulated public into
>thinking the whole mess was their fault and the faults of their sorry
>systems.
>
>10 to 1 some M$ MVP will lurk by here and jump all over this message.
>They will first misquote what was said, then lie about misquoting even
>when quoting what was misquoted in their attack. Then they will tell
>you that your system is at fault for running just fines before SP2 and
>not after SP2 because SP2 is M$ and M$ is their God of Gods.
>
>The best advice I read about installing SP2 on systems that SP2 was
>incompatible with (M$ calls if systems that are incompatible with
>SP2), is to do a complete system restore and load ONLY XP. If other
>software applications are loaded automatically with your specific
>restoration process, then uninstall them. All you should have
>installed, loaded and running is XP and whatever drivers are needed
>for your system to function at the most basic level. Then, install
>the dreaded SP2 update and see if it takes. If the system blows, then
>SP2 is not compatible with your already running system (M$ calls it
>your system not being compatible with SP2).
>
>Remember, when SP2 was first thrown on the public, Corporate HQ of IBM
>and the US DOD sent notices out to all involved in their higher
>echelon that SP2 was to NOT be attempted. They didn't want their
>networks brought to their knees and when it comes to the DOD, neither
>do we. I don't know about IBM Corporate now but an associate that
>still works with DOD says that most of their high level nets are still
>not running SP2.
>
>According to him, they already have On-Property M$ reps subcontracted
>to supply 24/7 hands on systems maintenance. They instructed these M$
>Reps to do SP2 upgrades to systems on some Pentagon nets one computer
>at a time. They had so many failures at the start that they halted
>any further attempts on the rest of the systems. On the systems that
>SP2 brought down in the initial try to install SP2, he said that the
>M$ reps had no idea why on about half of those systems and could not
>get SP2 to take no matter what. In other words, not even M$ knew why
>on half the failed SP2 attempts.