Notify Object , Driver Signing & Protocol Driver

NTDEV
1

We recently upgraded from a NDIS 3.0 protocol driver to NDIS 5.0 protocol
driver. In the earlier case we used to bind the protocol driver to the
underling NIC by calling an IOCTL from an application. IOCTL used to make
call to NDISOpenAdapter.

Now with NDIS 5.0, the BindAdapterHandler calls NDISOpenAdapter (). I plan
to use a notify object to let the NIC driver know about the binding with
Protocol driver. NIC driver is owned by someone else. Is there any other
option other than using a Notify object to make the BindAdapterHandler ()
call happen?

Q2: If I do not want Microsoft to bundle my driver with the Window
Installation, do I have to go for driver signing?

Thanks,
Nitin

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

> Protocol driver. NIC driver is owned by someone else. Is there any other

option other than using a Notify object to make the BindAdapterHandler ()
call happen?

You mix 2 different entities. Notify objects are installation user mode DLLs executed by the network control panel. Their purpose
is to create the registry structure for NDIS.

ProtocolBindAdapter is called by NDIS.SYS after NdisRegisterProtocol. NDIS.SYS parses the registry created by the notify objects and
network control panel to call ProtocolBindAdapter.
NdisOpenAdapter must be called from ProtocolBindAdapter and use the same name as NDIS.SYS passed to ProtocolBindAdapter.

Max

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Thanks.
Sorry for not being clear earlier.

Right. NDIS.sys shall call the ProtocolBindAdapter () after Notify creates
an entry in the registry. What I wanted to ask is - Is using Notify object
the only way of making NDIS.sys know that it has to call my
ProtocolBindAdapter handler? I do not have any control over NIC’s inf. Is
there any other option.

Nitin

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com