WDF 1.0 PCIDRV.sys and NDISEDGE.sys will not load

I built pcidrv.sys and ndisedge.sys with Winddk Longhorn x86 checked
environment, plus set_wdf_env.cmd and kmdf\inc. Then installed them with the
netdrv.inf and wdf**.dll co-installer in vista Beta2.

However, both drivers cannot be loaded and the device manager error code is
#37,
"Windows cannot initialize the device driver for this hardware." No any
event log associated with those failure either.

Can any Microsoft expert duplicate the problem ? or I missed anything during
build or install ?

Thanks for any advice.

-Gary Li

Doron
Tue Mar 07 22:07:10 CST 2006

what do setupact.logand setupapi.log have to say?

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Gary Li" <garyli@verizon.net> wrote in message
news:D0A3D169-27C8-403A-858C-300D17A0D623@microsoft.com...
>I built pcidrv.sys and ndisedge.sys with Winddk Longhorn x86 checked
> environment, plus set_wdf_env.cmd and kmdf\inc. Then installed them with
> the
> netdrv.inf and wdf**.dll co-installer in vista Beta2.
>
> However, both drivers cannot be loaded and the device manager error code
> is
> #37,
> "Windows cannot initialize the device driver for this hardware." No any
> event log associated with those failure either.
>
> Can any Microsoft expert duplicate the problem ? or I missed anything
> during
> build or install ?
>
> Thanks for any advice.
>
> -Gary Li

garyli
Wed Mar 08 12:20:27 CST 2006

I cannot see any problem by looking at those log files.
The ramdisk sample in DDK cannot be loaded either.

I suspect something wrong in my build environment.
But no clue where.
I am using Vista DDK, selected WLH checked build environment.
Then, run set_wdf_env.cmd in KMDF (also set inc cover KMDF\inc).

Is this right environment to build WDF sample drivers ?

-Gary

"Doron Holan [MS]" wrote:

> what do setupact.logand setupapi.log have to say?
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Gary Li" <garyli@verizon.net> wrote in message
> news:D0A3D169-27C8-403A-858C-300D17A0D623@microsoft.com...
> >I built pcidrv.sys and ndisedge.sys with Winddk Longhorn x86 checked
> > environment, plus set_wdf_env.cmd and kmdf\inc. Then installed them with
> > the
> > netdrv.inf and wdf**.dll co-installer in vista Beta2.
> >
> > However, both drivers cannot be loaded and the device manager error code
> > is
> > #37,
> > "Windows cannot initialize the device driver for this hardware." No any
> > event log associated with those failure either.
> >
> > Can any Microsoft expert duplicate the problem ? or I missed anything
> > during
> > build or install ?
> >
> > Thanks for any advice.
> >
> > -Gary Li
>
>
>

Eliyas
Wed Mar 08 13:06:08 CST 2006

You should use Server Sp1 DDK to build KMDF 1.0. You should not use vista
WDK. Vista DDK headers do not match with KMDF 1.0 libraries. The version
of framework that's part of vista DDK is only compatible with inbox Vista
runtime - which is currently marked version 1.5.

--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/driver/kernel/KB-drv.mspx

garyli
Thu Mar 09 02:51:28 CST 2006

When I used WS2003 DDK SP1 to build the WDF drivers, it works.
Thanks

-Gary

"Eliyas Yakub [MSFT]" wrote:

> You should use Server Sp1 DDK to build KMDF 1.0. You should not use vista
> WDK. Vista DDK headers do not match with KMDF 1.0 libraries. The version
> of framework that's part of vista DDK is only compatible with inbox Vista
> runtime - which is currently marked version 1.5.
>
> --
> -Eliyas
> This posting is provided "AS IS" with no warranties, and confers no rights.
> http://www.microsoft.com/whdc/driver/kernel/KB-drv.mspx
>
>
>

garyli
Fri Mar 10 01:09:26 CST 2006

Sorry for the confusion.

Under this topic, I actually reported a general build issue for all WDF
sample drivers. I built them with wrong DDK (WDK for Vista), which resulted
in the device manager error #37 for all WDF drivers. The build problem was
fixed by using WS 2003 DDK SP1. Thanks for your reminding.

The ndisedge.sys unloading issue still exists, and I reported it in a
separate trace.

Thanks

-Gary

"Gary Li" wrote:

> When I used WS2003 DDK SP1 to build the WDF drivers, it works.
> Thanks
>
> -Gary
>
> "Eliyas Yakub [MSFT]" wrote:
>
> > You should use Server Sp1 DDK to build KMDF 1.0. You should not use vista
> > WDK. Vista DDK headers do not match with KMDF 1.0 libraries. The version
> > of framework that's part of vista DDK is only compatible with inbox Vista
> > runtime - which is currently marked version 1.5.
> >
> > --
> > -Eliyas
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > http://www.microsoft.com/whdc/driver/kernel/KB-drv.mspx
> >
> >
> >