I normally do a SETTIME and SETDATE in call field when first
launching CT program before a contest starts.
In getting set up for IARU this past weekend,
I noticed that I had to enter some oddball time in the TIME window
to get the program to get the correct UTC time to indicate.
Then, sometime during contest, CT Ver 10.08 crashed when entering a callsign
I had a batch file set up which the Operator on duty typed and
away we went, back into the program.....except he didn't notice
that the TIME reset itself to the WRONG time!
The on duty Op never caught it and at 45 minutes before contest ended
I just happened to catch it...too late,many QSOs logged at wrong time and it
was some odd ball ammount, not an even hour!!!
Never had this problem happen with any previous version of CT
Anyone get nailed with this one?
I'l be pinging on some of you guys that worked us to try to
ressurect the log.....&@$%$^%%^%$$%#$#@Y&*( !!!!
Violated my first rule I teach all newbie contestors
I train at N6KI...NEVER NEVER run a new version specifically fixed
for a particular contest..ugghhhh
73, Dennis N6KI
Anyone else
Anyone else experience
________________________________________________________________
The best thing to hit the Internet in years - Juno SpeedBand!
Surf the Web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!
_______________________________________________
CT-User mailing list
CT-User@contesting.com
http://lists.contesting.com/mailman/listinfo/ct-user
CT on the web: http://www.k1ea.com/
|