From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_07B3_01C3D249.54624DC0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   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_07B3_01C3D249.54624DC0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   As
expected.  The =
update history=20
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=20
    history is just a for your benefit.  It has no purpose other =
than=20
    that.  If you want to reset your client settings you can delete =

    \Program Files\WindowsUpdate.  Kill the whole directory and =
your next=20
    visit to Windows Update will reinitialize the client =
side.
     
       None
of this affects =
the selection=20
    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 in=20
      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 you=20
      up to date install> >> ||to your
non-up-to-date  =

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

------=_NextPart_000_07B3_01C3D249.54624DC0--

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