Compartir a través de

NDIS_TAPI_SET_APP_SPECIFIC (Compact 2013)

  • Artículo

3/26/2014

OID_TAPI_SET_APP_SPECIFIC uses the NDIS_TAPI_SET_APP_SPECIFIC structure when it requests the miniport driver to set the ulAppSpecific member of the specified call's LINECALLINFO structure.

Support for this request is mandatory.

Syntax

typedef struct _NDIS_TAPI_SET_APP_SPECIFIC { 
  ULONG ulRequestID; 
  HDRV_CALL hdCall; 
  ULONG ulAppSpecific; 
} NDIS_TAPI_SET_APP_SPECIFIC, *PNDIS_TAPI_SET_APP_SPECIFIC;

Members

  • ulRequestID
    [in] Reserved.
  • hdCall
    [in] Specifies the miniport driver's handle to the call for which the application-specific member is to be set.
  • ulAppSpecific
    [in] Specifies the new content of the ulAppSpecific member for the call's LINECALLINFO structure. This value is uninterpreted by the NIC driver. The value is not validated by NDISTAPI when this request is made.

Remarks

The MiniportSetInformation function can return one of the following:

  • NDIS_STATUS_SUCCESS
  • NDIS_STATUS_PENDING
  • NDIS_STATUS_TAPI_INVALCALLHANDLE
  • NDIS_STATUS_TAPI_RESOURCEUNAVAIL
  • NDIS_STATUS_FAILURE

Requirements

Header

ndistapi.h,
ntddndis.h

See Also

Reference

NDIS 5.x Legacy Structures
OID_TAPI_SET_APP_SPECIFIC
MiniportSetInformation