Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Wrong\s+call\s*$/: 7 ]

Total 7 documents matching your query.

1. [TRLog] Wrong call (score: 1)
Author: kg5u@hal-pc.org (Dale L. Martin)
Date: Sun, 5 Sep 1999 12:10:20 -0500
A couple of times during the Sprint contest while in S&P mode, I blew the guys call while typing it in the callsign field. I would immediately update it in the exchange field, then enter the exchange
/archives//html/TRLog/1999-09/msg00010.html (7,469 bytes)

2. [TRLog] Wrong call (score: 1)
Author: n6tr@teleport.com (n6tr@teleport.com)
Date: 5 Sep 1999 17:38:35 -0000
Half of this can be cured by turning CALLSIGN UPDATE ENABLE = TRUE. This will fix your log entry. However, TR will still send the callsign that is in the call window instead of the "correct" call in
/archives//html/TRLog/1999-09/msg00012.html (7,930 bytes)

3. [TRLog] Wrong call (score: 1)
Author: LRod@pobox.com (LRod@pobox.com)
Date: Sun, 5 Sep 1999 18:04:59 +0000
Far be it for me to argue with the software developer, but are you sure about this? I seem to recall one of the charms about TR was the ability to send the corrected call with the exchange when the
/archives//html/TRLog/1999-09/msg00014.html (8,081 bytes)

4. [TRLog] Wrong call (score: 1)
Author: aa4ga@contesting.com (Lee Hiers)
Date: Sun, 5 Sep 1999 14:31:12 -0400
I'm pretty sure I did just this last night. Several times. =:o Or, maybe it was with the callsign window empty, but the call and the exchange in the exchane window. Sprint is alway such a blur... --
/archives//html/TRLog/1999-09/msg00015.html (8,102 bytes)

5. [TRLog] Wrong call (score: 1)
Author: n0ss@earthlink.net (Tom Hammond - N0SS)
Date: Sun, 05 Sep 1999 14:01:08 -0500
Hi Guys: I think it WILL send the updated call IF the call in the call windos has been sent COMPLETELY and attention been allowed to automatically drop to the EXCHANGE window.... seems last time I tr
/archives//html/TRLog/1999-09/msg00016.html (9,381 bytes)

6. [TRLog] Wrong call (score: 1)
Author: n6tr@teleport.com (n6tr@teleport.com)
Date: 5 Sep 1999 23:33:05 -0000
Hmm - you could be right. I kind of remember doing something like that but I couldn't make it work that way. I will do a little more digging. Tree -- FAQ on WWW: http://www.contesting.com/trlogfaq.h
/archives//html/TRLog/1999-09/msg00017.html (7,744 bytes)

7. [TRLog] Wrong call (score: 1)
Author: kg5u@hal-pc.org (Dale L. Martin)
Date: Sun, 5 Sep 1999 23:27:20 -0500
TRUE. call callsign contents Tree, My Callsign Update is set to TRUE. I misstated the problem. I am in S&P mode. I enter the callsign incorrectly in the callsign window. When he comes back with his
/archives//html/TRLog/1999-09/msg00018.html (8,525 bytes)


This search system is powered by Namazu