Re: Protocol binding !!! helps

Hi Max,

I am writing NDIS 3.1. How do i know the adapter name? by looking at the
INf file? Please give me some clues. If I know the adapter name can I
enter it directly into the NdisOpenadapter() or I need to read it from the
registry?

Thanks

ken

From: “Maxim S. Shatskih”
>Reply-To: “NT Developers Interest List”
>To: “NT Developers Interest List”
>Subject: [ntdev] Re: Protocol binding !!! helps
>Date: Sat, 21 Apr 2001 00:34:28 +0400
>
> > Instead of formal way of binding to the beneath NIC adapter.
> >
> > Can I bind to the Miniport driver instead using the miniport driver’s
>name?
> > If yes please show me how.
>
>Binding is performed by calling NdisOpenAdapter in your protocol.
>You must know the adapter name to do this.
>
>The modern way of determining it (which will also give you the ability of
>being notified on adapter arrival and removal) is installing your binary as
>an NDIS protocol (via NCPA) and relying on ProtocolBindAdapter callback.
>NDIS will provide you the adapter name there for your NdisOpenAdapter call.
>You will also see ProtocolUnbindAdapter callback when the adapter is
>disappearing (due to PnP removal or “net stop NICDriver”).
>
>You can also read the adapter name from the NDIS registry by your code
>(this
>is an old NDIS3 way) or to read it from some store of your own.
>
>In the latter case, you will not receive notifications on NIC
>arrival/removal, but you will be able of forgetting about registering your
>driver with NCPA as a protocol driver. Any kernel-mode module (not
>necessary
>installed as a protocol) will be able to call NdisOpenAdapter using this
>technique.
>
> Max
>
>
>—
>You are currently subscribed to ntdev as: xxxxx@hotmail.com
>To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

_________________________________________________________________
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

> ----------

From: Ken Nguyen[SMTP:xxxxx@hotmail.com]
Reply To: NT Developers Interest List
Sent: Saturday, April 21, 2001 1:40 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Protocol binding !!! helps

I am writing NDIS 3.1. How do i know the adapter name?

NDIS 3.1 supports ProtocolBindAdapter callback and it is the best way how to
get adapter name for open.

by looking at the
INf file? Please give me some clues. If I know the adapter name can I
enter it directly into the NdisOpenadapter() or I need to read it from the

registry?

If you know it why to read it again from the registry? :slight_smile:

Best regards,

Michal Vodicka
Veridicom
(RKK - Skytale)
[WWW: http://www.veridicom.com , http://www.skytale.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

> Hi Max,

I am writing NDIS 3.1. How do i know the adapter name? by looking at the
INf file?

By parsing the NDIS registry, look in PACKET sample code.

BTW - it is much simpler to use NDIS4 and rely on ProtocolBindAdapter - you
will be free from the need of parsing the registry data.

f I know the adapter name can I
enter it directly into the NdisOpenadapter() or I need to read it from the
registry?

Yes.

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