NDIS_TAPI_CONFIG_DIALOG (Compact 2013)

3/26/2014

The NDIS_TAPI_CONFIG_DIALOG structure is used with the OID_TAPI_CONFIG_DIALOG to retrieve the name of a user-mode dynamic link library that can be called to configure the specified device.

Support for this request is optional. This request is not made by RAS.

The NDIS_TAPI_CONFIG_DIALOG structure is defined as follows.

Syntax

typedef struct _NDIS_TAPI_CONFIG_DIALOG { 
  ULONG ulRequestID; 
  ULONG ulDeviceID; 
  ULONG ulDeviceClassSize; 
  ULONG ulDeviceClassOffset; 
  ULONG ulLibraryNameTotalSize; 
  ULONG ulLibraryNameNeededSize; 
  CHAR szLibraryName[1]; 
} NDIS_TAPI_CONFIG_DIALOG, *PNDIS_TAPI_CONFIG_DIALOG; 

Members

• ulRequestID
  [in] Reserved.

• ulDeviceID
  [in] Specifies the line device to be configured. This was set up in a preceding OID_TAPI_PROVIDER_INITIALIZE request.

• ulDeviceClassSize
  [in] Specifies the size in bytes of the device-class string.

• ulDeviceClassOffset
  [in] Specifies the offset in bytes to the zero-terminated, variable-size counted string specifying the class of the device whose configuration is requested. Valid device class strings are the same as those specified for the OID_TAPI_GET_ID request when it is applied to a line device (ulSelect has the value LINECALLSELECT_LINE).

• ulLibraryNameTotalSize
  [in] Specifies the size in bytes of the szLibraryName member.

• ulLibraryNameNeededSize
  [out] Specifies the size in bytes that is needed to hold all the returned information.

• szLibraryName
  [out] Specifies space for a zero-terminated string naming a configuration DLL for the requested device. Names not containing a complete path or an extension will be subject to the rules used by the Win32 LoadLibrary function for determining default paths and extensions. If the miniport driver determines this buffer is too small to hold all the information, it should specify the necessary size in the ulLibraryNameNeededSize member and return an NDIS_STATUS_TAPI_STRUCTURETOOSMALL error.

Remarks

The MiniportQueryInformation function can return one of the following:

• NDIS_STATUS_SUCCESS
• NDIS_STATUS_PENDING
• NDIS_STATUS_TAPI_STRUCTURETOOSMALL
• NDIS_STATUS_TAPI_INVALDEVICECLASS
• NDIS_STATUS_TAPI_OPERATIONUNAVAIL
• NDIS_STATUS_TAPI_RESOURCEUNAVAIL
• NDIS_STATUS_FAILURE

Requirements

Header

ndistapi.h, ntddndis.h

See Also

Reference

NDIS 5.x Legacy Structures
OID_TAPI_CONFIG_DIALOG
OID_TAPI_GET_ID
MiniportQueryInformation
OID_TAPI_PROVIDER_INITIALIZE