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. |
A default registry entry always exists for a Hayes-compatible modem that is connected to COM1. You can specify additional external modems under the HKEY_LOCAL_MACHINE\ExtModemskey. Most of the values that are set for PCMCIA modems also apply to external modems, except that the following values are ignored for external modems.
Value : type | Default | Description |
---|---|---|
TSP |
Unimodem.dll |
This value is redundant because Unimodem processes the ExtModemkeys. |
DeviceArrayIndex: REG_DWORD |
1 |
The Serial.dll file uses these registry values when it loads for the port on which the external modem is connected. |
Prefix |
COM |
|
DLL |
Serial.dll |
|
ResetDelay: REG_DWORD |
800 |
|
The following code example of registry entries will cause TAPI 2.0 to create a line device for the external modem from CompanyX and present it as one of the available TAPI devices. In this minimal example, all of the default settings from the HKEY_LOCAL_MACHINE\Driver\Unimodem\Initand \Settingskeys will be used.
Copy Code | |
---|---|
[HKEY_LOCAL_MACHINE\ExtModems\CompanyX-Modem] "Port"="COM1:" "DeviceType"=dword:1 "FriendlyName"="CompanyX External Modem" [HKEY_LOCAL_MACHINE\ExtModems\CompanyX-Modem\Init] [HKEY_LOCAL_MACHINE\ExtModems\CompanyX-Modem\Settings] |