NDIS 6 miniport - MiniportInitialize is not called
- From: "miki" <michael.waksman@xxxxxxxxx>
- Date: 3 Dec 2006 08:55:46 -0800
Hi,
I am trying to write an ndis 6 miniport virtual driver (I am not strong
in names so meanwhile I called him netvmini)
On the device manager I get the message:
"This device is not working properly because Windows cannot load the
drivers required for this device. (Code 31)"
When using WinDbg I see that my driverentry is called and return
SUCCESS.
but my MiniportInitializeEx is not called instead the DriverUnload is
called.
on setupapi.dev file I get:
cmd: c:\tools\devcon.exe install netvmini.inf root\netvmini[Device Install (UpdateDriverForPlugAndPlayDevices) - root\netvmini]
Section start 2006/12/03 17:22:06.296
!!! sto: Inf file does not contain CatalogFile directive for the
specified processor architecture. Inf = c:\ndis6\netvmini.inf
! sto: The Driver Package does not contain a catalog file, but user
wants to install anyway.
! sig: No installed catalogs matching catalog name '' were found
that validated the file.
! sig: Error 1168: Element not found.
! sig: No installed catalogs matching catalog name '' were found
that validated the file.
! sig: Error 1168: Element not found.
! dvi: Device restart was skipped becasuse the DI_DONOTCALLCONFIGMG
flag was set.
!!! dvi: Device not started: Device has problem: 0x1f:
CM_PROB_FAILED_ADD.
! sig: No installed catalogs matching catalog name '' were found
that validated the file.
! sig: Error 1168: Element not found.
! ndv: Queueing up error report since device has a PnP problem...
! dvi: Driver list already built
<<< Section end 2006/12/03 17:23:19.139
<<< [Exit status: SUCCESS]
(I don't understand why the Exit status is SUCCESS)
As I understand since I am not running vista x64 I don't have to sign
the driver on the development phase so I ignore the !sig warnings.
I tried to use my own written INF file and also the INF file of
netvmini from WDK samples (NDIS 5 driver) for loading the driver both
resulted with the same error code - 31
What can be the reason that MiniportInitializeEx is not called even
though DriverEntry succeeded?
Thanks
Miki
.
- Follow-Ups:
- Re: NDIS 6 miniport - MiniportInitialize is not called
- From: Calvin Guan
- Re: NDIS 6 miniport - MiniportInitialize is not called
- Prev by Date: Re: WDF Dynamic Bus Driver New Child Installs Twice
- Next by Date: Inquiring events already registered to TDI
- Previous by thread: Re: WDF Dynamic Bus Driver New Child Installs Twice
- Next by thread: Re: NDIS 6 miniport - MiniportInitialize is not called
- Index(es):
Relevant Pages
|
Loading