Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Summary\s+for\s+Points\s+re\-calculation\s*$/: 3 ]

Total 3 documents matching your query.

1. [TRLog] Summary for Points re-calculation (score: 1)
Author: je1cka@nal.go.jp (Tack Kumagai)
Date: Fri, 4 Jun 1999 14:21:10 +0900
Thanks George & Tree I suggested this to the guy and I did for myself. Here is the summary how to REWORK(not exactly re-calculate the score) the Log data. 1. Copy the original LogData to another dire
/archives//html/TRLog/1999-06/msg00021.html (8,091 bytes)

2. [TRLog] Summary for Points re-calculation (score: 1)
Author: aa4ga@contesting.com (Lee Hiers)
Date: Fri, 4 Jun 1999 09:13:36 -0400
<SNIP> Rather than CODE SPEED = 99 and/or CW TONE set to zero, if I remember correctly there is a command to stop all code sending...that should make the TR READ work even faster. Watch the rate mete
/archives//html/TRLog/1999-06/msg00022.html (7,767 bytes)

3. [TRLog] Summary for Points re-calculation (score: 1)
Author: n6tr@teleport.com (n6tr@teleport.com)
Date: Fri, 4 Jun 1999 06:35:30 -0700 (PDT)
Setting CW TONE to zero does this. No need to change the speed. Tree -- FAQ on WWW: http://www.contesting.com/trlogfaq.html Submissions: trlog@contesting.com Administrative requests: trlog-REQUEST@c
/archives//html/TRLog/1999-06/msg00023.html (7,011 bytes)


This search system is powered by Namazu