From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_063D_01C4821E.784E1770
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   I believe so.

Rich

  "Gregg N"  wrote in message =
news:Xns9545C5B44385Egregginvalidinvalid{at}216.144.1.254...
  "Geo."  wrote in news:411e9a0d{at}w3.nls.net:

  > Oh I understand what you said, but how does it know what files it
  > needs from Windows Update and what files to take from the local
  > machine? Is that process foolproof/bugfree?

  I am only speaking hypothetically, based on my understanding of what =
Rich=20
  said. I don't know for sure how this actually works.

  When it is done taking files from windows update and the local machine =
it=20
  ends up with the exact same service pack, bit-for-bit, which can then =
be=20
  installed. I imagine MD5 or similar checksums are used to verify the =
the=20
  service pack was properly assembled before it is installed. If the=20
  checksum fails, it can tell you you need to obtain the service pack=20
  through other means.

  > I mean think about this
  > for a minute, verifying 100mb of patches or just assuming none are
  > installed and installing everything from a known good source, which
  > seems less error prone?=20

  It wouldn't have to verify patches, it just has to see if the files it =

  needs are present. If they were corrupted, the checksum on the service =

  pack would fail.

  > installed and installing everything from a known good source, which

  You are using the term "installing", when you should be using the term =

  "downloading". I think it is only the "download" part that is =
different=20
  between the WU route and the complete download route. Once the =
download=20
  phase is complete, the "install" part is the same.

  Is my understanding correct, Rich?

  Gregg
------=_NextPart_000_063D_01C4821E.784E1770
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   I believe
so.
 
Rich
 

  "Gregg N" <gregg{at}invalid.invalid>">mailto:gregg{at}invalid.invalid">gregg{at}invalid.invalid>
=
wrote in=20
  message news:Xns9=
545C5B44385Egregginvalidinvalid{at}216.144.1.254..."Geo."=20
  <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote =
in news:411e9a0d{at}w3.nls.net:&g=
t; Oh I=20
  understand what you said, but how does it know what files it> =
needs=20
  from Windows Update and what files to take from the local> =
machine? Is=20
  that process foolproof/bugfree?I am only speaking =
hypothetically,=20
  based on my understanding of what Rich said. I don't know for sure =
how=20
  this actually works.When it is done taking files from windows =
update=20
  and the local machine it ends up with the exact same service pack, =

  bit-for-bit, which can then be installed. I imagine MD5 or similar =

  checksums are used to verify the the service pack was properly =
assembled=20
  before it is installed. If the checksum fails, it can tell you you =
need to=20
  obtain the service pack through other
means.> I mean =
think=20
  about this> for a minute, verifying 100mb of patches or just =
assuming=20
  none are> installed and installing everything from a known good =
source,=20
  which> seems less error prone? It
wouldn't have to =
verify=20
  patches, it just has to see if the files it needs are present. If =
they=20
  were corrupted, the checksum on the service pack would =
fail.>=20
  installed and installing everything from a known good source, =
whichYou=20
  are using the term "installing", when you should be using the term=20
  "downloading". I think it is only the
"download" part that is =
different=20
  between the WU route and the complete download route. Once the =
download=20
  phase is complete, the "install" part is the
same.Is my=20
  understanding correct,
Rich?Gregg

------=_NextPart_000_063D_01C4821E.784E1770--

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