From: "Rich" 

This is a multi-part message in MIME format.

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

   Sure they can.  Security fixes between service packs can be found at =
http://www.microsoft.com/security.  Service packs contain more than just =
security fixes.  If you get and install a private hotfix between service =
packs you have to pay greater attention and should discuss with the = folks
supplying you the hotfix what else you installed to ensure = everyone is on
the same page.  Of course, unless you have a need I would = recommend
against installing private hotfixes because they do not get = the
integration testing that goes into an integrated release like a = service
pack.  As I'm sure is obvious to you, if you make yourself a = custom
install you would surely test the resulting installation you = built before
deploying it if you were wise.  Microsoft does this with = the integrated
service pack installs.

Rich

  "Geo."  wrote in message =
news:3f075dcf$1{at}w3.nls.net...
  The slipstream method you talk about still requires I know and =
download the
  full barrage of patches which is where my complaint originates. You =
have
  totally missed the entire issue. The current patchwork has gotten so =
complex
  even MS can't keep it straight.

  Geo.

  "Rich"  wrote in message news:3f071faf{at}w3.nls.net...
     Put aside George's silly idea that full installs be made available =
to him
  because he is too lazy to create them himself.  (See
  =
http://www.microsoft.com/technet/prodtechnol/windows2000serv/support/spde=
ploy.asp
  and =
http://www.microsoft.com/technet/security/tools/tools/hfdeploy.asp).



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








   Sure they
can.  =
Security fixes=20
between service packs can be found at http://www.microsoft.com/secur" target="new">http://www.microsoft.com/secur=">http://www.microsoft.com/security">http://www.microsoft.com/secur=
ity. =20
Service packs contain more than just security fixes.  If you get = and=20
install a private hotfix between service packs you have to pay greater = attention=20
and should discuss with the folks supplying you the hotfix what else you =

installed to ensure everyone is on the same page.  Of course, =
unless you=20
have a need I would recommend against installing private hotfixes = because they=20
do not get the integration testing that goes into an integrated release = like a=20
service pack.  As I'm sure is obvious to you, if you make yourself
= a custom=20
install you would surely test the resulting installation you built = before=20
deploying it if you were wise.  Microsoft does this with the = integrated=20
service pack installs.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:3f075dcf$1{at}w3.nls.net...The=20
  slipstream method you talk about still requires I know and download=20
  thefull barrage of patches which is where my complaint originates. =
You=20
  havetotally missed the entire issue. The current patchwork has =
gotten so=20
  complexeven MS can't keep it
straight.Geo."Rich" =
<{at}>=20
  wrote in message news:3f071faf{at}w3.nls.net...&nbs=
p; =20
  Put aside George's silly idea that full installs be made available to=20
  himbecause he is too lazy to create them himself. 
(Seehttp://www.microsoft.com/technet/prodtechnol/windows2000serv/supp=
ort/spdeploy.asp">http://www.microsoft.com/technet/prodtechnol/windows200=
0serv/support/spdeploy.aspand=20
  http://www.microsoft.com/technet/security/tools/tools/hfdeploy.as=
p">http://www.microsoft.com/technet/security/tools/tools/hfdeploy.asp;=
).

------=_NextPart_000_017C_01C34346.B7D4E3A0--

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