CT Ver 8

Howard Hoyt k4pql at vnet.ibm.com
Mon Jun 15 15:23:54 EDT 1992

The following came in on IBM Contest Forum (via K5NA) and I thought
it might be of interest:

----- CONTEST FORUM appended at 17:28:47 on 92/06/15 GMT (by K5NA at KGNVMA) --
Subject: CT level 8.05

June 15, 1992

I am appending the README and RELEASE8.TXT files from the CT 8 package
here so you can see some of the changes and features for CT level 8.05.

WARNING - This is a long append.

                          Richard King (K5NA)
                          Kingston, NY
                          K5NA AT KGNVMA
README (file)

   CTPAK.EXE (or CTPAK1,2,3 if you got the 360K low density disks)
contains all of the files necessary to run CT. Make a backup copy
of the diskette(s)!  If necessary, make a directory to hold
the CT files.  Copy the files fromn the distribution disk(s) to the CT
directory. Unpack the archive by typing CTPAK (CTPAK1, CTPAK2, CTPAK3).

If in doubt, consult your manual page 6.


   Page 15 of the manual is incorrect regarding memory usage by CT.
CT86.EXE uses EXPANDED memory, not EXTENDED memory, as the manual
says. However, CT286.EXE and CT386.EXE use EXTENDED memory and
ignore EXPANDED memory.

   If your computer is a 286, 386 or 486 and has more than one meg of
memory, CT286 or CT386 are usable.  However, at least 1/2 meg of
extended or XMS memory must be available to CT.  Either disable the
expanded memory manager or set it up to leave some extended or XMS
memory for CT.

  Most of the 386 based expanded memory managers provide either
expanded memory or extended memory on demand. These include EMM386
(comes with DOS5), QEMM386 and MAX386. CT86, CT286, CT386 should all
find what they need if one these memory managers are running.

   Many 286 (AT) class machines have hardware on the motherboard
which converts extended memory into expanded memory. Usually there
are switches which must be set and an EMM driver which must be loaded
in config.sys. In that case, reconfigure the machine to extended
memory for CT286 and expanded memory for CT86. CT386 does not run on
AT class machines.

	8086 (XT) class machines must run CT86 and may not run CT286 or
CT386. If your XT machine has an expanded memory board and driver,
then CT will use expanded memory allowing more QSO's.

   The most common reason CT286 or CT386 won't run is that some other
program has grabbed all the extended memory before CT runs. Usually
this program is a disk cache program such as SMARTDRV or SUPERPCK, or
a disk compression program such as STACKER.  Tell SUPERPCK to leave
memory for other programs by using the /R: switch. /R:512 means
"leave 512K for other programs."  Tell SMARTDRV how much memory it
may use by giving SMARTDRV a size parameter.  For example, if your
computer has 1.5 meg of extended memory, give SMARTDRV 1 meg by
adding the number 1024 to the SMARTDRV line in config.sys. This leaves
1/2 meg for CT.

	Another user of extended memory is a ram disk. The DOS5 ram disk
(RAMDRIVE.SYS) has a size parameter, just like SMARTDRV. A typical
RAMDRIVE line is:

device=c:\dos\ramdrive.sys 1024 /e

This means "setup a ram disk using 1024K of extended memory."
Be sure to leave enough memory for CT.

The file CT.CFG is shipped renamed to EXAMPLE.CFG. When CT loads, it
looks for the file CT.CFG. If the file is found, CT uses the info in
that file to fill in the information sheet. If you choose to use this
feature, rename the file to CT.CFG and fill the information in with
YOUR particulars. See Page 34 in the manual for more info.

GL es CU in the pileups. - K1EA
                           Release 8 Revision History

Beta Testers

A special thanks to KM9P, N3RD, N3RS, K5ZD, K1TR, KR1R for testing
the code. They found plenty, so we will continue to test all year.

Note To Users

This year the format of the .BIN file has changed. Accordingly, we
have provided a new tool, 7TO8.EXE, which converts old logs to the
new format.

Known bugs

1. CT386 (not CT286 or CT86) using CW and COMTSR, CW gets chopped up
on occasion.

2. WAE QTC form: F10 (send a particular QTC line) doesn't work.

3. All the usual tools: R2B.EXE, B2R.EXE, QSL.EXE, MERGE.EXE,
FIXMINE.EXE not ready for release. All registered users of Version 8
will receive an update in the mail.

4. CT386 or CT286: If SAVELOG or AUTOSAVE fail (the floppy frive door is
open), the program crashes. I am working with our compiler company
(Zortech) on this one.  Regular CT works OK.


1. The new command line switch -NF (no freqs) prevents a station from
passing frequency info around the network.  This is for packet based
multi operations. Tnx KM9P

Revision History


* In CQWW and AA: An unknown country prefix could cause a crash when
changed to a good country. Fixed in 8.01.

* The extended keyboard arrow keys didn't work. Fixed in 8.01.


* IARU HF Championship: zones are restricted to the range 1 - 90

* CT.CFG now fixed. New entry in CT.CFG:
  Voice Keyer: DVP

* DRSI tnc's now work again

* The syntax for a TNC in CT.CFG has changed. LOCAL and REMOTE are no longer
  used. Three typical examples are:

TNC:           COM2, 4800
TNC:           DRSI
TNC:           REMOTE


* A full F6 could overrun F7 message

* CT.CFG station number always came up one higher than specified

* New command line switch: -NC (no comm). NC tells CT to use no comm
lines.  This is useful when looking at logs after the contest on
another computer without radios and tnc's. (tnx W6GO)


* Improved control of TS950

More information about the CQ-Contest mailing list