WinUSB install on Vista 64

> Yes they are, Build for 64 since Windows 2000 DDK

2003 DDK was the first with x64 env :-)

--
Maxim S. Shatskih
Windows DDK MVP

http://www.storagecraft.com

>"Maxim S. Shatskih" <> wrote in message news:...
>> Yes they are, Build for 64 since Windows 2000 DDK
>
>2003 DDK was the first with x64 env :-)
>
"Denis @ TheOffice" <> wrote:

>No it was not, check again. attached is the setenv for 64 bit in NT 2000 DDK build in 1999.

That's Itanium. Maxim was talking about x64.
--
Tim Roberts,
Providenza & Boekelheide, Inc.

"Denis @ TheOffice" <> wrote:
>>
>If I understand you.
>I think I may have had the wrong kind of signature from VeriSign then.
>I think they gave me user mode kind for web content, activex, cabs and so on...
>Although, I specifically ask the guy for "Drivers" I should have said "Kernel mode"
>Could that be possible?

If it is a Verisign Class 3 Code-Signing Certificate, then I think you are
golden for KMCS.
--
Tim Roberts,
Providenza & Boekelheide, Inc.

Yes, I know but still 64 and it was building... Never try till x64 XP.


"Tim Roberts" <> wrote in message news:...
> >"Maxim S. Shatskih" <> wrote in message news:...
>>> Yes they are, Build for 64 since Windows 2000 DDK
>>
>>2003 DDK was the first with x64 env :-)
>>
> "Denis @ TheOffice" <> wrote:
>
>>No it was not, check again. attached is the setenv for 64 bit in NT 2000 DDK build in 1999.
>
> That's Itanium. Maxim was talking about x64.
> --
> Tim Roberts,
> Providenza & Boekelheide, Inc.

It says :
CN = VeriSign Class 3 Code Signing 2009-2 CA

Then why it still doesn't install in Vista 64 bit?



"Tim Roberts" <> wrote in message news:...
> "Denis @ TheOffice" <> wrote:
>>>
>>If I understand you.
>>I think I may have had the wrong kind of signature from VeriSign then.
>>I think they gave me user mode kind for web content, activex, cabs and so on...
>>Although, I specifically ask the guy for "Drivers" I should have said "Kernel mode"
>>Could that be possible?
>
> If it is a Verisign Class 3 Code-Signing Certificate, then I think you are
> golden for KMCS.
> --
> Tim Roberts,
> Providenza & Boekelheide, Inc.

"Denis @ TheOffice" <> wrote:
>
>It says :
>CN = VeriSign Class 3 Code Signing 2009-2 CA
>
>Then why it still doesn't install in Vista 64 bit?

I'm not sure whether I already said this or not, so bear with me.

The Class 3 certificate is used for KMCS. That doesn't have anything to do
with INSTALLATION; if missing, your driver will not LOAD on a 64-bit
system.

The "unsigned driver" warning is an INSTALL time thing, but doesn't affect
anything after installation. To eliminate THAT, you need the WHQL
signature.

So, will your driver INSTALL (after acknowledging the warning), but then it
refuses to LOAD?
--
Tim Roberts,
Providenza & Boekelheide, Inc.

I am also going through this process and think you need WHQL to use driver on 64-bit system not just silent install.

I signed my 64-bit driver and tried to install on Vista.
--- There was unsigned warning <---- OK, expected as I didn't get WHQL signature
--- installation succeeded but the driver didn't load <---- Unexpected as your say

You can load a Class3 signed driver on 64-bit vista if you have turned on the test mode otherwise you can't.

For release purpose you MUST sign with certificate from VeriSign and submit to WHQL, otherwise you can't release. That means WHQL unsigned warning is not just an install time warning it affects after-wards as well.

I want to Thank you for help I finally got it to install as a full release.
To resume as I whish I had a walk thru like this:

(pitfall)The Logo certification is NOT mandatory in order to load a USB driver.
In order to load the package must be signed with a KMCS signature.

The KMCS signature is made based on a certification purchased from an authorized CA vendor,
and a Cross Certificate obtain found at:
http://www.microsoft.com/whdc/winlog...crosscert.mspx

(pitfall)Must also use the signtool provided in the latest WDK (such as WDK 7600.16385.0)
(pitfall)Another thing you can only sign with the computer that the CA certificate was issued.

This example is with a VeriSign spc.
(pitfall) make sure you copy the cross certificate in such a folder...

SignTool sign /v /ac C:\VeriSign\MSCV-VSClass3.cer /s my /n "YOUR CORPORATION REGISTERD TO CA" /t
http://timestamp.verisign.com/scripts/timestamp.dll YourUsb.sys
to verify : Signtool verify /kp /v yourusb.sys

Then generate a cat file for your inf: Assuming your inf is in order.
Inf2Cat /driver:. /os:2000,XP_X86,XP_X64,Server2003_X86,Server2003_X6 4,Server2003_IA64,Vista_X86,Vista_X64 /v

SignTool sign /v /ac C:\VeriSign\MSCV-VSClass3.cer /s my /n "YOUR CORPORATION REGISTERD TO CA" /t
http://timestamp.verisign.com/scripts/timestamp.dll YourCat.cat
to verify : Signtool verify /kp /v /c yourusb.cat yourusb.sys

That is all that is needed.





"Tim Roberts" <> wrote in message news:...
> "Denis @ TheOffice" <> wrote:
>>
>>It says :
>>CN = VeriSign Class 3 Code Signing 2009-2 CA
>>
>>Then why it still doesn't install in Vista 64 bit?
>
> I'm not sure whether I already said this or not, so bear with me.
>
> The Class 3 certificate is used for KMCS. That doesn't have anything to do
> with INSTALLATION; if missing, your driver will not LOAD on a 64-bit
> system.
>
> The "unsigned driver" warning is an INSTALL time thing, but doesn't affect
> anything after installation. To eliminate THAT, you need the WHQL
> signature.
>
> So, will your driver INSTALL (after acknowledging the warning), but then it
> refuses to LOAD?
> --
> Tim Roberts,
> Providenza & Boekelheide, Inc.

"Denis @ TheOffice" <> wrote in message
news:...

> (pitfall)The Logo certification is NOT mandatory in order to load a USB
> driver.
> In order to load the package must be signed with a KMCS signature.

Pitfall: uinless the device belongs to a class that requires WHQL signature.

--pa

That what they want you to believe.

"Pavel A." <> wrote in message news:%...
> "Denis @ TheOffice" <> wrote in message news:...
>
>> (pitfall)The Logo certification is NOT mandatory in order to load a USB driver.
>> In order to load the package must be signed with a KMCS signature.
>
> Pitfall: uinless the device belongs to a class that requires WHQL signature.
>
> --pa
>
>