Serial Port Driver Registry Settings (Compact 2013)
3/26/2014
The following table shows the registry subkeys, values, and descriptions for the HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial serial port driver registry key.
Subkey |
Value |
Description |
---|---|---|
"SysIntr" |
dword:13 |
Hardware-platform-dependent. SYSINTR_FIRMWARE plus the IRQ. |
"IoBase" |
dword:02F8 |
Hardware-platform-dependent base address of port-mapped I/O. |
"IoLen" |
dword:8 |
Hardware-platform-dependent I/O space mapping to a virtual address in a memory-mapped I/O system. Notifies the system how much larger the address window is. |
"DeviceArrayIndex" |
dword:0 |
Serial port that the driver manages. This key specifies the serial adapter that the driver manages. It also specifies the object to use inside the driver DLL. It is only useful for multi-object drivers, such as serial drivers, built-in drivers, and so on. You cannot use this key for single object drivers. |
"Prefix" |
"COM" |
Entry point prefix. The entry point is constructed from the Prefix value and the name of the entry point. If the driver exposes the stream interface with undecorated entry points, no Prefix value exists. |
"Dll" |
"Serial.Dll" |
DLL loaded by the bus enumerator. |
"Order" |
dword:0 |
Value between zero (0) and 255. The smallest Order value gets loaded first. If there is no Order value, the driver loads after drivers with defined Orders. |
Exposing a Serial Device to the Telephony API
To expose a serial device to the Telephony API (TAPI), you must create a Unimodem registry subkey under the HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial registry key. The HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial\Unimodem registry subkey must contain values for Tsp, DeviceType, FriendlyName, and DevConfig.