network driver

NTDEV
1

Hello everyone !
I’m writting network driver for win95.
I have the following question :
What should be done for dispatch functions from
ProtocolCharacteristics could be executed ?

My DriverEntry includes definition of ProtocolCharacteristics and then
I register them by NdisRegisterProtocol.
I thought this would be enough for execution of dispatch routines …
but this is not … :frowning:
What should I add ?

Best regards,
jenson mailto:xxxxx@beep.ru

2

Your protocol functions will not be called automatically until you install
your NDIS protocol driver.

I believe that the DDK includes a sample NDIS protocol driver and its
companion .INF file.

Once properly installed NDIS will begin calling your functions. Te first
that you will probably see is a call to your BindAdapterHandler.

Good luck,

Thomas F. Divine

PCAUSA - Toolkits & Resources For Network Software Developers
NDIS Protocol - TDI Client - Windows 95 Redirector
http:

----- Original Message -----
From: jenson
To: NT Developers Interest List
Sent: Friday, October 27, 2000 12:26 PM
Subject: [ntdev] network driver

> Hello everyone !
> I’m writting network driver for win95.
> I have the following question :
> What should be done for dispatch functions from
> ProtocolCharacteristics could be executed ?
>
> My DriverEntry includes definition of ProtocolCharacteristics and then
> I register them by NdisRegisterProtocol.
> I thought this would be enough for execution of dispatch routines …
> but this is not … :frowning:
> What should I add ?
>
> Best regards,
> jenson mailto:xxxxx@beep.ru
>
></http:>

3

Well, there is vpacket.vxd sample …
but it crushes, when my test application tries to communicate with it.

By the way… was does “installation” mean ?
I guess only the loading order. or not ?
Why should it not work if I load driver by myself ?

TFD> Your protocol functions will not be called automatically until you install
TFD> your NDIS protocol driver.

TFD> I believe that the DDK includes a sample NDIS protocol driver and its
TFD> companion .INF file.

TFD> Once properly installed NDIS will begin calling your functions. Te first
TFD> that you will probably see is a call to your BindAdapterHandler.

Best regards,
jenson mailto:xxxxx@beep.ru

4

Hi, Thomas, et al.,

Suppose I install my NDISWAN miniport driver into system. How can I tell
system to use this driver instead of others when RAS call NDISWAN.sys to
establish a remote connection? Thanks,

Best regards,

Henry

On 10/27/00, ““Thomas F. Divine” ” wrote:
> Your protocol functions will not be called automatically until you install
> your NDIS protocol driver.
>
> I believe that the DDK includes a sample NDIS protocol driver and its
> companion .INF file.
>
> Once properly installed NDIS will begin calling your functions. Te first
> that you will probably see is a call to your BindAdapterHandler.
>
> Good luck,
>
> Thomas F. Divine
>
> PCAUSA - Toolkits & Resources For Network Software Developers
> NDIS Protocol - TDI Client - Windows 95 Redirector
> http:
>
> ----- Original Message -----
> From: jenson
> To: NT Developers Interest List
> Sent: Friday, October 27, 2000 12:26 PM
> Subject: [ntdev] network driver
>
>
> > Hello everyone !
> > I’m writting network driver for win95.
> > I have the following question :
> > What should be done for dispatch functions from
> > ProtocolCharacteristics could be executed ?
> >
> > My DriverEntry includes definition of ProtocolCharacteristics and then
> > I register them by NdisRegisterProtocol.
> > I thought this would be enough for execution of dispatch routines …
> > but this is not … :frowning:
> > What should I add ?
> >
> > Best regards,
> > jenson mailto:xxxxx@beep.ru
> >
> ></http:>