Frequently asked questions
This section of the help contains answers to frequently asked questions about KComm.
Which operating systems does KComm run under?
KComm is available for both Windows and Linux. It has been tested using Windows XP SP2 and Xandros Desktop 4.1. I currently have no knowledge of whether it will work on other versions.
The Linux version lacks some functionality of the Windows version and is currently only at version 1.2, although you are welcome to try building the latest version from the source code archive.
Is KComm available for other platforms besides Windows and Linux?
KComm has been developed using Lazarus, an open source cross platform development tool that is available on Linux and Mac OS among other platforms.
Theoretically a Mac version should be possible to create, but since I don't possess an Apple Macintosh I have not tried it.
Does KComm support other (non-Elecraft) transceivers?
No.
KComm was designed specifically to make use of certain Elecraft-specific features such as the ability to send CW using computer control protocol commands which are not supported by other transceiver manufacturers. To avoid issues caused by third party libraries it has been written to use the Elecraft command protocol directly. No provision has been made to support other makes and models of transceiver, and to do so would be a major task that I have neither the time not the inclination to pursue.
What size log file can KComm handle?
That is a very good question. KComm stores the log in a flat file (text file), same as MixW. It does not use a database. There is no fixed limit to the number of entries in the log file. Any limits will be imposed by limitations in the display components used (unknown) or, more likely, by performance. In order to check for previous contacts, or whether a call entered is a new entity, KComm searches the entire log. This obviously takes longer the more contacts there are in the log, but a faster computer will mitigate this.
Very active operators might be advised to start a new log file every year, or to create separate log files for each contest. Casual operators will probably find that the log can increase to several thousand entries before performance becomes a problem.