From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0D5E_01C48710.B3ABBE20
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   I was thinking of Windows 98 (not SE) or Windows 95.

Rich

  "Glenn Meadows"  wrote in message =
news:41269759$1{at}w3.nls.net...
  I think 2K is on V4, at least that's the url for all my Win2K =
machines.

  --=20
  Glenn M.


    "Rich"  wrote in message news:4126758f{at}w3.nls.net...
       Windows Update is on its fifth major version.  Migrations are =
always separate for different operating system releases.  I wouldn't be =
surprised if older versions are still on the v3 site.

    Rich

      "Glenn Meadows"  wrote in message =
news:41265bb7{at}w3.nls.net...
      Oh, and the Windows Update site/pages are now different for XP, at =
least if
      SP2 is in place on Pro.  After updating a system using SUS (which =
worked
      great, BTW), I used the regular Windows Update Web Page, to see =
what
      non-critical updates might be there, and I got a request to allow =
the latest
      version of WU to download, so I let it come down (new dialogs =
displaying),
      and then the page was different, with two options, for two =
different styles
      of update.

      Went back with a Win2K machine, and got the old page, so XP is =
migrating to
      a different, maybe more intelligent, or maybe just different =
Update engine.

      --=20
      Glenn M.


      "Robert Comer" 
wrote in message
      news:412656da$1{at}w3.nls.net...
      > > 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.
      > >
      >
      >


------=_NextPart_000_0D5E_01C48710.B3ABBE20
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   I was
thinking of Windows =
98 (not SE)=20
or Windows 95.
 
Rich
 

  "Glenn Meadows" <gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
wrote =
in message=20
  news:41269759$1{at}w3.nls.net...
  I think 2K is on V4, at least that's the url for all my Win2K=20
  machines.
  -- Glenn M.
   
   
  

    "Rich" <{at}> wrote in message news:4126758f{at}w3.nls.net...
      
Windows Update is on =
its fifth=20
    major version.  Migrations are always separate for different =
operating=20
    system releases.  I wouldn't be surprised if older versions are =
still=20
    on the v3 site.
     
    Rich
     
    
      "Glenn Meadows" <gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
=
wrote in=20
      message news:41265bb7{at}w3.nls.net...Oh=
,=20
      and the Windows Update site/pages are now different for XP, at =
least=20
      ifSP2 is in place on Pro.  After updating a system using =
SUS=20
      (which workedgreat, BTW), I used the regular Windows Update =
Web Page,=20
      to see whatnon-critical updates might be there, and I got a =
request to=20
      allow the latestversion of WU to download, so I let it come =
down (new=20
      dialogs displaying),and then the page was different, with two =
options,=20
      for two different stylesof update.Went
back with a =
Win2K=20
      machine, and got the old page, so XP is migrating toa =
different, maybe=20
      more intelligent, or maybe just different Update
engine.-- =

      Glenn M."Robert
Comer" <bobcomer_removeme{at}mindsp=">mailto:bobcomer_removeme{at}mindspring.com">bobcomer_removeme{at}mindsp=
ring.com>=20
      wrote in messagenews:412656da$1{at}w3.nls.net...=
>=20
      > This is changing under our feet as we speak.  Today I =
took=20
      afully-patched> > machine, set to
"download, then =
ask" to=20
      WinUpdate.  It prompted me witha>
> standard =
"may I?"=20
      dialog for the asx client v5.  I declined SP2, and =
the> >=20
      pages> > in MyComputer had already changed to the new =
style, and=20
      WinUpdate, of> > course,>
> displayed with the =
new=20
      look.>> I'm not surprised.
:(>> > I =
also=20
      noticed some nice behavior from NIS. (Get thee behind me; =
shakes>=20
      > rattle).  A full (with reboot) update of NIS this week =
gets the=20
      WMI> > client,> > and
*intercepts* the =
security panel=20
      installation, advising the user togo>
> with> =
>=20
      NIS instead of Windows Firewall.  Accept that, and NIS takes =
over=20
      fully> > and> >
properly, as the only=20
      firewall.>> Oh gak, that's even =
worse!>> - Bob=20
     
Comer>>>>
"Frank Haber" <frhaber{at}N0SPMrcn.com>">mailto:frhaber{at}N0SPMrcn.com">frhaber{at}N0SPMrcn.com>
=
wrote in=20
      message> news:4126540f$1{at}w3.nls.net...=
>=20
      > >This is all easy to recreate, install WinXP (anything=20
      apparently), make> >
>sure> > auto update =
is turned=20
      off from the get-go (not just prompt)  WU up =
allthe> >=20
      patches available -- no security dialog change, turn on autoupdate =

      and> > wait> > for it
to cycle, new security=20
      dialog.> >> > This is
changing under our feet =
as we=20
      speak.  Today I took
afully-patched> > machine, =
set to=20
      "download, then ask" to WinUpdate.  It prompted me =
witha>=20
      > standard "may I?" dialog for the asx client
v5.  I =
declined SP2,=20
      and the> > pages> >
in MyComputer had already =
changed=20
      to the new style, and WinUpdate, of> >
course,> =
>=20
      displayed with the new look.>
>> > I also =
noticed some=20
      nice behavior from NIS. (Get thee behind me; shakes>
>=20
      rattle).  A full (with reboot) update of NIS this week gets =
the=20
      WMI> > client,> > and
*intercepts* the =
security panel=20
      installation, advising the user togo>
> with> =
>=20
      NIS instead of Windows Firewall.  Accept that, and NIS takes =
over=20
      fully> > and> >
properly, as the only=20
      firewall.>=20
>>>

------=_NextPart_000_0D5E_01C48710.B3ABBE20--

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