new member need helps! NDIS PROTOCOL DRIVER

NTDEV
1

I am writing a NDIS protocol driver for Win9x.( there is a miniport driver
underlying the protocol driver)

Questions:

#1,How does NDIS know to call my protocol driver to bind to the underlying
Adapter? what are the steps? I did some research and here what I have so
far.

a. First I have to install my protocol driver using the .inf file -> NDIS
will call my protocol driver with a adapterName then I can use the
Adaptername pass in by the NDis to open and bind to the NiC. I am still
little bit confuse. How does the NDIS know to call my protocol driver and
pass in the correct adaptername for to me to open and bind to the it? what
happen if my Miniport driver supports multiple NIc adapters?

Thank you,

Cheers,

Get your FREE download of MSN Explorer at http://explorer.msn.com

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

When the users adds a protocol then the protocol is added and bound by
default for all the NIC adapters.

Ramit.
----- Original Message -----
From: “Ken Nguyen”
To: “NT Developers Interest List”
Sent: Saturday, April 07, 2001 1:18 PM
Subject: [ntdev] new member need helps! NDIS PROTOCOL DRIVER

> I am writing a NDIS protocol driver for Win9x.( there is a miniport driver
> underlying the protocol driver)
>
> Questions:
>
> #1,How does NDIS know to call my protocol driver to bind to the underlying
> Adapter? what are the steps? I did some research and here what I have so
> far.
>
> a. First I have to install my protocol driver using the .inf file -> NDIS
> will call my protocol driver with a adapterName then I can use the
> Adaptername pass in by the NDis to open and bind to the NiC. I am still
> little bit confuse. How does the NDIS know to call my protocol driver and
> pass in the correct adaptername for to me to open and bind to the it?
what
> happen if my Miniport driver supports multiple NIc adapters?
>
> Thank you,
>
> Cheers,
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@wipro.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
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

> #1,How does NDIS know to call my protocol driver to bind to the underlying

Adapter? what are the steps? I did some research and here what I have so
far.

This is for NDIS>=4 protocols.
NDIS will call your BindAdapterHandler according to the information in the
binding registry.
This registry is written by NCPA when you install your protocol.
You must have a correct INF for the protocol for this - see the PACKET’s
INF.

Another way (NDIS3) - is to call NdisOpenAdapter explicitly after
NdisRegisterProtocol. In this case, you can pick the adapter name from any
source you want - including the private registry of your own.
Installation via NCPA is not necessary for such protocols.

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