 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. |
The name of a generic device driver can be used as a subkey of the Drivers\PCMCIA\key in conjunction with drivers listed within the Drivers\PCMCIA\Detect\key. Such Drive rsubkeys are similar to the Drivers\PCMCIA\Plug-and-Play-IDkey with respect to the values they contain.
The following table shows the values for this subkey. Additional values can be stored for purposes specific to the device.
| Value name | Value type | Description |
|---|---|---|
| Dll | REG_SZ | This required entry specifies the file name for a driver DLL that the Device Manager is to load. |
| Prefix | REG_SZ | This value, if it exists instead of Entry, specifies the device file-name prefix of the device driver. It is a three-character identifier, such as COM. |
| Index | REG_DWORD | Optional. Specifies the device index. This value specifies the index assigned to the driver. If this value is not present, the Device Manager assigns the lowest index value available. This index is associated with the device. Only index values from 0 through 9 are allowed. Let the Device Manager determine the index value. |
| Context | REG_DWORD | Optional. Specifies the device context. If this value is present — that is, if it was initialized by the device's setup application — the Device Manager passes it as the dwInfoparameter to the RegisterDevicefunction. If it is not present, a pointer to a string containing the registry path to the device's Activekey is passed as the parameter. The driver's initialization function can then open this key to read its information. To let the driver read the Activekey data, do not initialize this value. |
| Ioctl | REG_DWORD | Optional. Specifies an optional I/O control code
that the Device Manager sends to an stream interface driver. If
this value is present, the Device Manager opens the loaded driver
and calls its I/O control function. The Device Manager passes the
I/O control code specified by the
Ioctlregistry key. The driver does any necessary
post-initialization in this context. For example, the driver loads
modules that use the device.
In addition, the Device Manager broadcasts a WM_DEVICECHANGE message for the new device and signals the application notification system by means of the PegEventHasOccurredfunction, passing it the NOTIFICATION_EVENT_DEVICE_CHANGE message. |
For example, RAMCard is the name of a driver without a Plug and Play identifier. In addition to being listed within the Drivers\PCMCIA\Detectkey, this driver would also have a subkey within Drivers\PCMCIA\to store values, as shown in the following example.
HKEY_LOCAL_MACHINE [Drivers] [PCMCIA] [RAMCard] SZ: Prefix = RAM SZ: Dll = RAMCARD.DLL
Last updated on Tuesday, July 13, 2004