Jim et al,
I had a terrible time getting TR to function properly in the MNQP.
Well, I started out entering a call with a slash and two letter county
abbreviation. Apparently TR assumes a /two letter suffix is a DX station.
Sometimes TR would accept the county and log it properly, sometimes not.
Then I tried using a three letter abbreviation. Same deal.
Then I remembered a note I wrote to myself last year: MINNESOTA QSO PARTY:
Use "Call/R/County" or else counties will not be counted properly.
I tried using /R/two letters like my note said but had problems with the
band map inserting garbage characters or spaces in the call window and
sometimes not logging the county properly.
After much frustration, I just entered a two letter abbreviation and logged
the QSO. Then went to the editable window and added the county and mult if
it was a new one. As Jim mentioned, at those rates it wasn't too much of a
problem. I don't have these problems with the Michigan, California or
Florida QSO parties, just with MN.
Try it yourself... enter a call/SL (for St. Louis county). Or call/STL (the
call/three letter abbreviation works for other states' parties).
Using the latest version.
73,
Tom N2CU <><
|