Thank you MAX and …for your info.,
Problems:
I am trying to run the vpacket example from the window98 ddk and example
Trans31 from Numega example drivers. I installed the Protocol driver as
they suggested using their INF files. Load the driver using numega softice
I set the break points at the Xxxbindadapter routine. Plugged the pnp NIC.
It did not break It seemed to me that NDIS did not see my example protocol
driver. What might be the problem?
1, could it be version of NDIS on miniport and protocol driver?
2,???
3,??
please helps.
Thank you
From: “Maxim S. Shatskih”
>Reply-To: “NT Developers Interest List”
>To: “NT Developers Interest List”
>Subject: [ntdev] Re: new member need helps! NDIS PROTOCOL DRIVER
>Date: Sat, 7 Apr 2001 18:23:04 +0400
>
> > #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: 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