Downloading and Installing tk150
on Linux-Based Systems
runs in the X Windows System graphical environment and is independent
of your desktop manager (e.g., KDE or Gnome).
is being tested on
a 1400 MHz AMD Athlon® based computer
running Red Hat® Linux® 7.3
and Tcl/Tk version 8.3, patchlevel 8.3.3.
This is experimental software and probably contains defects.
It remains under development.
When available, newer versions of
will be made available for download at this web site.
Downloading and Installing tk150 for Linux
Download and install the free tcl and tk RPMs
for your system.
You can search for download locations at
If the rpmfind server is unavailable, you can
download them from the Tcl Developer Xchange
Create a new installation directory on your system, e.g.,
Download the gzipped version of
into the installation directory you created earlier.
Decompress and untar the file after downloading it:
tar -zxvf tk150-1.3.tar.gz
This will create a new subdirectory, named tk150.1.3
and place the files there.
Define and export tk150, a new environment variable
to point to the installation subdirectory just created.
To make the change permanent, you must add the two
lines above to your shell's profile, e.g.,
if you use the bash shell.
Remove the .tk150rc configuration file
if you have one from a previous installation.
To ensure the tk150 environment variable is
made known within X Windows, you should logout, login
again, then restart your graphical
user interface before using tk150 for the first time.
Make sure your serial port has both read
and write permissions for the user who will
run the program.
For example, I use /dev/ttyS1
as the serial port to connect the radio.
If I type in a console window:
ls -l /dev/ttyS1
the output shows the permissions:
crw-rw-rw- 1 root uucp 4, 65 Aug 15 06:40 /dev/ttyS1
Notice that /dev/ttyS1 is readable and writeable
by everyone (user, group, and others).
Login as root or run the
su program to assume root privileges.
Then, change the permissions and exit.
chmod ugo+rw /dev/ttyS1
windowing shell is in your PATH.
Be sure to read a memory image from your radio and save
it in a template (.t15) file as a backup before making any changes.