From: "Robert Comer" 

> This is changing under our feet as we speak.  Today I took a fully-patched
> machine, set to "download, then ask" to WinUpdate.  It
prompted me with a
> standard "may I?" dialog for the asx client v5.  I declined
SP2, and the
> pages
> in MyComputer had already changed to the new style, and WinUpdate, of
> course,
> displayed with the new look.

I'm not surprised. :(

> I also noticed some nice behavior from NIS. (Get thee behind me; shakes
> rattle).  A full (with reboot) update of NIS this week gets the WMI
> client,
> and *intercepts* the security panel installation, advising the user to go
> with
> NIS instead of Windows Firewall.  Accept that, and NIS takes over fully
> and
> properly, as the only firewall.

Oh gak, that's even worse!

- Bob Comer



"Frank Haber"  wrote in message
news:4126540f$1{at}w3.nls.net...
> >This is all easy to recreate, install WinXP (anything apparently), make
> >sure
> auto update is turned off from the get-go (not just prompt)  WU up all the
> patches available -- no security dialog change, turn on autoupdate and
> wait
> for it to cycle, new security dialog.
>
> This is changing under our feet as we speak.  Today I took a fully-patched
> machine, set to "download, then ask" to WinUpdate.  It
prompted me with a
> standard "may I?" dialog for the asx client v5.  I declined
SP2, and the
> pages
> in MyComputer had already changed to the new style, and WinUpdate, of
> course,
> displayed with the new look.
>
> I also noticed some nice behavior from NIS. (Get thee behind me; shakes
> rattle).  A full (with reboot) update of NIS this week gets the WMI
> client,
> and *intercepts* the security panel installation, advising the user to go
> with
> NIS instead of Windows Firewall.  Accept that, and NIS takes over fully
> and
> properly, as the only firewall.
>

--- BBBS/NT v4.01 Flag-5