-----Original Message-----
From: K4RO Kirk Pickering [SMTP:k4ro@k4ro.net]
Sent: Tuesday, January 12, 1999 5:35 PM
To: trlog@contesting.com
Subject: [TRLog] Can't abort CW immediately w/ Esc
> Escaping further than necessary happens to me when I start sending the
> unintended or unintendedly. TRlog sends out at least three letters before
> responding to ESC (1000 or more QSOs in the log, 66MHz 486 or 100MHz P5).
> Enough time to hit ESC again. With UPDATE RESTART BIN FILE = TRUE it's
> even worse.
I find the same problem. Hitting Esc does NOT abort the CW immediately,
which causes panic in every CW contest. I'm finally learning that a
single "dit" on the paddles (only if you're using the paddle port) will
abort CW immediately. It seems that Esc used to work immediately, but
does not any more. Is it really a function of log size?
I have also the same problem. And I found this IS function of log size.
No matter what CPU - 486 or MMX.
Martin Huml
OK1FUA, OL5Y in the contests
OL5Y@contesting.com
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|