From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_07E6_01C3D39B.9F4DBF10
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Nothing.  They are always evaluated based on what you have installed. =
If there are some you believe should be offered I would ask for the file =
versions (not timestamps) of the version you have installed and the =
version you believe you should have.

Rich

  "David Blair"  wrote in message =
news:3ff9dea4{at}w3.nls.net...
  What do I do to reset the upgrades?
    "Rich"  wrote in message news:3ff7b2e5$1{at}w3.nls.net...
       As expected.  The update history has no effect on update =
selection.

    Rich

      "David Blair"  wrote in message =
news:3ff673e3$1{at}w3.nls.net...
      Tried just now. Still only sees 2 updates I didn't grab earlier. =
It doesn't list all the fixes post SP1 that should be there.
        "Rich"  wrote in message news:3ff66f60$1{at}w3.nls.net...
           The Windows Update installation history is just a for your =
benefit.  It has no purpose other than that.  If you want to reset your =
client settings you can delete \Program Files\WindowsUpdate.  Kill the =
whole directory and your next visit to Windows Update will reinitialize =
the client side.

           None of this affects the selection of applicable updates.

        Rich

          "David Blair"  wrote in message =
news:3ff59a71$1{at}w3.nls.net...
          I would only replace those files which are the "same"- so both =
the
          Installation History and Windows Update won't have an issue. =
Both
          installation, from an XP perspective, are the same.


          "Jan van Hoek (NL)"  wrote in =
message
          news:VA.000001c6.008cc35e{at}xs4alldot.nl...
          > >> || Why don't you just copy the files
          > >> ||from you up to date install
          > >> ||to your non-up-to-date  install?
          > >> I thought of that, but was unsure if it would be wise.
          >
          > It may prove effective, IF it succeeds. However, if either =
partition is
          > active, you will receive a lot of "file in use" errors, =
which will defeat
          > your purpose.
          >
          > True installation programs (like the Windows Update =
function) have
          > workarounds for that, e.g. via the infamous re-boot. But the =
COPY/XCOPY
          > cannot cope with such situations, and neither does Windows =
Explorer. All
          > will fail to get those files accross.
          >
          > Whether it is unwise to bypass the Windows Update (and =
Restore)
          > functions, noone can tell. For starters, it won't correctly =
update the
          > Add/Remove Programs list, and it will falsify the =
Installation History as
          > displayed by Windows Update. Everyone will advise you =
against such a
          > bypass action. But some of the time you have no alternative =
than to jump
          > blindfolded and hope for the best


------=_NextPart_000_07E6_01C3D39B.9F4DBF10
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








  
Nothing.  They are =
always=20
evaluated based on what you have installed. If there are some you = believe should=20
be offered I would ask for the file versions (not timestamps) of the = version you=20
have installed and the version you believe you should have.
 
Rich
 

  "David Blair" <DRB{at}uspam.udie.net>">mailto:DRB{at}uspam.udie.net">DRB{at}uspam.udie.net>
wrote in =
message=20
  news:3ff9dea4{at}w3.nls.net...
  What do I do to reset the =
upgrades?
  

    "Rich" <{at}> wrote in message news:3ff7b2e5$1{at}w3.nls.net...
       As
expected.  The =
update=20
    history has no effect on update selection.
     
    Rich
     
    

      "David Blair" <drb{at}u-spam-u-die.com>">mailto:drb{at}u-spam-u-die.com">drb{at}u-spam-u-die.com>
=
wrote in=20
      message news:3ff673e3$1{at}w3.nls.net...
      Tried just now. Still
only sees 2 =
updates I=20
      didn't grab earlier. It doesn't list all the fixes post SP1 that =
should be=20
      there.
      

        "Rich" <{at}> wrote in message news:3ff66f60$1{at}w3.nls.net...
          
The Windows Update =

        installation history is just a for your benefit.  It has no =
purpose=20
        other than that.  If you want to reset your client settings =
you can=20
        delete \Program Files\WindowsUpdate.  Kill the whole =
directory and=20
        your next visit to Windows Update will reinitialize the client=20
        side.
         
          
None of this =
affects the=20
        selection of applicable updates.
         
        Rich
         
        
          "David Blair" <drb{at}u-spam-u-die.com>">mailto:drb{at}u-spam-u-die.com">drb{at}u-spam-u-die.com>
wrote=20
          in message news:3ff59a71$1{at}w3.nls.net...I=20
          would only replace those files which are the "same"- so both=20
          theInstallation History and Windows Update won't have an =
issue.=20
          Bothinstallation, from an XP perspective, are the=20
          same."Jan van Hoek (NL)"
<janvanhoekAT{at}xs4allDOT.nl&g=">mailto:janvanhoekAT{at}xs4allDOT.nl">janvanhoekAT{at}xs4allDOT.nl&g=
t;=20
          wrote in messagenews:VA.000001c6.008cc35e=
{at}xs4alldot.nl...>=20
          >> || Why don't you just copy the
files> >> =
||from=20
          you up to date install> >> ||to your =
non-up-to-date =20
          install?> >> I thought of that,
but was unsure if =
it=20
          would be wise.>> It may prove
effective, IF it =
succeeds.=20
          However, if either partition is> active, you will =
receive a lot=20
          of "file in use" errors, which will
defeat> your=20
          purpose.>> True installation
programs (like the =
Windows=20
          Update function) have> workarounds for that, e.g. via =
the=20
          infamous re-boot. But the COPY/XCOPY> cannot cope with =
such=20
          situations, and neither does Windows Explorer. All> =
will fail=20
          to get those files accross.>>
Whether it is =
unwise to=20
          bypass the Windows Update (and Restore)> functions, =
noone can=20
          tell. For starters, it won't correctly update the> =
Add/Remove=20
          Programs list, and it will falsify the Installation History =
as>=20
          displayed by Windows Update. Everyone will advise you against =
such=20
          a> bypass action. But some of the time you have no =
alternative=20
          than to jump> blindfolded and hope for the=20
        =
best

------=_NextPart_000_07E6_01C3D39B.9F4DBF10--

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