From: "Rich" 

This is a multi-part message in MIME format.

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

      Yes, you are discussing something completely different.  Even =
worse, since you downloaded the file from the download center, Windows =
Update and its verification mechanism are not involved in any way.

Rich

  "Jan van Hoek (NL)"  wrote in message =
news:VA.000001d6.001f340c{at}xs4alldot.nl...
  >> You haven't given enough info to identify
  >> what warning you saw and what component presented it.

  Since I don't want to appear like regular (l)users, who cannot be=20
  bothered to remember the exact error message and the circumstances=20
  in which it appeared, I made an attempt to reconstruct the=20
  problem.

  I started with downloading=20
  http://www.microsoft.com/downloads/details.aspx?FamilyID=3D141d5f9e
  -07c1-462a-baef-5eab5c851cf5&displaylang=3Den>, which is AKA DirectX=20
  9.0b EndUser Runtime. I ran the resulting EXE on my Windows XP Pro=20
  SP1 box, and it installed without a hitch. So far for the good=20
  news. Doing the same on my Windows 2000 Adv Server SP3 box, the=20
  infamous "Digital Signature Not Found" popups appeared, with=20
  "Unknown software package" in the body text.

  FYI: The latter box (showing the problem) is completely up-to-date=20
  in terms of Windows Update (IOW, better patched than the former).=20
  It is my shared external ISP connection with ISA running on it,=20
  hence my eagerness to keep it as up-to-date as humanly possible.

  Further FYI: The offending popup messages appear 2 times during=20
  the installation process.

  Can it be that my inventory of trusted root certificates is not=20
  complete, that being the reason that the signature was not=20
  recognized as a valid one??

  An other cause for this problem can be that I accidentally killed=20
  a necessary background service as part of the OS hardening=20
  process?? This is just a wild guess and not a very likely cause=20
  for these particular popups, because all other downloads (incl.=20
  regular Windows Update runs) proceed without problems, and I may=20
  assume that these are checked for valid signatures too??
  --=20
  -- Jan van Hoek (NL)
  -- Sun 8 Feb 2004 01:57 CET


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








      Yes, you =
are=20
discussing something completely different.  Even worse, since
you=20 downloaded the file from the download center, Windows Update and
its=20 verification mechanism are not involved in any
way.
 
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.000001d6.001f340c=
{at}xs4alldot.nl...>>=20
  You haven't given enough info to identify>> what
warning you =
saw and=20
  what component presented it.Since I don't want to appear like =
regular=20
  (l)users, who cannot be bothered to remember the exact error =
message and=20
  the circumstances in which it appeared, I made an attempt to =
reconstruct=20
  the problem.I started with downloading
<http://www.microsoft.com/downloads/details.aspx?FamilyID=3D141d5f=
9e">http://www.microsoft.com/downloads/details.aspx?FamilyID=3D141d5f9e=
A>-07c1-462a-baef-5eab5c851cf5&displaylang=3Den>,=20
  which is AKA DirectX 9.0b EndUser Runtime. I ran the resulting EXE =
on my=20
  Windows XP Pro SP1 box, and it installed without a hitch. So far =
for the=20
  good news. Doing the same on my Windows 2000 Adv Server SP3 box, =
the=20
  infamous "Digital Signature Not Found" popups appeared, with =
"Unknown=20
  software package" in the body text.FYI: The latter box =
(showing the=20
  problem) is completely up-to-date in terms of Windows Update (IOW, =
better=20
  patched than the former). It is my shared external ISP connection =
with ISA=20
  running on it, hence my eagerness to keep it as up-to-date as =
humanly=20
  possible.Further FYI: The offending popup messages appear 2 =
times=20
  during the installation process.Can it be that my =
inventory of=20
  trusted root certificates is not complete, that being the reason =
that the=20
  signature was not recognized as a valid
one??An other =
cause for=20
  this problem can be that I accidentally killed a necessary =
background=20
  service as part of the OS hardening process?? This is just a wild =
guess=20
  and not a very likely cause for these particular popups, because =
all other=20
  downloads (incl. regular Windows Update runs) proceed without =
problems,=20
  and I may assume that these are checked for valid signatures =
too??--=20
  -- Jan van Hoek (NL)-- Sun 8 Feb 2004 01:57=20
CET

------=_NextPart_000_0193_01C3EE2F.C8FCA520--

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