TRLog
[Top] [All Lists]

[TRLog] Can't abort CW immediately w/ Esc

Subject: [TRLog] Can't abort CW immediately w/ Esc
From: k4ro@k4ro.net (K4RO Kirk Pickering)
Date: Tue, 12 Jan 1999 10:35:26 -0600 (CST)
> 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?  

Hardware is still the same old AMD "586" (133MHz 486) under DOS 95.

-Kirk  K4RO
 


--
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


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