 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 function requests exclusive access to a specified socket and function pair.
STATUS CardRequestExclusive( CARD_CLIENT_HANDLE hCardClient CARD_SOCKET_HANDLE hSocket );
Parameters
- hCardClient
- Client handle obtained from the CardRegisterClientfunction.
- hSocket
- Handle to a socket and function pair.
Return Values
CERR_SUCCESS indicates success. One of the following values indicates failure:
- CERR_BAD_HANDLE
- Indicates that the driver handle specified for hCardClientis invalid.
- CERR_BAD_SOCKET
- Indicates that the socket identifier specified for hSocketis invalid.
- CERR_NO_CARD
- Indicates that no PC Card is inserted.
Remarks
This function signals Card Services to issue a series of callback events as it negotiates for approval with each registered driver. First, Card Services sends a CE_EXCLUSIVE_REQUEST event code to all registered drivers to determine if they allow exclusive use. If all drivers approve the request, Card Services sends each driver a CE_CARD_REMOVAL event code. Finally, it sends a CE_CARD_INSERTION event code to the requesting driver followed by a CE_EXCLUSIVE_COMPLETE event code. If any drivers do not approve, Card Services sends the requesting driver a CE_EXCLUSIVE_COMPLETE event code with a failing status in the Parm1member of the CARD_EVENT_PARMSstructure.
Driver name
PCMCIA
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.
See Also
Last updated on Tuesday, July 13, 2004