The behavior you describe with additional "F" keys confusing the PK232
and/or Writelog is consistent with what I have observed for *some* TNC's
running RTTY on Writelog. But not all TNC's.
With the SCS PTC-II (on RTTY), you can hit multiple "F" keys and everything
works fine.
With the DXP38, a second "F" key before the first message is finished
results in truncation of the first message, the second not being properly
sent, and frequently a requirement to reset the interface.
Using CW on the serial port (rather than the TNC) you can hit multiple "F"
keys just fine. In fact, I operated the DX CW weekend without the need to
restart Writelog at all and with zero CW problems running CW from the serial
port. Version was 10.24.
73,
Mike WA0SXV
----- Original Message -----
From: "Les Kalmus" <w2lk@arrl.net>
To: <writelog@contesting.com>
Sent: Tuesday, February 20, 2001 07:38
Subject: [WriteLog] WL operating problems
>
> The software generally worked OK except that I could not hit 2 F-keys in
> succession when searching and pouncing. The second key is not sent and I
> had the same unsent message problem as I will describe for running. I had
> other problems like duped seq. numbers which were reported by others.
>
> ...
> I found that hitting an F key before a previous F key press completed,
i.e.
> to send my call twice could only be done by waiting for the first press to
> finish sending. Not waiting resulted in nothing sent the second time, BUT
> pressing a different F key, i.e. to send the exchange, resulted in the
> unsent call being sent. I found in the heat of battle that WL consistently
> left unsent F key data in a buffer somewhere and would then send it when a
> different F key was pressed later on.
>
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|