QComm comes with several configurations ready to run. A configuration script defines what command line options are available to the user, what actions to take when the user presses certain keys, and what methods are available for exchanging data with the serial device. Text that goes to the serial port and text that comes from the serial port can be tightly or loosely monitored, it can be visible or invisible to the user - you configure it.
QComm allows full control over your serial ports - from COM1 to COM4. Baud (up to 57.6K), start/stop bits, data bits, parity, and line duplex can be set. DSR and DTR can be controlled. IRQ level and COM port address can be explicitly set. And, for chips that support it, FIFO size may be configured.
One example configuration that comes with QComm is geared toward BASIC-52 users. It can upload and download BASIC files. It can RUN a program and quit when finished. It can provide a terminal session until the user presses the exit key. And it can log that run or terminal session to a file.
Another example configuration supports modems. It can auto-dial a phone number for convenience, call a number and connect to it, or issue an AT command. Of course this configuration can be easily modified to support other modem uses.
QComm was not designed to compete with the highly interactive communications tools already on the market. Those tools put the user interface first and the scripting language second. QComm puts the scripting language first which in turn defines the user interface. QComm is ideal for controlling user-initiated interaction with serial devices, for automating serial communications.
Minimum system requirements: DOS 2.0+, 128K RAM, one floppy drive, and a serial port.