[Trlog] RST in Exchange Interacts with County List

[Paul Kirley]

For both the Florida and New England QSO Parties, the exchange is RS(T) and county abbreviation.  

Normally TRLog will assume that the received RST is 59(9) unless told otherwise.  Based on the setting of WAIT FOR STRENGTH, TRLog will either pause for transmitted strength or send 59(9) if not previously told otherwise.

During the Florida party I took the lazy approach with WAIT FOR STRENGTH = FALSE and did not bother to type received 599 (I used CW only).  This caused no problems.

While logging imaginary QSOs made with a code practice oscillator instead of a transceiver, I have found that TRLog will lock up during the New England party if that lazy approach is taken.  Once TRLog is forced either to wait for transmitted strength or is asked to fill in received 599, further logging is not possible unless received RST and QTH are both entered in that order.  Subsequently entering only received QTH will lock up TRLog.

Because this problem did not occur with the shorter Florida county abbreviations, I suspect that the 5-character New England county abbreviations are causing it.  It appears that the problem can be avoided if full received exchanges are always entered, which provides a work-around.

My experiments included both CONTEST = NEW ENGLAND QSO and CONTEST = CAL QSO PARTY.  (I use the latter for events that require or prefer Cabrillo submissions, editing the POST result with MS Word or Excel into final form.)  The problem described above occurred with both CONTEST specifications, which leads me to suspect the length of the DOM multiplier abbreviations.

73, Paul W8TM

P.S.:  There are errors in the supplied neqso.dom.  The abbreviation WinVT occurs twice and both are incorrect.