Hello there,
quick question about a anomaly that I have noticed.
I’ve got a working filter-hook driver that intercepts
NdisMRegisterMiniport(), NdisRegisterProtocol() and then does all the
bookkeeping for NdisOpenAdapter() etc. Everything works fine except
this one weird thing:
– the structure passed to MyNdisRegisterProtocol() by “NdisWan” is a
bit bigger than what the header defines. So, I’ve had to use some
padding 
NDIS30_PROTOCOL_CHARACTERISTICS=56
NDIS40_PROTOCOL_CHARACTERISTICS=76
NDIS50_PROTOCOL_CHARACTERISTICS=108
uiIndicatedVersion=5.0
uiCharacteristicsLength=122
– at the same time all other protocols that are registered during the
startup use decent lengths…
So, has anybody else noticed this?
Thanks in advance,
Oleg Smolsky
Software Design Authority
Allied Telesyn Research