>> > It would really help if the q # could be assigned just when the q is
>> > logged, rather than the way it currently is...
This could be done with CQWW but not with contests where
the QSO # is part of the exchange.
>> > 3. There was also a significant delay in the call window being cleared
>> > after the enter key is pressed to log the q, this is really annoying
>> > when the rates are up around 200/min.
Same here with two 60MHz 486/~200MB computers. 133MHz Pentiums with newer disks
worked fine. I am fairly sure
smartdrv was properly up on all.
>> > 4. Apparently in cw, if the start sending now key is pressed, and
>> > one backspaces to correct the end of the call before it is sent, the
>> > program sends the call as originally typed, not as corrected...
>> > while this is not a big issue for me, and my sending style, it is
>> > a really big issue for them, and I don't need any more reasons for
>> > them not to like the program...
I don't use the start sending now key. When sending is started by AUTO SEND
CHARACTER COUNT/AUTO CALL TERMINATE
then TRLog will send the correct call. It is even smart enough to correct an
erroneous letter if it catches you red-handed.
The start sending key was probably invented to let CT-addicts stick to their
bad habits :-) I suggest you twist
hands to exercise the AUTO features BEFORE the contest.
>Sounds like you have something else competing for
>> the CPU and there are not enough horses left to get the updated callsign
>> reflected in the output buffer.
I have recently found a windows thing named IFSHLP to spoil
CW timing. Win98 won't run without it, and it is hard to get rid of. Where is
the beast started?
Takes me an hour to kill Windoze and a week to put every-thing back on all my
friends' computers :-)
--
Juhan ES5QX
|