Howard Hoyt wrote:
>
> I have had intermittent problems with TR locking up after entering
> certain calls. This usually happens in the heat of battle, altho
> no different this time, I did note the call entered:
> KH8AZ/T
> tr allows me to enter his section but WILL NOT LOG the call. In addition,
> it will not log any future calls until I terminate and restart tr.
> Naturally, the turkey called me again, dropping his /t and it produced
> the same results.
>
> After the contest, I brought up my arrl160 log and tried entering the
> call with the same results.
>
> Can anybody else reproduce this ? I am running 5.93.
>
> 73, Howie N4AF
I wasnt on much for the test but I played around with the program after
seeing your email. If KH8AZ/T is at a doemestic (state) and not on KH8
then TRLog chokes.
1)If KH8AZ/T is on KH8 then enter the siganl report and TRLog will
automatically add the KH8 to the mult line.
2) If KH8AZ/T is really portable (W6, w7, etc) then TRLog will
definitely choke when you try to put in a state rather than KH8. If he
is say in Washington then entering the callas KH8AZ/7/T will allow you
to then enter WA as the state. Personally I think that all contests
should require folks to sign /# so that their callsign matches there QTH
# (flame suit on).
3) Dont confuse the ARRL 160 logging with the ARRL 10 logging. ARRl 160
requires a valid ARRL SECTION or DX (in this case PAC for KH8) while the
ARRL 10 is looking for STATES or DX. Personally I think that KH8 should
count as DX for the 160 Test but since it is in an ARRL section aint so
(flame suit on again).
4) While I do get a lock up of sorts when the QTH doesnt match the
expected call prefix, hitting <ESC> twice should clear everthing without
rebooting.
Dave
N7EX
|