From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_01D6_01C3EE62.96FDFFA0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   OK.  Either way, it is after Windows Update verification which takes =
place before anything installs.  The messages you describe are from the =
installer.  It may be that they are telling you that you have a =
non-certified video or sound driver.  Without seeing the message = anything
would just be a guess.  Anyway, nothing to do with verification = of signed
downloads.

Rich

  "Jan van Hoek (NL)"  wrote in message =
news:VA.000001db.0056ecbd{at}xs4alldot.nl...
  >> since you downloaded the file from the download center,
  >> Windows Update and its verification mechanism
  >> are not involved in any way.

  I knew of no other way to reconstruct the error message you asked=20
  for. Anyway, it is the very same error message as I received via=20
  Windows Update, so my point still stands.

  And I wouldn't be surprised when the underlying download proved to=20
  be exactly the same as what one receives via Windows Update. IOW=20
  the "unsigned" popup appears at a moment that Windows Update=20
  already has done its job, being just a forefront for getting=20
  things that are also present via the Download Center. Pure=20
  speculation, of course, but I don't think that I'm far from the=20
  truth.
  --=20
  -- Jan van Hoek (NL)
  -- Mon 9 Feb 2004 01:19 CET

  PS: As someone mostly well informed about MS related issues, do=20
  you by any chance know a way out of my OP question??


------=_NextPart_000_01D6_01C3EE62.96FDFFA0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








  
OK.  Either way, it =
is after=20
Windows Update verification which takes place before anything =
installs. =20
The messages you describe are from the installer.  It may be that
= they are=20
telling you that you have a non-certified video or sound driver. 
= Without=20
seeing the message anything would just be a guess.  Anyway,
nothing = to do=20
with verification of signed downloads.
 
Rich
 

  "Jan van Hoek (NL)" <janvanhoekAT{at}xs4allDOT.nl&g=">mailto:janvanhoekAT{at}xs4allDOT.nl">janvanhoekAT{at}xs4allDOT.nl&g=
t;=20
  wrote in message news:VA.000001db.0056ecbd=
{at}xs4alldot.nl...>>=20
  since you downloaded the file from the download center,>> =
Windows=20
  Update and its verification mechanism>> are not
involved in =
any=20
  way.I knew of no other way to reconstruct the error message =
you asked=20
  for. Anyway, it is the very same error message as I received via=20
  Windows Update, so my point still
stands.And I wouldn't be =

  surprised when the underlying download proved to be exactly the =
same as=20
  what one receives via Windows Update. IOW the
"unsigned" popup =
appears at=20
  a moment that Windows Update already has done its job, being just =
a=20
  forefront for getting things that are also present via the =
Download=20
  Center. Pure speculation, of course, but I don't think that I'm =
far from=20
  the truth.-- -- Jan van Hoek
(NL)-- Mon 9 Feb 2004 =
01:19=20
  CETPS: As someone mostly well informed about MS related =
issues, do=20
  you by any chance know a way out of my OP=20
question??

------=_NextPart_000_01D6_01C3EE62.96FDFFA0--

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