installing avshws sample driver on Vista 64

Hi,

I have build the sample driver using checked 64 environment.

I have "Windows cannot load the device driver for this hardware. The
driver may be corrupted or missing. (Code 39)" after instaling it.

Has anybody know what can be wrong here?


Regards,
scout

scout119
Tue Oct 16 15:02:50 PDT 2007

On Oct 16, 5:28 pm, scout...@gmail.com wrote:
> Hi,
>
> I have build the sample driver using checked 64 environment.
>
> I have "Windows cannot load the device driver for this hardware. The
> driver may be corrupted or missing. (Code 39)" after instaling it.
>
> Has anybody know what can be wrong here?
>
> Regards,
> scout

Just to confirm that I am using right settings It is WDK 6001 and
"Windows Vista and Windows Server 2008 x64 Checked Build Environment".

Regards,
scout.

Zhou
Tue Oct 16 18:57:19 PDT 2007

>
> Just to confirm that I am using right settings It is WDK 6001 and
> "Windows Vista and Windows Server 2008 x64 Checked Build Environment".

http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/1d8687881797e958

scout119
Tue Oct 16 20:40:11 PDT 2007

On Oct 16, 9:57 pm, Zhou <zhouchangzhi...@gmail.com> wrote:
> > Just to confirm that I am using right settings It is WDK 6001 and
> > "Windows Vista and Windows Server 2008 x64 Checked Build Environment".
>
> http://groups.google.com/group/microsoft.public.development.device.dr...

Sweet!

Thanks a lot.

scout.

scout119
Tue Oct 16 21:57:56 PDT 2007

On Oct 16, 11:40 pm, scout...@gmail.com wrote:
> On Oct 16, 9:57 pm, Zhou <zhouchangzhi...@gmail.com> wrote:
>
> > > Just to confirm that I am using right settings It is WDK 6001 and
> > > "Windows Vista and Windows Server 2008 x64 Checked Build Environment".
>
> >http://groups.google.com/group/microsoft.public.development.device.dr...
>
> Sweet!
>
> Thanks a lot.
>
> scout.

hmm no luck with 6000 as well. Build it, singed it, installed it -
Code 39.

Still need some directions on how to make it to work on vista 64
(ultimate)

Thanks,
scout.

Anatoly
Wed Oct 17 02:38:17 PDT 2007

You may get code 39 on 64 if driver is not properly signed. You need either
to sign your driver or run with debugger connected.

Anatoly.

<scout119@gmail.com> wrote in message
news:1192572170.325132.150480@z24g2000prh.googlegroups.com...
> On Oct 16, 5:28 pm, scout...@gmail.com wrote:
>> Hi,
>>
>> I have build the sample driver using checked 64 environment.
>>
>> I have "Windows cannot load the device driver for this hardware. The
>> driver may be corrupted or missing. (Code 39)" after instaling it.
>>
>> Has anybody know what can be wrong here?
>>
>> Regards,
>> scout
>
> Just to confirm that I am using right settings It is WDK 6001 and
> "Windows Vista and Windows Server 2008 x64 Checked Build Environment".
>
> Regards,
> scout.
>

Gianluca
Wed Oct 17 09:02:56 PDT 2007

Unsigned drivers do not load on Vista 64. You either need to use test
signing or disable signature validation at boot time.

This document explains how to do this

http://www.microsoft.com/whdc/winlogo/drvsign/kmcs_walkthrough.mspx

Have a nice day
GV

--
Gianluca Varenni, Windows DDK MVP

CACE Technologies
http://www.cacetech.com


<scout119@gmail.com> wrote in message
news:1192597076.922594.140200@q5g2000prf.googlegroups.com...
> On Oct 16, 11:40 pm, scout...@gmail.com wrote:
>> On Oct 16, 9:57 pm, Zhou <zhouchangzhi...@gmail.com> wrote:
>>
>> > > Just to confirm that I am using right settings It is WDK 6001 and
>> > > "Windows Vista and Windows Server 2008 x64 Checked Build
>> > > Environment".
>>
>> >http://groups.google.com/group/microsoft.public.development.device.dr...
>>
>> Sweet!
>>
>> Thanks a lot.
>>
>> scout.
>
> hmm no luck with 6000 as well. Build it, singed it, installed it -
> Code 39.
>
> Still need some directions on how to make it to work on vista 64
> (ultimate)
>
> Thanks,
> scout.
>

scout119
Wed Oct 17 12:59:43 PDT 2007

On Oct 17, 5:38 am, "Anatoly Greenblatt" <anatolik_at_email.com>
wrote:
> You may get code 39 on 64 if driver is not properly signed. You need either
> to sign your driver or run with debugger connected.
>
> Anatoly.
>
> <scout...@gmail.com> wrote in message
>
> news:1192572170.325132.150480@z24g2000prh.googlegroups.com...
>
>
>
> > On Oct 16, 5:28 pm, scout...@gmail.com wrote:
> >> Hi,
>
> >> I have build the sample driver using checked 64 environment.
>
> >> I have "Windows cannot load the device driver for this hardware. The
> >> driver may be corrupted or missing. (Code 39)" after instaling it.
>
> >> Has anybody know what can be wrong here?
>
> >> Regards,
> >> scout
>
> > Just to confirm that I am using right settings It is WDK 6001 and
> > "Windows Vista and Windows Server 2008 x64 Checked Build Environment".
>
> > Regards,
> > scout.- Hide quoted text -
>
> - Show quoted text -

Hi Anatoly,

I did everything "by the book" as it described in the
selfsign_readme.html from:

64 bit Vista, WDK 6000, "Windows Vista and Windows Server Longhorn x64
Checked Build Environment"

1. build the code, copied .inf file and .sys to C:\Driver (by the way
why does the name of the output folder has amd64 and not just x64,
just want to be sure that it is ok for Intel 64 as well)
2. Created test certificate in the build environment window: makecert -
r -pe -ss TEST c:\ddk.cer
3. Added it to the system: certmgr -add c:\ddk.cer -s -r localMachine
root
certmgr -add c:\ddk.cer -s -r localMachine trustedpublisher
4. Created cat file: signability /auto /cat /driver:c:\Driver /os:512
5. Signed cat file: signtool sign /s TEST c:\driver\avshws.cat
6. Signed driver file: signtool sign /s TEST c:\driver\avshws.sys
7. Verified it: signtool verify /pa /v c:\driver\avshws.cat (did same
for .sys file as well)
8. Installed the driver and got Code 39.

I've tried to sign .cat only and .sys only as well with the same
result.

What am I doing wrong?

Regards,
scout

scout119
Wed Oct 17 17:36:10 PDT 2007

On Oct 17, 5:38 am, "Anatoly Greenblatt" <anatolik_at_email.com>
wrote:
> You may get code 39 on 64 if driver is not properly signed. You need either
> to sign your driver or run with debugger connected.
>
> Anatoly.
>
> <scout...@gmail.com> wrote in message
>
> news:1192572170.325132.150480@z24g2000prh.googlegroups.com...
>
>
>
> > On Oct 16, 5:28 pm, scout...@gmail.com wrote:
> >> Hi,
>
> >> I have build the sample driver using checked 64 environment.
>
> >> I have "Windows cannot load the device driver for this hardware. The
> >> driver may be corrupted or missing. (Code 39)" after instaling it.
>
> >> Has anybody know what can be wrong here?
>
> >> Regards,
> >> scout
>
> > Just to confirm that I am using right settings It is WDK 6001 and
> > "Windows Vista and Windows Server 2008 x64 Checked Build Environment".
>
> > Regards,
> > scout.- Hide quoted text -
>
> - Show quoted text -

My environment:

Windows Vista 64, WDK 6000, "Windows Vista and Windows Server Longhorn
x64 Checked Build Environment"

I did the following according to the documentation on selfsigning:

1. Buidl the driver and put it into c:\Driver (.sys and .inf files).
By the way why does the output folder name have amd64 as part of the
name and not just x64?, just wnat to be sure that it is ok for Intel
based 64 systems)
2. Created test certificate: makecert -r -pe -ss TEST c:\ddk.cer
3. Added it to the system: certmgr -add c:\ddk.cer -s -r localMachine
root
certmgr -add c:\ddk.cer -s -r localMachine trustedpublisher
4. Created .cat file: signability /auto /cat /driver:c:\Driver /os:512
5. Signed the .cat and .sys files: signtool sign /s TEST c:\driver
\avshws.cat
signtool sign /s TEST c:\driver\avshws.sys
6. Verified the files: signtool verify /pa /v c:\driver\avshws.cat
signtool verify /pa /v c:\driver\avshws.sys
7. Installed the driver and got Code39 again.

I have tried signing .cat or .sys files only as well with the same
result.

What am I doing wrong here?

Regards,
scout

Anatoly
Thu Oct 18 03:28:12 PDT 2007

Test certificates are not accepted by default. You need to enable test
signing with "bcdedit -set testsigning on"and reboot.

Anatoly

<scout119@gmail.com> wrote in message
news:1192635550.189631.307950@v29g2000prd.googlegroups.com...
> On Oct 17, 5:38 am, "Anatoly Greenblatt" <anatolik_at_email.com>
> wrote:
>> You may get code 39 on 64 if driver is not properly signed. You need
>> either
>> to sign your driver or run with debugger connected.
>>
>> Anatoly.
>>
>> <scout...@gmail.com> wrote in message
>>
>> news:1192572170.325132.150480@z24g2000prh.googlegroups.com...
>>
>>
>>
>> > On Oct 16, 5:28 pm, scout...@gmail.com wrote:
>> >> Hi,
>>
>> >> I have build the sample driver using checked 64 environment.
>>
>> >> I have "Windows cannot load the device driver for this hardware. The
>> >> driver may be corrupted or missing. (Code 39)" after instaling it.
>>
>> >> Has anybody know what can be wrong here?
>>
>> >> Regards,
>> >> scout
>>
>> > Just to confirm that I am using right settings It is WDK 6001 and
>> > "Windows Vista and Windows Server 2008 x64 Checked Build Environment".
>>
>> > Regards,
>> > scout.- Hide quoted text -
>>
>> - Show quoted text -
>
> Hi Anatoly,
>
> I did everything "by the book" as it described in the
> selfsign_readme.html from:
>
> 64 bit Vista, WDK 6000, "Windows Vista and Windows Server Longhorn x64
> Checked Build Environment"
>
> 1. build the code, copied .inf file and .sys to C:\Driver (by the way
> why does the name of the output folder has amd64 and not just x64,
> just want to be sure that it is ok for Intel 64 as well)
> 2. Created test certificate in the build environment window: makecert -
> r -pe -ss TEST c:\ddk.cer
> 3. Added it to the system: certmgr -add c:\ddk.cer -s -r localMachine
> root
> certmgr -add c:\ddk.cer -s -r localMachine trustedpublisher
> 4. Created cat file: signability /auto /cat /driver:c:\Driver /os:512
> 5. Signed cat file: signtool sign /s TEST c:\driver\avshws.cat
> 6. Signed driver file: signtool sign /s TEST c:\driver\avshws.sys
> 7. Verified it: signtool verify /pa /v c:\driver\avshws.cat (did same
> for .sys file as well)
> 8. Installed the driver and got Code 39.
>
> I've tried to sign .cat only and .sys only as well with the same
> result.
>
> What am I doing wrong?
>
> Regards,
> scout
>