Tnx Tree,
phew! I just turned the radio interface off and sure enough, *ping* all q's
came through fine. I can't find any consistency with the read, sometimes
it's the call immediately following the bandchange, sometimes it's a few
calls away.
I'm using a TS-940.
-----Original Message-----
From: n6tr@teleport.com <n6tr@teleport.com>
To: joe.carvalho@mci.com <joe.carvalho@mci.com>; trlog@contesting.com
<trlog@contesting.com>
Date: Tuesday, March 09, 1999 3:36 PM
Subject: Re: [TRLog] TR read logfile problems. DUPES!!!
>> Had the system crash a few times during the DX contest last weekend. =
>> While I was letting my temper kewl down, I thought I'd play around with =
>> some of tr's features.
>> Scenario follows:
>> mv log.dat kr6na.dat
>> rm *.bin *.tmp
>> dvptsr
>> tr read kr6na.dat
>>
>> radio was on and computer interface was enabled.
>> dupes dupes and more dupes.
>> I don't usually dupe. I make every attempt to keep from annoying the op =
>> at the other end, as well as wasting my time during a pileup.
>> Why does tr decide to randomly move a contact from 10m to 15m or 20m?
>> The original log showed no(0) dupes, reread it showed a few dupes.
>
>The only thing I can think of is that the radio interface is causing
>this. Turn off the radio when doing TR READ.
>
>> Aside from doing a search on a call. Is it possible, when I'm called and
=
>> tell the op at the other end that they're a dupe to have their previous =
>> band-contact info pop up somewhere on the screen? I take the time to =
>> give the op the info, but it does take a few seconds to search and bring
=
>> up the contact info. My feeling is if I show them as a dupe and they =
>> don't show me, it's a bad call for both of us, no?
>
>There is a Control-J flag to do this. Something like AUTO DISPLAY DUPE
>ENABLE.
>
>Tree
--
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
|