NdisCoDeleteVc destroys a caller-created VC.
NDIS_STATUS NdisCoDeleteVc( NDIS_HANDLE NdisVcHandle );
Specifies the handle identifying the VC to be deleted. The caller originally obtained this handle from NdisCoCreateVc.
NdisCoDeleteVc can return one of the following:
||NDIS deleted the VC.|
||The VC is still active, so it could not be deleted.|
||This call is redundant, but deactivation on the given VC is still pending.|
When a protocol calls NdisCoDeleteVc, there must be no outstanding calls on the given VC and that VC already has been deactivated. To meet these requirements implies that the following conditions hold:
- If the call tear-down was initiated by a local client, that client has already called NdisClCloseCall with the given NdisVcHandle and its close-call request has completed successfully.
- If the call tear-down was initiated by a remote client, the stand-alone call manager has already called NdisCmDeactivateVc with the given NdisVcHandle and its deactivation request has completed successfully.
When NdisCoDeleteVc returns control, the NdisVcHandle is no longer valid.
Stand-alone call managers, which register themselves with NDIS as protocol drivers, can call NdisCoDeleteVc. Connection-oriented miniport drivers that provide integrated call-management support call NdisMCmDeleteVc instead.
|Minimum supported client||Supported for NDIS 6.0 and NDIS 5.1 drivers (see NdisCoDeleteVc (NDIS 5.1)) in Windows Vista. Supported for NDIS 5.1 drivers (see NdisCoDeleteVc (NDIS 5.1)) in Windows XP.|
|Header||ndis.h (include Ndis.h)|
|DDI compliance rules||Irql_Connection_Function|