From: Kota on
Hi,

We have signed a driver using verisign authenticode signature and we are
supporting OS versions from XP to WIN-7 for both 32, 64 bit.

Driver signing worked fine for below OS:
XP-32,64, Server 2003-32, Vista 32, Win-7 32 & 64.

Not worked:
-----------
Server 2008, Vista 64.

Single binary is used for all 32 bit OS, using WDK-600 xp-32 free build env
Single binary is used for all 64 bit OS, using WDK-600 Server2003-64 free
build env

Vista-64 Device manager shows Code-39.
I have connected the windbg and loaded driver by same method. It works fine,
because it is in debug mode. I confirmed that, It is signing related problem
in above OS by windbg, Am i correct?

In Vista64, Looked at Eventlogs in Device manager under "Audit Failure", It
shows myDriver.sys is having Invalid hash file.

But same binaries worked for Win-7 64.

Development Tools used:
--------------------------
WDK-6000 driver development
WDF-xxx15 coinstaller dll ==> so that, I don't need to restart in lower OS
instead of WDF-xxx19.

Inf2Cat(driver signing) ---WDK7600 Inf2cat is used for signing the catalogue
file, because 7600 supports Win-7.

Below is the only specifying individual OS for catalogue file generation:

-----------------------bat file for generating catalogue file------
stampinf -f pmc55xx.inf -v %VERSION%
pause
cls

pause

INF2CAT /driver:%CURDIR%\ForSigning\xp-32
/os:XP_X86,Server2003_X86,Vista_X86,Server2008_X86,7_X86

popd
pause

pushd ForSigning\xp-64
Pause
cls

stampinf -f pmc55xx.inf -v %VERSION%
pause
cls

pause
INF2CAT /driver:%CURDIR%\ForSigning\xp-64
/os:XP_X64,Server2003_X64,Vista_X64,Server2008_X64,Server2008R2_X64,7_X64

---------------------------------------------------------------
We having signed the catalogue file only and proivded the inf,sys,dll other
files.

I am not sure what else I should provide for this case, working for most of
the OS, but not for all. Please let me know, if you require more info.

Appreciate your thoughts & inputs.

Thanks,
Kota