The primary reason that NdisGetReceivedPacket would return NULL would be
that the lower-level miniport used a non-packet method for indicating
received packets.
For example, if the lower-level miniport called NdisMEthIndicateReceive,
then NdisGetReceivedPacket should return NULL in the higher-level protocol’s
ReceiveHandler.
You must design your receive handler in such a way that it does not depend
on NdisGetReceivedPacket returning a pointer to a packet descriptor.
Regards,
Thomas F. Divine
PCAUSA - Toolkits & Resources For Network Software Developers
NDIS Protocol - NDIS Intermediate - TDI Client
http: - http:
----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Friday, August 03, 2001 5:38 AM
Subject: [ntdev] Re: Padding in itermediate driver
> Hi,
> Thank you thomas that was very much helpfull.
> I have one more question regarding NdisGetReceivedPacket().I want to know
> under what conditions this function returns NULL ,DDK does not specify
> regarding this condition.
> Thanks/Regards,
> Shashi
—
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</http:></http:>