Archived from groups: alt.sys.pc-clone.dell (
More info?)
"Joe Morris" <jcmorris@mitre.org> wrote in message
news:cffpj2$l4a$1@newslocal.mitre.org...
> "S.Lewis" <stew1960@cover.bellsouth.net> writes:
>
>>At least for the moment, it appears MS wants to 'cascade' the downloads
>>via
>>'automatic updates', as the download doesn't appear via "Windows Update"
>>scan this morning (at least for me).
>
> The guidance I've seen says that the sequence will be
>
> * automatic update for systems with beta/RC versions of SP2 (already
> done?)
> * automatic update for other users (16 August)
> * Windows Update (later in the month)
>
> And for corporate users there is a download available that includes
> both a new .ADM (policy) file and a command script, both of which
> temporarily (120 days) disable the ability of either automatic update
> or Windows update to pick up SP2, which will cause all sorts of
> mischief in enterprise environments.
>
>>I've been running SP RC1 and then RC2 for the last 90 days or so, and my
>>update grabbed the final release this morning. I backed everything up
>>before installing it.. The install while slow, was uneventful.
>
> Single-data-point: on a 700 MHz laptop (OmniBook 500) the install takes
> approximately one hour.
>
> Problems I've seen so far are system hangs (both on the OB500 each time
> I've reimaged it and installed SP2, perhaps ten minutes after the
> reboot -- another tester on a different computer had the system hang
> during the reboot) and bogus "power spike in the USB interface" warnings
> when the laptop is redocked.
>
>>You can choose to turn off the XP firewall and auto updates if desired
>>during the install. It's just that the user is forced to interact/choose
>>the status of those, as well as the status of any AV program installed on
>>the machine.
>
> The problem now is that many/most of the existing third-party AV and
> firewall products aren't yet SP2-aware and thus are not recognized by
> the "security center" introduced by the service pack.
>
> Joe Morris
Joe,
Informative post. The worst side-effects I've seen to this point: 1)
having to re-enable HTML and attachment (security) settings in OE, as both
are prevented/disabled by default after the SP2 'upgrade'. (I use a mail
filter that allows viewing on the server prior to bringing messages down).
I also noticed (on my P4 2.0 homebuild with XP Pro) a temporary
slowdown/hang at shutdown during the 'windows is shutting down' splash,
though that seems to have cleared up.
Also, the default "automatic update" settings attempt to bring *all updates*
down (including non-criticals) if the preferences aren't altered, which is
going to stink up some devices (particularly video cards) in all likelihood.
I had noticed as well the MS announcement that
arrangements/patches/workarounds were being made for those administering
networks to delay bringing SP2 down until those folks could estimate any
negative impact on a controlled basis.
Stew