[ct-user] CT9.34 Beta

Ken Wolff Ken Wolff <kwolff@ultranet.com>
Sat, 20 Dec 1997 19:29:54 -0500

I have placed a CT9.34 beta version in:


The readme follows:

9.34 Beta

* Fixed the multiop bug that moves the cursor to the beginning of the
call when someone else modifies a QSO. The DX'peditions and other
multi-ops have been suffering with this for years.

* moved the default bandmap to the right

* CT now self-registers. REGISTER.EXE is no longer needed.

* Fixed Ctrl-L bug where a qso marked as a non-qso was still checked for dupe
purposes. (tnx ZL2BSJ)

* The internal storage representation of time has been adjusted by
seven hours to match ANSI standard time functions. On startup, if CT
finds a log using the old standard, it adjusts each qso and re-writes
the log. This takes a few seconds. 

* If you export your logs to other programs, and the export program
uses the old CT format, either use FIX_TIME to adjust the time, or
ask the publisher of the target program to contact me for details. I
have created a new B2R9 which understands the new time format.

* The new time scheme fixes the two hour error in the M/S QSY meter
and the two hour offset in the ARRL CALL.LOG file. (tnx K2QMF)

* The new time scheme fixes the sked function (ALt-E) (tnx N1BB)

* CT assumes your computer is set to UTC. If you wish to leave it on
local time, set the TZ evironment variable. For example:

SET TZ=EST5          // eastern standard time 5 hours behind
SET TZ=PDT7          // pacific daylight time 7 hours behind
SET TZ=CEU-2         // european central time 2 hours ahead
SET TZ NST3:30       // newfoundland std time 3 hours 30 minutes behind

The first three letters of TZ spec don't mean anything, but the time
offset does. For example,

SET TZ=XYZ-6:27      // tells CT to assume you are 6 hours, 27 minutes 
                     // ahead of UTC

CT will automatically compute UTC based on the TZ variable. CT won't
compensate for daylight savings, avoiding the sudden change in time
during CQWW SSB.

----- Items Reported, but not confirmed or corrected ------

Please send me e-mail if you have observed or can reproduce these problems

* Band data on LPT1 incorrect (PA3AAV)
* Radio control pin disabled  (PA3AAV)
* The first character sent after the '+' key is too long (N1BB)
* The sked function ist kaput (N1BB)
* FT840 not supported (KE6YNR)
* Need a way to pull calls from bandmap (NA2NA)
* CT1BOH would like a the rate box to report points for last 10 and 100 qso's
* NOWORKDUPE does not surpress F4, as the manual says it should (W5UN)
* Radio control pin should be moved to Pin 14 match TR6.15 (W6NL)
* Need a scratchpad for backcopy of multiple calls in a pileup (W6NL)
* Time sync from station 1 is broken (N3RD)
* Colorsave does not work (NN5T)
* CQWW wants a single log for M/S, not two logs as in the paper days (W0TM)
* K3WW wants to send from the paddle and have weight control
* Ve3SS has requested the Canada Day and Canada Winter Contests
* K3MM would like CT track the FT1000MP mode in muti-mode contests
* The breakdown sheet is screwed up during the first two hours (K2QMF)

Submissions:              ct-user@contesting.com
Administrative requests:  ct-user-REQUEST@contesting.com
WWW:                      http://www.contesting.com/ct/
Questions:                owner-ct-user@contesting.com