Protocl Driver and NdisWAN

NTDEV
1

Hi!
I need to modify the MS-supplied protocol driver sample to make it bind to
NDISWAN. Is this at all possible, and if so, what changes would I need to
make to the code. I suppose I’d also need to change the INF file, right?

Any commants/suggestions…

TIA
Siddharth Karnik

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

Hello ,

scc> I need to modify the MS-supplied protocol driver sample to make it bind to
scc> NDISWAN. Is this at all possible, and if so, what changes would I need to
scc> make to the code. I suppose I’d also need to change the INF file, right?

some things are importand, your medium array must contain the rigth
medium value (NdisMediumWan) for NdisOpenAdapter and your
characteristic table for NdisRegisterProtocol must set
the
WanSendCompleteHandler,
WanTransferDataCompleteHandler and
WanReceiveHandler.

elli

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

> ----------

From: Mathias Ellinger[SMTP:xxxxx@ellisoft.de]
Reply To: NT Developers Interest List
Sent: Sunday, January 28, 2001 6:38 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Protocl Driver and NdisWAN

Hello ,

scc> I need to modify the MS-supplied protocol driver sample to make it
bind to
scc> NDISWAN. Is this at all possible, and if so, what changes would I
need to
scc> make to the code. I suppose I’d also need to change the INF file,
right?

some things are importand, your medium array must contain the rigth
medium value (NdisMediumWan) for NdisOpenAdapter and your

This is right and necessary thing.

characteristic table for NdisRegisterProtocol must set
the
WanSendCompleteHandler,
WanTransferDataCompleteHandler and
WanReceiveHandler.

I’m sorry but this isn’t correct. A protocol bound to NdisWan uses standard
protocol handlers and any other protocol, there is no difference. WAN
handlers in protocol characteristics uses IMHO NdisWan itself when registers
as a protocol bound to WAN miniports and IM drivers between WAN miniports
and NdisWan.

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

4

Hello ,

VM> I’m sorry but this isn’t correct. A protocol bound to NdisWan uses standard
VM> protocol handlers and any other protocol, there is no difference. WAN
VM> handlers in protocol characteristics uses IMHO NdisWan itself when registers
VM> as a protocol bound to WAN miniports and IM drivers between WAN miniports
VM> and NdisWan.

Ok that is rigth, I have defined this handlers in my driver, but this
are only stubs and I use only NdisRequest for communication.

elli

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