NdisCompleteUnbindAdapter
TOC
Collapse the table of content
Expand the table of content

NdisCompleteUnbindAdapter function

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.

NdisCompleteUnbindAdapter completes an unbinding operation for which the caller's ProtocolUnbindAdapter function previously returned NDIS_STATUS_PENDING.

Syntax


VOID NdisCompleteUnbindAdapter(
  _In_ NDIS_HANDLE UnbindAdapterContext,
  _In_ NDIS_STATUS Status
);

Parameters

UnbindAdapterContext [in]

Specifies the UnbindContext handle passed in to ProtocolUnbindAdapter.

Status [in]

Specifies the Status of the completed unbind operation, always NDIS_STATUS_SUCCESS.

Return value

None

Remarks

When a protocol returns NDIS_STATUS_PENDING from its ProtocolUnbindAdapter function, that driver must eventually call NdisCompleteUnbindAdapter when the unbinding operation is completed.

When NdisCompleteUnbindAdapter is called, the protocol has finished cleaning up any state the driver maintains about the binding and released any resources it allocated to establish the binding. This call notifies the NDIS library of the completion of the unbinding operation that this driver initiated when it called NdisOpenAdapter from ProtocolBindAdapter.

On return from NdisCompleteUnbindAdapter the UnbindAdapterContext handle should be considered invalid. That is, the protocol should not pass this handle in calls to any NdisXxx function.

Requirements

Target platform

Universal

Version

Not supported for NDIS 6.0 drivers in Windows Vista. Use NdisCompleteUnbindAdapterExinstead. Supported for NDIS 5.1 drivers in Windows Vista and Windows XP.

Header

Ndis.h (include Ndis.h)

Library

Ndis.lib

IRQL

PASSIVE_LEVEL.

See also

MiniportHalt
NdisCloseAdapter
NdisIMDeInitializeDeviceInstance
ProtocolBindAdapter
ProtocolUnbindAdapter

 

 

Send comments about this topic to Microsoft

Show:
© 2016 Microsoft