This documentation is archived and is not being maintained.

NdisMArcIndicateReceiveComplete function

Note   NDIS 5. x has been deprecated and is superseded by NDIS 6. x. For new NDIS driver development, see Network Drivers Starting with Windows Vista. For information about porting NDIS 5. x drivers to NDIS 6. x, see Porting NDIS 5.x Drivers to NDIS 6.0.

NdisMArcIndicateReceiveComplete notifies NDIS that an ARCNET packet, identified in a preceding call to NdisMArcIndicateReceive, has been fully transferred by the NIC so that NDIS can notify the appropriate bound protocols.


VOID NdisMArcIndicateReceiveComplete(
  _In_ NDIS_HANDLE MiniportAdapterHandle


MiniportAdapterHandle [in]

Specifies the handle originally input to MiniportInitialize.

Return value



After any ARCNET receive indication, a serialized miniport driver eventually must call NdisMArcIndicateReceiveComplete to indicate the end of the transfer operation over the net, even if a particular packet is accepted by no bound protocol.

NdisMArcIndicateReceiveComplete both indicates the completion of a transfer operation for a receive and notifies any bound protocol that has already consumed the initial indication that it can begin postprocessing the received data.

When a miniport driver calls NdisMArcIndicateReceiveComplete, NDIS indicates the completion of the receive operation to each such protocol by calling its ProtocolReceiveComplete function.

ProtocolReceiveComplete functions need not operate under the severe time constraints of the corresponding ProtocolReceive functions. However, another receive indication to the ProtocolReceive function can come in while the ProtocolReceiveComplete function is running.

A miniport driver need not call NdisMArcIndicateReceiveComplete in one-to-one correspondence with its calls to NdisMArcIndicateReceive. That is, a NIC driver can issue a single receive-complete indication for some number of receive indications, particularly when network traffic is high. For example, when a NIC driver is continually indicating receives from the same source, it might call NdisMArcIndicateReceiveComplete once for every ten indications. On the other hand, a miniport driver might call NdisMArcIndicateReceiveComplete once for each indication when network traffic is low so that the driver can regain ownership of the memory it allocated for receives promptly. However, a miniport driver must call NdisMArcIndicateReceiveComplete at least once per batch of packets indicated from its MiniportHandleInterrupt function.

Note that only serialized miniport drivers should call NdisMArcIndicateReceiveComplete.


Target platform



Not supported in Windows Vista.


Ndis.h (include Ndis.h)



See also




Send comments about this topic to Microsoft