Microsoft Windows CE 3.0  

Drivers for PC Card Devices

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.

Stream interface drivers for PC Cards are PC Card client drivers. They use the PC Card Services library to interact with their PC Card devices. The PC Card Services library handles all the details of moving data across the PCMCIA bus, thus allowing stream interface drivers for PC Card devices to concentrate on device-specific tasks. Windows CE supports PC Card Type II sockets. PC Card client drivers can also interact with the PCMCIA Socket Services library, if necessary.

Most PC Card socket functions have a parameter that represents a socket and function pair. A socket and function pair is a combination of one particular PC Card socket and one particular function of a PC Card. Socket and function pairs support multifunction PC Cards and platforms with more than one PC Card socket. Drivers for multifunction cards should register one device file name for each function. Any drivers that you create for PC Cards should also be written to work with any socket index because different platforms have different numbers of PC Card sockets.

If you write a generic PC Card driver — one that can drive an entire class of PC Cards adhering to a specified operating standard — you need an additional entry point in the DLL for a detection function. The Device Manager uses the detection function when a user inserts an unknown PC Card with no Plug and Play identifier. This function must conform to the PFN_DETECT_ENTRY prototype declared in Public\Common\DDK\Inc\DevLoad.h. For more information on PC Card detection functions, see Device Manager.

Note that user-level applications cannot access the PC Card Services library directly. An application that attempts to call LoadLibrarywill encounter errors because of the way the Device Manager manages the PC Card Services library. Applications that need to access these functions should do so by means of a small, intermediate device driver that provides wrappers around the functions in the library.

The following table lists the functions in the PC Card Services library that drivers for PC Card devices use to interact with PC Cards.

CardAccessConfigurationRegister CardReleaseExclusive
CardDeregisterClient CardReleaseIRQ
CardGetEventMask CardReleaseSocketMask
CardGetFirstTuple CardReleaseWindow
CardGetNextTuple CardRequestConfiguration
CardGetParsedTuple CardRequestExclusive
CardGetStatus CardRequestIRQ
CardGetTupleData CardRequestSocketMask
CardMapWindow CardRequestWindow
CardModifyWindow CardResetFunction
CardRegisterClient CardSetEventMask

 Last updated on Tuesday, July 13, 2004

© 2004 Microsoft Corporation. All rights reserved.