Microsoft Windows CE 3.0  

CardReleaseConfiguration

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 places the selected socket and card into a memory-only interface, which is the default mode.

STATUS CardReleaseConfiguration(
CARD_CLIENT_HANDLE
hCardClient
CARD_SOCKET_HANDLE
hSock
);

Parameters

hCardClient
Handle obtained from the CardRegisterClientfunction.
hSock
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 hSockis invalid or that a PC Card is not inserted.
CERR_IN_USE
Indicates that the configuration is owned by another driver.
CERR_WRITE_FAILURE
Indicates that this function is unable to write configuration registers.

Remarks

Card Services removes power if no other drivers are using the card.

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

CardRequestConfiguration



 Last updated on Tuesday, July 13, 2004

© 2004 Microsoft Corporation. All rights reserved. 500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.