Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
NdisCmDeregisterSapComplete returns the final status of a client's request, for which the call manager previously returned NDIS_STATUS_PENDING, to deregister a SAP.
Syntax
VOID NdisCmDeregisterSapComplete(
[in] NDIS_STATUS Status,
[in] NDIS_HANDLE NdisSapHandle
);
Parameters
[in] Status
Specifies NDIS_STATUS_SUCCESS.
[in] NdisSapHandle
Specifies the handle identifying the SAP.
Return value
None
Remarks
NdisCmDeregisterSapComplete notifies both NDIS and the client that the call manager has completed the SAP-deregistration request for which its ProtocolCmDeregisterSap function previously returned NDIS_STATUS_PENDING.
A call to NdisCmDeregisterSapComplete causes NDIS to call the client's ProtocolClDeregisterSapComplete function.
The call manager should consider the NdisSapHandle invalid when NdisCmDeregisterSapComplete returns control.
Only stand-alone call managers, which register themselves with NDIS as protocol drivers, can call NdisCmDeregisterSapComplete. Connection-oriented miniport drivers that provide integrated call-management support call NdisMCmDeregisterSapComplete instead.
Requirements
| Requirement | Value |
|---|---|
| Minimum supported client | Supported for NDIS 6.0 and NDIS 5.1 drivers (see NdisCmDeregisterSapComplete (NDIS 5.1)) in Windows Vista. Supported for NDIS 5.1 drivers (see NdisCmDeregisterSapComplete (NDIS 5.1)) in Windows XP. |
| Target Platform | Desktop |
| Header | ndis.h (include Ndis.h) |
| Library | Ndis.lib |
| IRQL | <= DISPATCH_LEVEL |
| DDI compliance rules | Irql_CallManager_Function(ndis) |