ProtocolCloseAdapterComplete

Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

ProtocolCloseAdapterCompleteis a required driver function that completes processing for an unbinding operation for which NdisCloseAdapterreturned NDIS_STATUS_PENDING.

VOID
ProtocolCloseAdapterComplete(
IN NDIS_HANDLE
ProtocolBindingContext, 
IN NDIS_STATUS
Status
);

ProtocolCloseAdapterCompleteis a required driver function that completes processing for an unbinding operation for which NdisCloseAdapterreturned NDIS_STATUS_PENDING.

Parameters

ProtocolBindingContext

Specifies the handle to a protocol-allocated context area in which the protocol driver maintains per-binding runtime state. The driver supplied this handle when it called NdisOpenAdapter.

Status

Indicates the final status of the close operation in the underlying driver.

Comments

NDIS delays calling ProtocolCloseAdapterCompleteuntil every request pending on the binding has completed. When ProtocolCloseAdapterCompleteis called, the NdisBindingHandleoriginally returned by NdisOpenAdapteris no longer valid. ProtocolCloseAdapterCompletecannot call any Ndis XXXfunction that requires this handle as a parameter.

ProtocolCloseAdapterCompletereleases all resources the driver allocated for per-binding network I/O operations before it returns control.

ProtocolCloseAdapterCompletemust call NdisCompleteUnbindAdapterwith the UnbindContexthandle saved in the ProtocolBindingContextarea by ProtocolUnbindAdapter. Consequently, ProtocolCloseAdapterCompleteshould not release the driver-allocated context area until it has called NdisCompleteUnbindAdapter.

Requirements

Runs on	Versions	Defined in	Include	Link to
Windows CE OS	2.0 and later	Ndis.h		Ndislib.lib

Note This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.