Thomas
Thu Aug 19 21:37:31 CDT 2004
On June 29, 2004 Eirk[MSFT] gave an explanation for this. See:
http://groups.google.com/groups?q=+%22driver+installation%22+author:erik&hl=en&lr=&ie=UTF-8&selm=40e2092c%241%40news.microsoft.com&rnum=2
Good luck,
Thomas F. Divine, Windows DDK MVP
http://www.rawether.net
"Abhishek R [MSFT]" <abhishek@online.microsoft.com> wrote in message
news:41255c7e@news.microsoft.com...
> WHQL digitial signature is *not* a requirement with the DIFx tools.
> Authenticode should work fine too. The samples that shipped with the DIFx
> tools are actually signed with authenticode certificates, and not WHQL
> certificates.
>
> Not sure why you are seeing the error with your authenticode certificate.
>
> --
> This posting is provided "AS IS" with no warranty, and confers no rights.
>
> "Duane Johnson" <duane___@wrq.com> wrote in message
> news:%23hRywm6gEHA.712@TK2MSFTNGP09.phx.gbl...
> > I've been trying to use the DIFxAPP code to install our NFS Client
Device
> > driver and have been running into problems. The DIFxAPP code requires a
> > WHQL digital signature.for use with Windows 2000 and XP. Since we have
no
> > hardware we cannot take advantage of that program. An Authenticode
> > signature can be used for Windows Server 2003, but apparently not for
> > Win2k
> > and XP (According to the Authenticode doc anyway). Has anyone else run
> > into
> > this problem? Any workarounds?
> >
> > Does anyone know why a WHQL digital signature is a requirement? Any
idea
> > if
> > this requirement might be relaxed in the future?
> >
> >
> > The error that cat get past is 0x800B0100L which is "No signature was
> > present in the subject."
> >
> > I have supplied an Authenticode signiture, so I'm guessing that it
wants
> > a
> > WHQL digital signature, correct?
> >
> > Regards,
> >
> > Duane Johnson
> > WRQ, Inc.
> >
> >
>
>