Re: NDIS 6 miniport - MiniportInitialize is not called
- From: "Calvin Guan" <hguan@xxxxxxxxxxxxxxxxxxx>
- Date: Sun, 3 Dec 2006 16:06:34 -0800
Did you run check inf against your inf file?
there are couple of reasons off my head why miniportinitEx wouldn't get
call:
1) make sure you have include 3 newly introduced keys in your DD.install
section. Ndis!AddDevice will fail if they are missing or misspelled.
2) registry corrupted.
3) resource allocation failure (not likely applicable to your case since
yours is a vmp)
4) other pnp failures occurred between addDev and Irp_mn_start_dev inside
ndis(could be miniport's fault).
--
Calvin Guan (DDK MVP)
Sr. Staff Engineer
NetXtreme Vista/LH Server Miniport
Broadcom Corporation
Connecting Everything(r)
"miki" <michael.waksman@xxxxxxxxx> wrote in message
news:1165164946.142976.276430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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:
- References:
- Prev by Date: Re: device class of tdi filter and tdi client
- Next by Date: Re: device class of tdi filter and tdi client
- Previous by thread: NDIS 6 miniport - MiniportInitialize is not called
- Next by thread: Re: NDIS 6 miniport - MiniportInitialize is not called
- Index(es):
Relevant Pages
|
