Share via

CardGetNextTuple (Windows Embedded CE 6.0)

  • Article

1/6/2010

This function retrieves the next tuple of the specified type for the specified socket and function.

Syntax

STATUS CardGetNextTuple(
  PCARD_TUPLE_PARMS pGetTupleParms 
);

Parameters

Return Value

CERR_SUCCESS indicates success. One of the following values indicates failure:

  • CERR_BAD_ARGS
    Indicates that the pointer specified for pGetTupleParms is not valid.
  • CERR_BAD_SOCKET
    Indicates that the hSocket socket identifier in CARD_TUPLE_PARMS is not valid or that no PC Card is inserted in the socket.
  • CERR_NO_MORE_ITEMS
    Indicates that the end of card information structure (CIS) has been reached or that the requested tuple was not found.
  • CERR_OUT_OF_RESOURCE
    Indicates that card services is unable to set up a memory window to read the CIS.
  • CERR_READ_FAILURE
    Indicates that no PC Card is inserted or that the PC Card is unreadable.

Remarks

This function follows the CIS tuple chain, as specified by the uLinkOffset, uCISOffset, and fFlags members of CARD_TUPLE_PARMS. These members were set by a previous call to the CardGetFirstTuple function or this function.

To obtain tuple data, use CardGetTupleData.

The driver retains the values returned in the uLinkOffset, uCISOffset, and fFlags members of CARD_TUPLE_PARMS so that subsequent calls to this function or CardGetTupleData can follow the tuple chain. The driver does not access the uTupleCode and uTupleLinkmembers unless the return value is CERR_SUCCESS.

The CARD_TUPLE_PARMS and CARD_DATA_PARMS structures are arranged so that their corresponding members are aligned. With care, drivers can use a single buffer in all calls to the card services tuple functions.

Requirements

Header cardsv2.h
Library Pcc_serv.dll
Windows Embedded CE Windows CE 1.0 and later

See Also

Reference

PC Card Driver Functions
CARD_DATA_PARMS
CARD_TUPLE_PARMS
CardGetFirstTuple
CardGetTupleData