BindAdapterHandler for WDM/ NDIS protocol driver not called

Q

QuasiCodo

On XP, I have a WDM driver which uses the PnP mechanism to load. Once
loaded, I called NdisRegisterProtocol to register the protocol portion of
the driver with NDIS. The problem I am having is the my
BindAdapterHandler() is not being called. The PnpEventHandler() is being
called with NetPnpEvent->NetEvent set to NetEventBindsComplete (i.e. NDIS
tells me that all bindings for this protocol have been performed).

A BindsComplete indication without any BindAdapterHandler() callbacks is
what I would expect if I had not installed the protocol in the system.
However, I have a separate INF file in which I install the protocol.
BindView shows this that my protocol is installed and bound to the NIC card.

The only thing I can think of is that protocol identifier in the INF file
does not match the protocol name I gave to NdisRegisterProtocol().

Any ideas?

((&-<
 
Q

QuasiCodo

Changing the protocol name in the NdisRegisterProtocol to the service name
in the registry worked.
 
Q

QuasiCodo

Changing the protocol name in the NdisRegisterProtocol to the service name
in the registry worked.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

ndislwf (NDIS 6.0 Sample Filter Driver) to monitor native wifi adapter 0
NDIS protocol driver (WinXP DDK 2600.1109) 4
How to export functions from Ndis miniport driver for a smart carddriver to use ? 2
What is GTNDIS5 NDIS Protocol Driver? 6
Opening COM port from NDIS driver 0
protocolBindAdapter Problem in embedded XP 1
Problem with Power Management in NDIS driver 3
PCAMPR5 NDIS protocol driver problem 2

Top