Copyright (C) 1999, 2000, 2001 Chris Vine, G3XXF

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    A copy of the GNU General Public License version 2 is set out
    in the file COPYRIGHT accompanying this distribution.  You can
    also obtain a written copy from the Free Software  Foundation,
    Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

		INSTALLATION: FROM SOURCE FILES

To install, place the distribution file in a local source directory
(eg ~/src).  Untarring/unzipping it will create a sub-directory
'kam-gtk' where the source code can be found.  You can now edit the
kam configuration file kamrc (which will be placed by "make install"
in /etc) so that it matches your serial port, speed setting for your
Kam, and callsign (see further below under "setup" for more on this
file), and other particualars.  kamrc specifies run-time not
compile-time options, but you can edit it now so that the version
installed by "make install" is correct.  Alternatively, you can start
up the program, enter your callsign and serial port particulars with
the initialisation dialogs which will automatically come up, and enter
any other settings once the program has started by bringing up the
`Settings' dialog from the `File/Settings' pull-down menu once the
program has started.  (See below).  You must restart the program after
making any later change using the `Settings' dialog to the settings
for the serial port device or serial port speed.  In addition, the
callsign or selcall settings cannot be changed using the Settings
dialog while there is an active connection, or a connection is being
attempted.

Then enter the command `./configure'.  This will set up the Makefile
so that it matches your system.  This can be done as user (you do not
need to be root).  Then type "make", and then "make install".  "make
install" must be run as root so that the correct permissions are given
for proper program operation.  "make" can be run as user.  The program
and configuration files (other than kamrc) will by default be
installed in /usr/local/kamdir.  The name of the executable is
"kam-gtk".

"make install" will give suid and sgid permissions to the installed
binary.  If appropriate permissions are given to the serial device
(/dev/ttyS*), this can be refined and changed for the security
conscious, by modifying the install permissions and ownerships given
in the file `Makefile.presets' before running `configure' (or by
modifying Makefile after configure has been run).  However, by default
the main program process will release suid/sgid permissions, leaving
only the process managing the serial port with root privileges.

When `./configure' is run, the following parameters can be passed
which will modify the ordinary defaults (for an ordinary compile you
will not need to use any of these - just entering `./configure' will
be sufficient):

  The default installation directory is /usr/local/kamdir.  The
  directory in which the program files are installed can be changed 
  by running configure with the --prefix=DIR.  By default the
  executable files (kam-gtk and endhost) are placed in the same
  directory but this can be changed by running configure with the
  --exec-prefix=DIR parameter
  (eg ./configure --prefix=/usr/local/share/kamdir --exec-prefix=/usr/local/bin)

  By default, the program will release suid/sgid privileges on all
  but the process managing the serial port.  To change it, run
  configure with the --enable-keep-privileges parameter

  By default, the lock files are normally stored in /var/lock.
  This can be changed by running configure with the
  --with-lockdir=DIR parameter
  (eg ./configure --with-lockdir=/var/serial/lock)

  By default the programs assumes that the X server on which the
  program is displayed displays Latin-1 characters for continental
  characters.  This is the character set used by most Unix systems.
  It can be changed by running configure with the
   --with-charset parameter, set to `cp437' (for Code Page 437) or
  `ascii' for plain ASCII (it can also be explicitly set to `latin-1',
  but that is the default).
  (eg ./configure --with-charset=ascii)
  NOTE: this option is concerned with the local display, not with what
  is transmitted.  The character set transmitted is set using the
  CHAR_SET: option in the configuration file kamrc.

  By default the program will be compiled to support Pactor and G-Tor
  modes.  To exclude either of these when compiling for an older
  Kam or Kam Plus which does not support them, run configure with the
  --disable-pactor or --disable-gtor parameters.  (Disabling Pactor
  will also automatically disable G-Tor).
 (eg ./configure --disable-gtor)

  By default, the program will use the 'E' command to change over
  from transmit to receive (or from ISS to IRS), which will cause
  the Kam to only complete the changeover when all text previously
  entered has been sent -- this is the default.  Some older Kams may
  not support the 'E' command.  To provide an immediate change-over,
  whether there is buffered text or not, run configure with the
  --disable-buffered-changeover parameter.
 (eg ./configure --disable-buffered-changeover)


Additional `configure' parameters can be seen by entering
`./configure --help'.  If you have run configure, and want to run it
again, enter `make clean' beforehand to clear out the cache.

If you have an unusual set-up which `configure' cannot cope with and
it reports errors which you think are unjustified, and those errors
relate to detecting the presence of Gtk+, libsigc++ or Gtk--, you can
omit these tests by running configure with the --disable-gtktest,
--disable-sigctest and --disable-gtkmmtest parameters respectively.
If something else is amiss which you think is unjustified, try copying
Makefile.sample to Makefile and config.h.sample to config.h (these
sample files are a typical Makefile and config.h which `configure'
would produce), and then amending them by hand to suit your system
before running `make' and `make install'.

This program can safely be installed in the same directory as the
"kamplus" program for ncurses and Qt, as they can share the same
configuration and other files.

To compile and link, gtk+-1.2.*, libsigc++-1.0.* and gtkmm-1.2.* must
be installed.  You must have these and the respective
gtk+-devel-1.2.*, libsigc++-devel-1.0.* and gtkmm-devel-1.2.* rpm
packages installed if you use the Red Hat rpms.

	INSTALLATION: FROM PRE-COMPILED LINUX BINARY FILE

To install, place the distribution file in a local source directory
(eg ~/src).  Untarring/unzipping it will create a sub-directory
'kam-gtk' where the source code can be found.  You can now edit the
kam configuration file kamrc (which will be placed by
"./install_kamplus" in /etc) so that it matches your serial port,
speed setting for your Kam, and callsign (see further below under
"setup" for more on this file), and other particualars.  kamrc
specifies run-time options, but you can edit it now so that the
version installed by "./install_kamplus" is correct.  Alternatively,
you can start up the program, enter your callsign and serial port
particulars with the initialisation dialogs which will automatically
come up, and enter any other settings once the program has started by
bringing up the `Settings' dialog from the `File/Settings' pull-down
menu once the program has started.  (See below).  You must restart the
program after making any later change using the `Settings' dialog to
the settings for the serial port device or serial port speed.  In
addition, the callsign or selcall settings cannot be changed using the
Settings dialog while there is an active connection, or a connection
is being attempted.

The pre-compiled binary is compiled against gtk+1.2.10, gtk--1.2.8 and
libsigc++1.0.3.  It is statically linked, so it does not use the gtk+
shared libraries.  To install run the shell script file
`./install_kamplus'.  This must be done as root so that the correct
permissions are given for proper program operation.  The program and
configuration files (other than kamrc) will be installed in the
directory specified in `install_kamplus'
 - this is /usr/local/kamdir by default.

The name of the executable is "kam-gtk".

"./install_kamplus" will give suid and sgid permissions to the
installed binary.  If appropriate permissions are given to the serial
device (/dev/ttyS*), this can be refined and changed for the security
conscious.  However, the main program process in the pre-compiled
binaries will release suid/sgid permissions in any event, leaving only
the process managing the serial port with root privileges.

This program can safely be installed in the same directory as the
"kamplus" program for ncurses and Qt, as they can share the same
configuration and other files.

The binary is statically linked so that it will run independently of
the system in which it is installed.  If you have a number of
applications running, this will not make the most efficient use of
memory resources.  If memory is tight, you should consider recompiling
from the source which comes with the distribution so as to use the
shared system libraries (see above for how to do that).

                            SETUP

As mentioned above, `make install' or `./install_kamplus' will by
default place the kam configuration file (kamrc) in /etc.  The
settings in kamrc can be changed by manually editing kamrc before
running either of these, by manually editing $HOME/.kamrc,
/usr/local/etc/kamrc or /etc/kamrc afterwards, or by using the
Settings dialog from the File/Settings pull-down menu.  The
configuration file is searched for in that order, so $HOME/.kamrc
takes precedence over /usr/local/etc/kamrc and /etc/kamrc.

You must restart the program after making any change using the
Settings dialog to the initial settings for the serial port device or
serial port speed.  In addition, the callsign or selcall settings
cannot be changed using the Settings dialog while there is an active
connection, or a connection is being attempted.

The settings entered using the start-up initialisation dialogs or the
Settings dialog are always stored as $HOME/.kamrc.  Accordingly, if
the Settings dialog has been used, and you want to revert to the
global settings, this can be done either by deleting the $HOME/.kamrc
file, or by pressing the `Reset' button in the Settings dialog, which
will reload the Settings dialog from /usr/local/etc/kamrc or
/etc/kamrc.

Help can be obtained when filling out the Settings dialog by holding
the mouse over the relevant help (?) button, which will bring up a
"Tips" display, or by pressing the button, which will bring up an
information display.

Amongst the settings which are contained in kamrc is the directory in
which other relevant kam files (such as "messages") can be found and
in which the capture file capture.txt and certain temporary files will
be written.  The directory must therefore be one in which there will
be write permission.  It is recommended that this directory should
either be the same one in which the kam executable is installed -
normally /usr/local/kamdir, as "make install", "./install_kamplus"
("make install" and "./install_kamplus" will automatically give the
correct write permissions to this directory).

The kam configuration file may specify your Amtor selcall, but it does
not need to do so.  If you do not specify a selcall, then the standard
four letter selcall matching your callsign will automatically be
generated by the program for you.

The sample file kamrc which comes with this distribution and the help
(?) buttons in the Settings dialog give further details - it is much
easier than this explanation sounds.

Before using the program you must also have initialised the Kam (if
you have already used your Kam with another program then it will
already be initialised, and you can skip this part, subject to the
comment about speeds below).  To do this you can put the program in
terminal mode instead of host mode by typing "kam-gtk setup" instead of
"kam-gtk" when starting the program.  To see how to go from there, look
at the handbook under "Initializing the KAM Plus".

The SPEED: setting in the Kam configuration file (kamrc) must match
the speed the Kam has been initialised for.

Note that if you have previously initialised the kam using the DOS
Pacterm program which comes with the Kam Plus, Pacterm operates at
1200 baud Kam/Computer link speed, whereas you will be better off with
9600 baud, as host mode involves additional tnc/computer traffic in
order to keep track of the Kam status information.

It is therefore best to set up the Kam for 9600 baud.  One way of
doing this if the Kam has previously been initialised for a lower
speed is to put the SPEED: setting in kamrc to the speed the Kam has
previously been initialised for, start the program as "kam-gtk setup"
so that you are in terminal mode, and then enter the Kam command
RESTORE DEFAULTS.  This will cause the Kam to re-initialise.  Then
quit the program, amend the speed setting in /etc/kamrc to 9600,
restart the program with "kam-gtk setup", wait for the auto-baud
detect prompt and press '*'.  See the Kam Plus handbook for further
details.

		      USE OF THE PROGRAM

When first used in host mode, the Kam must be switched on before the
program is run, so the program will place the Kam in Host mode.  Once
the program is started for the first time, Press F9 to send the Kam
parameters in file "tnc.parms".  Until this is done, the program will
not interface with the Kam correctly.

The program will leave the Kam in Host mode.  If you want to get out
of host mode, either use the "endhost" utility installed in the same
directory as "kam-gtk", or start the program again using "kam-gtk
setup" so that the Kam is placed in terminal mode.

The first time you use the program, you will be asked if you accept
the terms of the General Public Licence, version 2.  If you have not
entered your callsign and serial port particulars by editing the kamrc
configuration file, you will also be asked to enter these.

The program can be operated from the mouse, using the buttons and
pull-down menus.  However the program can also be operated by using
the following hot keys, which for compatability are the same as those
used by the console based "kamplus" program which uses the ncurses
library.

The keyboard hot keys operate as follows:

Cursor up - Scroll up.
Cursor down - Scroll down.
Cursor right - Scroll out (end scroll).

Page Up - changeover to transmit (HF modes).
Page Down - changeover to receive (HF modes).

Ctrl-A: change to Amtor mode (or send Ctrl-A - see below).
Ctrl-C: change to CW mode (if not in CW mode) or set the speed (if in CW
	mode).
Ctrl-D: disconnect (Packet, Pactor, Amtor and Gtor).
Ctrl-F: change to FEC.
Ctrl-G: change to G-tor.
Ctrl-L: change to Lamtor.
Ctrl-O: change to Gmon.
Ctrl-P: change to Pactor.
Ctrl-R: change to RTTY (Baudot) (if not in RTTY mode) or set the speed
        (if in RTTY mode).
Ctrl-S: change to ASCII (if not in ASCII mode) or set the speed (if in
        ASCII mode).
Ctrl-T: change to TOR mode (or send Ctrl-T - see below).
Ctrl-X: change to HF Packet.
Ctrl-Z: send Ctrl-Z (see below).

Alt-B: print the current scroll buffer.
Alt-C: send an auto-cq (Pactor, Amtor, Gtor or Tor)
       or (if in auto-cq mode) end auto-cq.
       (see also Alt-T below).
Alt-D: Download a 7plus/uuencoded file to a local file (Packet, Pactor
       or Gtor) (this makes no translations other than CR -> LF).
Ctrl- Alt-D: Download a binary file to a local file (Packet, Pactor or
       Gtor) (this saves the raw data to disk).
Alt-I: send ident ([CALL IN STORE] de [YOUR CALL]).
Alt-L: toggle whether receive speed locked to 100 baud (Pactor or Gtor).
Alt-N: toggle whether in Monitor DX Cluster mode.
Alt-P: set a print mark, or if one is already set, print from the mark.
Alt-R: enter an RST report to be stored in the RST buffer.
Alt-S: sync the transmit speed to the current receive speed (CW), or
       resync the Amtor decoder when monitoring (Amtor/Lamtor).
Alt-T: send an auto-cq when listening in Tor-standby mode but using
       Pactor FEC to send the CQ.
Alt-U: Upload a 7plus/uuencoded file (Packet, Pactor or Gtor) (this
       makes no translations other than LF -> CR).
       (Press again to abort the upload).
Ctrl-Alt-U: Upload a binary file (Packet, Pactor or Gtor) (this
       sends raw data and makes no translations).
       (Press again to abort the upload).
Alt-X: abort (Pactor, Amtor, Gtor or Tor)
Alt-0 to Alt-9: send the messages specified in the "messages" file.
Alt+ (Alt-plus): start/increment the QSO counter.
Alt- (Alt-minus): decrement the QSO counter.

F1: toggle display of Help file.
F2: toggle on/off capture of current stream to file [KAMDIR:]/capture.txt.
F3: toggle transmitting of text after word/line or with a guard in
    non-packet mode (see below).  
F4: connect with another station (Packet, Pactor, Amtor and Gtor).  
F5: send a command to the Kam (press again to run a configuration script).
F6: send a text file.
F7: enter another station's callsign in the callsign store.  
F8: toggle the callsign lock (see below).  
F9: send the Kam parameter file tnc.parms to Kam.  
F10: toggle the screen display between VHF and HF port of Kam.  
F11: go down a stream on the screen display (e.g. from stream C on current
     port to stream B).  
F12: go up a stream on the screen display (e.g. from stream A on current
     port to stream B).  (See the note below on the F12 key if you are
     using KDE-2).

Pressing Ctrl-A when in Packet, Pactor or Gtor mode and connected
will send a Ctrl-A character instead of asking whether to change to
Amtor mode (some BBSs use Ctrl-A to abort a message being sent)

Pressing Ctrl-T when in Packet, Pactor or Gtor mode and connected
will send a Ctrl-T character instead of asking whether to change to
Tor mode (some BBSs use Ctrl-T to abort a telnet session)

Pressing Ctrl-Z when in Packet, Pactor or Gtor mode and connected
will send a Ctrl-Z character (some BBSs use Ctrl-Z to end a message as
an alternative to /EX)

If Alt-C or the "auto-cq" button is pressed when in Pactor, Amtor,
Gtor or Tor-Standby modes, the program will run the CQ message found
in the file 'cq' placed in the directory specified by 'KAMDIR:' in
kamrc, repeating until a link is made.  It can be turned off by
pressing Alt-C or the "auto-cq" button again.  The delay between the
end of one CQ message and the start of the next may be specified by
the AUTOCQ: parameter in kamrc.  If none is specified, the default is
90 seconds (don't cook your output stage).  If in Tor-Standby mode,
pressing Alt-T will do the same, except that the CQ message will be
sent in Pactor FEC not Amtor FEC mode.  Pressing the "auto-cq" button
when in Tor mode will bring up a dialog, offering the choice of Amtor
FEC or Pactor FEC.  To stop an auto-cq session, press Alt-C or the
"auto-cq" button again.

Files can be uploaded, or downloaded to local disk, by choosing from
the upload and download menus.  The same can be done by hot-keys: if
Alt-D is pressed and the Kam is connected in Packet, Pactor or Gtor
mode, you can download a 7-plus file to local disc.  If Alt-U is
pressed, a 7-plus file can be sent.  The only character tranlations
made are LF -> CR when uploading, and CR -> LF when downloading, as
required by the Packet network.  These differ from sending a text file
via F6 or from the upload menu, or capturing a file via F2, by making
no other character translations.  With an ordinary compile, if a
stream is being captured, or if a text file is being uploaded from the
upload menu or by pressing F6, the stream will be captured or the file
sent using continental characters with a Latin-1 (computer) <-> Code
Page 437 (packet network) translation.  To work, the Kam parameters
are best set so that AUTOLF is OFF, AUTOCR is 0, CRADD is OFF, CRSUP
is OFF, LFADD is OFF and LFSUP is OFF.  (Running tnc.parms via F9 will
set these correctly automatically and the program will carry out all
the necessary CR/LF insertions (HF Tor modes) and CR <-> LF
translations (Packet mode).

Selected text in the receive window can also be saved to file from the
pull-down menu or from the right mouse pop-up menu.

When a binary download is chosen from the menu or Ctrl-Alt-D is
pressed, if the Kam is connected in Packet, Pactor or Gtor mode, a
download can be made of raw data to local disc with no character
translations, and if a binary upload is chosen from the menu or
Ctrl-Alt-U presssed, the program will upload raw data.  However, these
do not use any special protocal such a YAPP, so they are as yet only
really suitable for 7plus or UUencoded files which are being sent on a
direct station to station link not involving the Packet network, or
which have already had a LF -> CR translation made to them.  To send
raw data, it is essential that the Kam parameters are set so that
AUTOLF is OFF, AUTOCR is 0, CRADD is OFF, CRSUP is OFF, LFADD is OFF
and LFSUP is OFF as mentioned above.

If the lock button or Alt-L is pressed when in Pactor or Gtor mode,
the receive speed will be locked to 100 baud, and the bottom status
line will show "LOCK".

If Alt-1 to Alt-5 are pressed, the message specified in the file
"messages" will be sent ("messages" will be looked for in the
directory specified by KAMDIR: in kamrc).  Such a message should not
exceed MESSAGE_SIZE defined in prog_defs.h (276 bytes in the standard
distribution).  If Alt-6 to Alt-0 are pressed, the file specified in
the "messages" file will be sent.  There is no maximum message size
for a file sent with Alt-6 to Alt-0.  See the specimen "messages" file
installed by "make install" for further details.  Also see the
specimen "kamrc" file for the NOPROMPT option which will send the
relevant message without asking for confirmation first.

When sending a message or file via Alt-0 to Alt-9, seven shortcuts are
provided - $a is translated to your call, $b is translated to your
selcall, $c will be translated to the call in the callsign store
buffer for the currently active screen, $d will be translated to the
current time in UTC (hours and minutes),$e will be translated to the
current date (day-month-year), $f will be translated to the value (if
any) currently held in the RST report buffer and $g will be translated
to the value currently held in the QSO counter.  These translations do
not apply to any file sent via the F6 key - files sent via F6 are sent
exactly as they appear.

To start the QSO counter and the QSO counter dialog, press Alt-plus or
use the "File" pull-down menu or the pop-up menu.  (The QSO counter is
intended to make it easier to send contest reports by means of the $g
macro).  The QSO counter can be incremented or decremented using
Alt-plus or Alt-minus from the keyboard, or by using the buttons on
the QSO count dialog (the Alt-plus and Alt-minus keys on the keyboard
will increment the counter even though the main program and not the
counter has keyboard focus, which is quite handy).

The "Command" button or F5 can be used to send configuration scripts
as well as sending Kam commands entered directly at the keyboard.
Such scripts must be placed in the KAMDIR:/parms/ directory.  The
distribution comes with two scripts - 'home' and 'away', which contain
the kind of Kam parameters suitable for attended and unattended
operation.  To run a script, instead of entering a command directly at
the keyboard, press the "script" button in the connect dialog or F5
again, and then choose the script file.

When the HF port is not in a packet mode, it will send text to the Kam
depending on the setting chosen from the "Hf Send" menu or toggled by
F3.  If set to "Word", it will send text at the end of each word, if
set to "Line" it will send it at the end of each line (when Return is
pressed).  If set to "Guard", a minimum of 10 characters in any line
will be retained in the transmit queue, which can be erased from the
keyboard before being sent to enable correction of errors.  This can
be useful in Amtor and RTTY modes which do not allow the transmission
of backspace characters.  Pactor and Gtor do allow transmission of
backspace/delete, so this setting is not so important for those modes.

When the HF port is not in a packet mode, the program will search
incoming text for a valid callsign format, and if it finds one, enter
it in the Call Sign buffer (and also generate a SELCALL for calling a
station in Amtor).  Pressing the "Toggle callsign lock" button or
pressing F8 will lock the Call Sign buffer to the current displayed
callsign so that the buffer will not be updated.  When locked, an
asterisk will be displayed in front of the callsign shown on the
screen.  Pressing the button or pressing F8 again will unlock the
displayed callsign, so that it will be displaced by the next detected
valid callsign.

                    THE F12 KEY AND KDE-2

KDE-2.0 has anti-social default key bindings.  By default it grabs the
F12 key and uses it to place the keyboard in "mouse" mode (in mouse
mode the screen cursor can be controlled by using the keyboard cursor
keys).  To release this mode, which blocks all other keyboard input,
you must press F12 again.

The result is that the F12 key cannot be used as intended by the
program if you use KDE2 in its default set-up.  There are two
solutions:

  - use Shift-F12 to go up a stream on the current port, instead of
    F12 (the program will do this without change), or
  - change the KDE key binding for the F12 key.

To change the KDE key bindings, go to the KDE Control Center from the
`K' start menu and then pick the "Key bindings" item under "Look &
Feel".  Pick the "Global settings" tab and the fourth item down is
"Mouse emulation".  Highlight it and either click the "No key" box, or
click the "Custom key" box and pick another key (such as Shift-F12) to
put the keyboard in mouse mode.

Some other desktop environments or distributions may also do odd
things with key bindings.  If you find the keyboard does not do what
is expected, check the key bindings out.

               KEEPING PACKET CONNECTIONS ALIVE

A "keep alive" option can be set from the kamplus configuration file
/etc/kamrc.  This enables connections to nodes and BBSs, etc. to stay
up even if there is no traffic, by sending empty frames to any active
packet connections if no data is received/transmitted within the
period set by KEEPALIVE_MINS: in /etc/kamrc.  The kamplus
configuration file /etc/kamrc establishes the start-up setting: "keep
alive" can also be switched on and off from the "Setting" menu.

In fact, I have found no way to get the Kam Plus to send a proper
"null" packet (a packet with no data enclosed) and a "keep alive"
packet therefore sends a single space character.  This will cause the
least impact on text based packet network interfaces, but will cause
problems if you are uploading a file.  When uploading a file which may
have pauses in data transmission/reception greater than the setting of
KEEPALIVE_MINS, turn this option off.

                   MONITORING DX CLUSTERS

The program has a "Monitor DX Cluster" mode, which enables DX spots to
be monitored from a DX Cluster even when not connected (it monitors
spots sent to other connected stations).  This can be useful if the
Cluster is very busy by saving unnecessary traffic (as well as
avoiding the difficulty of staying connected on a busy node): the
program automatically cleans up the display to appear as if connected,
and checks for (and eliminates) duplicates sent to multiple connected
stations.

You can enter and leave DX Cluster mode by pressing Alt-N on the
keyboard or by pressing the "Monitor DX Cluster" button on the
toolbar.

The monitored Cluster will appear on the highest VHF stream available
to the program (with the default compile of 8 channels on each port,
this means that the Cluster will appear on the VHF-H stream).  This
also means that you cannot enter DX Cluster mode if you are connected
to another station on VHF-H stream - however, since connects from
other stations start at VHF-A and work upwards to the lowest free
stream, this is most unlikely to happen.  (You can also use the Kam
USERS command to define the maximum number of stations who can
initiate a connection with you, so keeping VHF-H free).

If the program has been set to sound the bell character, the program
will beep whenever a new dx spot is displayed.

                      CONNECT SCRIPTS

The program can ease the task of making Packet connects via nodes by
running automatic connect scripts.  See the file CONNECT_SCRIPTS with
this distribution for further details.

                         CLIPBOARD

Received text can be imported into other programs by copying it onto
the clipboard via the File pull-down menu or the right-mouse pop-up
menu.  (It can of course also be downloaded to file or captured to
capture.txt as mentioned above.)

                 CONTINENTAL CHARACTERS (LATIN-1)

To display continental characters, compile the program in its default
configuration with the latin-1 character set (as this is the default,
so you do not need to do anything special to achieve this when running
`./configure').

The transmitted and received character set (as opposed to the locally
installed character set on the X Server) can be set with the CHAR_SET:
parameter in the configuration file kamrc (see that file for further
details), or it can be set for the duration of the program from the
Settings item in the File pull-down menu or in the right click pop-up
menu.

                       PROGRAM APPEARANCE

The default font size of the menu bar and status bars is the Gdk
default (normally 12 point).  It can be set to 10 point or 11 point or
set explicitly to 12 point with the fontsize argument, as follows:

kam-gtk -fontsize 10
kam-gtk -fontsize 11
kam-gtk -fontsize 12

This assumes that you have adobe helvetica fonts installed (I do not
know of any Unix/Linux distributions which do not include this font).

The fontsize argument does not affect the fontsize of the display
windows.  The receive and send display window font size can be set at
start up with the WIN_FONTSIZE option in the configuration file
/etc/kamrc, or from the Settings dialog once the program has started.

The receive text window displays text in various colours, as follows:

black:  packet text when connected, and text received in Tor modes
        (including RTTY).
blue:   transmitted text in Tor modes (including RTTY).
green:  monitored Packet transmissions.
red:    response to sending a command to the Kam Plus.
purple: Kam Plus status information.

                           PRINTING

Received text can be printed in three ways:

1.  From the File pull-down menu or the right-mouse pop-up menu, or by
pressing Alt-B, the entire contents of the scroll buffer for the
stream currently displayed can be printed.

2.  From the File pull-down menu or the right-mouse pop-up menu, or by
pressing Alt-P, a print mark can be made in the stream currently
displayed.  At any later time, the text following the print mark can
be printed, either by pressing Alt-P again or via the menus.

3.  If text in the receive window is highlighted using the mouse, the
selected text can be printed out from the appropriate entry in the
File pull-down menu or the right-mouse pop-up menu.

The default printer command used is 'lpr'.  A special printer command
can be set with the PRINT_CMD: setting in kamrc (see the sample kamrc
file for further details).

		      CONTACTING THE AUTHOR

I can be reached at:

chris@cvine.freeserve.co.uk
G3XXF@GB7MSW.#33.GBR.EU

Updates can be obtained from:
http://www.cvine.freeserve.co.uk/

I am happy to arrange skeds on HF.

73, Chris.
