|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.|
This function releases the binding established and the resources allocated when the protocol called the NdisOpenAdapterfunction.
VOID NdisCloseAdapter( OUT PNDIS_STATUS Status, IN NDIS_HANDLE NdisBindingHandle );
|NDIS_STATUS_SUCCESS||The binding is closed, and all resources pertaining to that binding have been released.|
|NDIS_STATUS_PENDING||A close-adapter request is being handled asynchronously, and the caller's ProtocolCloseAdapterCompletefunction will be called when the close operation is done.|
The Windows CE version of NdisDeregisterProtocolfrees resources associated with the protocol. It does not close any outstanding bindings or call any adapter-specific ProtocolCloseAdapterCompleteor ProtocolStatusfunctions. Unlike the Windows NT version, it does not unload the miniport driver when there are no more protocol drivers, also known as protocol stacks, bound to it.
As soon as a protocol calls this function, the handle at NdisBindingHandleshould be considered invalid by the caller.
A driver that calls this function runs at IRQL PASSIVE_LEVEL.
|Runs on||Versions||Defined in||Include||Link to|
|Windows CE OS||2.0 and later||Ndis.h|
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.
Last updated on Tuesday, July 13, 2004