CT-User
[Top] [All Lists]

[ct-user] CT 9.85 available for testing

To: <ct-user@contesting.com>
Subject: [ct-user] CT 9.85 available for testing
From: jjreisert@alum.mit.edu (Jim Reisert AD1C)
Date: Mon, 20 Jan 2003 15:37:48 -0800 (PST)
CT 9.85 is now available from the CT Vault:

  http://www.k1ea.com/ctvault/

Here are Ken's release notes.  It's imperative that EVERYONE check their radios
with this new version. Ken has done a TON of work in this area. For example,
ICOM radios now set and unset split correctly, AS LONG AS YOU ONLY USE CT to
change the split status (using the "-" key), i.e. keep your fingers off the
radio's SPLIT button.  Also, if anyone has a FT-847 please test it - it might
work now.

Don't wait until the day before ARRL DX to test this version out!

73 - Jim AD1C

9.85

* A lot of testing was done with K1TTT and K1EP with regard to testing
  mode and radio issues.

* Thanks to a loan from W1JR, the FT817 is online.

* All the flovaors of multimode contests should be stable with respect
  to changing mode issues. When changing bands, the radio should return
  to the last mode used.

* There are some things to be aware of when using radio control

    1. If you toggle ALT F4 too quickly, IE the radio doesn't get
       completely switched before trying to switch back, you can lose
       your run frequency. We all HATE that. In time I hope to have a
       completely secure method worked out.

    2. If you toggle to a spot in a multi-mode contest CT will not 
       automatically set the mode for you. You need to set it yourself. 
       Unfortunately when you ALT-F4 to your run frequency and ALT-F4
       back to the spot you will have to set the mode again. I
       anticipate fixing this in the near future.

    3. I don't have access to most of the radios on the supported list,
       so you will have to try as many contest/category/modes as possible
       and give me good feedback before all is solid.

    4. I have been getting random "radio timeout" messages with the MP,
       but it doesn't seem to affect operation at all.


<Prev in Thread] Current Thread [Next in Thread>