[ct-user] Using CT946win.007

[Richard L. King]

Here are some of my observations of using CT946WIN.007 during the CQWW DX
CW Contest.

Setup:

Dell PIII - 450 Mhz computer running Windows/98 second edition.
IC765 radio on COM1 (only built-in com port).
TNC connection to PacketCluster on COM3 (using a usb com port).

1. Most functions worked very well. It would have been nice if we could
have run VGA mode and/or been able to move the windows within CT around.

2. Mouse support doesn't work with windows version.

3. Using the "+" key to send F3 and enter a QSO causes the first character
in F3 memory to be clipped. This was so bad that I started pushing F3 first
and then the enter key when the sending was complete. Enter would usually
foul up the CW being sent.

4. CW Speed window would hide and not be restored with ALT-R. My
work-around was to hit ATL-V (set CW speed) and then ESC. This would put
the CW Speed window back on top of everything.

5. Major intermittant problem with point-and-shoot. I was grabbing a spot
from the spots window using CTL-RIGHTARROW followed by ENTER. Sometimes
(about one time in 30/40 times) after hitting ENTER the call would be put
in the callsign field, but the arrow indicator would remain in the packet
spot window. When this happens, the keyboard was locked up. Oddly, the
packet window would continue to receive packet spots. I would have to close
the CT application to particially recover from this failure..

Once when this happened I noticed the message,

	Runtime error R6025
	- pure virtual function call

When I restarted CT after the above problem, it seemed to work except for
the CW memories. I could no longer send CW using any of the function keys.
To recover from this required me to restart WINDOWS/98. This was a solid
occurance after the CT hang problem on CTL-RIGHTARROW. Eventually, I
started restarting Windows/98 as soon as I had CT hang up with this problem.

I suspect that this failure was the result of some timing. Maybe timing
with the radio polling or something when I would try to grab the spot.

6. SAVELOG has some weird problems. When I started testing it, my first
diskette ended up being unreadable (even the directory info) immediately
after trying. It was a confirmed good diskette before the SAVELOG was
attempted. 

Another diskette was tried and CT would usually hang when I entered
SAVELOG, but once in a while it would appear to work (no hang). I am not
sure if the saved file was actually usable since I never tried to use it
afterwards. I was afraid to use the SAVELOG feature during the contest.
Immediately after the contest I tried it, and I couldn't get a good bin
file on the A: drive diskette.

That's all I can remember now about the weekend.

73, Richard
k5na@texas.net

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