CARD_DATA_PARMS (Windows CE 3.0 Device Driver Developement)

Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

This structure contains tuple information passed to the CardGetTupleDatafunction.

typedef struct {
CARD_SOCKET_HANDLE
hSocket;
UINT16
fAttributes; 
UINT8
uDesiredTuple; 
UINT8
uTupleOffset; 
UINT16
fFlags; 
UINT32
uLinkOffset; 
UINT32
uCISOffset; 
UINT16
uBufLen; 
UINT16
uDataLen; 
} CARD_DATA_PARMS, *PCARD_DATA_PARMS;

Members

hSocket

Handle to a socket and function pair.

fAttributes

[IN] Specify TUPLE_RETURN_LINKS to return link tuples. The first bit is 1.

uDesiredTuple

[IN] Specifies the desired tuple code. If it is 0xFF, the first tuple encountered is returned.

uTupleOffset

[IN] Specifies an offset into tuple data.

fFlags

[IN/OUT] Specifies flags used internally by Card Services. A driver must maintain this value between calls to tuple functions.

uLinkOffset

[IN/OUT] Specifies a tuple link offset used internally by Card Services. A driver must maintain this value between calls to tuple functions.

uCISOffset

[IN/OUT] Specifies card information structure (CIS) state information used internally by Card Services. A driver must maintain this value between calls to tuple functions.

uBufLen

[IN] Specifies the length, in maximum number of bytes, of tuple data.

uDataLen

[OUT] Specifies the length, in actual number of bytes, of tuple data.

Remarks

Because this structure is similar to the CARD_TUPLE_PARMSstructure, a driver could use a single CARD_DATA_PARMSstructure for all calls to the CardGetFirstTuple, CardGetNextTuple, and CardGetTupleDatafunctions.

Requirements

Runs on	Versions	Defined in	Include	Link to
Windows CE OS	1.0 and later

Note This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.

Last updated on Tuesday, July 13, 2004