The INQUIRER has heard now of three occasions where the SP3 install caused a local ruckus.
That's not that many however, considering the thousands of bug fixes that must have been downloaded already.
In the first case, a UK company attempted to install SP3 on two machines, one a Dell P3 550 and the other a Mesh XP 1.4.
The systems, said the end users, have nothing in common but produced exactly the same blue screen of death - a message about a non page fault.
The boys told us that on the Dell they didn't back up the previous install and had to re-install the entire OS. On the Mesh they made a backup, so when the BSOD arrived, went into safe mode, logged on as admin and removed the service pack.
They said that you have to say "yes" to back up your settings when the SP is first run to avoid potential calamity.
The third case we've heard about also caused a STOP situation - the user sent us a screen shot of the death, which you can find below.
Another reader downloaded SP3 but said that Microsoft has significantly changed their terms and conditions, with this paragraph: "The OS Product or OS Components contain components that enable and facilitate the use of certain Internet-based services. You acknowledge and agree that Microsoft may automatically check the version of the OS Product and/or its components that you are utilizing and may provide upgrades or fixes to the OS Product that will be automatically downloaded to your computer."
He said that acceptance of this means Microsoft can now auto-download code to W2K computers, without authorisation or knowledge, and he's decided not to install the patch because of the change. SP2's Ts&Cs had no such stipulation."
So be warned, folks, and be careful... ยต