 |
Please see the Why CLACom section for more detailed information.
|
Features
|
Product
|
|
CLACom
|
CLACom Lite
|
Win API
|
Win Event
|
|
Number of Functions (1)
|
117
|
51
|
17
|
9
|
|
COM Ports Supported (2)
|
255
|
20
|
See Note
|
8
|
|
Port Initialization Functions
|
12
|
7
|
2
|
2
|
|
Input (Receive) Functions
|
12
|
9
|
1
|
1
|
|
Output (Send) Functions
|
7
|
4
|
1
|
1
|
|
Buffer Overflow Detection
|
Yes
|
Yes
|
Yes
|
No
|
|
Error Reporting
|
Yes
|
Yes
|
No
|
Yes
|
|
Modem Status (3)
|
Yes
|
Yes
|
Yes
|
No
|
|
Modem Control (4)
|
Yes
|
Yes
|
Yes
|
No
|
|
Hardware Flow Control (5)
|
Yes
|
Yes
|
Yes
|
No
|
|
Terminal Emulation
|
Yes
|
No
|
No
|
No
|
|
File Transfer
|
Yes
|
No
|
No
|
No
|
|
Printed Manual (6)
|
Yes
|
PDF
|
No
|
No
|
|
Price
|
$239 - $254
|
$49
|
Free
|
$99
|
- Serial Port Functions only. The 16 Bit Windows API contains 17 functions, the 32
Bit Windows API contains 19 functions. In 32 Bits, Serial Ports are treated as Files, which adds many
additional functions. WinEvent supports 4 extra functions in 32 bits that are a single function call
in CLACom and in the Windows API (16 and 32 bits).
- This number represents the number of simultaneous Ports that the software supports
and is limited by Hardware and Operating System. 16 Bit Windows supports up to 8 Serial Ports, 32 Bit
Windows supports up to 255 Serial Ports.
- Modem Status indicates the status of a Device such as whether the Phone is Ringing,
the Modem is Connected to another Modem, the Device is Enabled, and whether the Device is able to Receive
Data. The last two are important because most devices, not just Modems, use these Control Signals to
tell Windows when it should send data. WinEvent supports these Status signals in 32 bits only and considers
them to be "advanced features".
- Modem Control refers to the ability of your program to tell a Device whether or
not your program is able to Receive Data.
- WinEvent supports Xon/Xoff Software Flow Control only. Most Devices that you will
interface with utilize Hardware Flow Control.
- There is no definitive Manual for the Windows Communications API. To use the Win
API, several books will need to be purchased.
Information derived from manufacturer data sheets and documentation, current as of
September 1, 2002.
|