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.
NdisMIndicateStatusComplete notifies NDIS (or NDISWAN) that the NIC driver, which has called NdisMIndicateStatus one or more times to indicate hardware anomalies or run-time state changes in the NIC, is ready to resume normal device I/O operations.
- MiniportAdapterHandle [in]
Specifies the handle originally input to MiniportInitialize.
When a miniport driver calls NdisMIndicateStatusComplete, NDIS calls the ProtocolStatusComplete function(s) of bound protocol(s) that were previously notified of the immediately preceding state change(s) in the underlying NIC with calls to their ProtocolStatus functions.
A miniport driver eventually must call NdisMIndicateStatusComplete after it calls NdisMIndicateStatus. However, a miniport driver need not deliver NdisMIndicateStatusComplete indications in one-to-one correspondence with its NdisMIndicateStatus indications. It can choose to issue a single status-complete indication for several status indications that have occurred, particularly when network traffic is high.
A protocol driver writer should assume that interrupts are enabled on the NIC while the ProtocolStatusComplete function is running. A protocol driver writer also should assume that the ProtocolStatus function is reentrant while the ProtocolStatusComplete function is running, particularly on an SMP platform.
A miniport driver must release any spin lock that it is holding before calling NdisMIndicateStatusComplete.
Serialized callers of NdisMIndicateStatusComplete must run at IRQL = DISPATCH_LEVEL. Deserialized callers of NdisMIndicateStatusComplete must run at IRQL <= DISPATCH_LEVEL.
|Not supported for NDIS 6.0 drivers in Windows Vista. Use NdisMIndicateStatusExinstead. Supported for NDIS 5.1 drivers in Windows Vista and Windows XP.|
|See Remarks section|