Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Bad\s+calls\s+identified\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Bad\s+calls\s+identified\s*$/: 4 ]

Total 4 documents matching your query.

1. [WriteLog] Bad calls identified (score: 1): Author: k4jrb@juno.com (Dave L Thompson); Date: Tue, 6 Nov 2001 21:50:17 -0500; Several have asked how to identify bad calls in writelog before log submission as several of the other logging programs do. The best way is to get a copy of the WT4I contest tools....the log checking; /archives//html/WriteLog/2001-11/msg00151.html (7,192 bytes)
2. [WriteLog] Bad calls identified (score: 1): Author: kg0us@swbell.net (dr); Date: Tue, 06 Nov 2001 21:38:01 -0600; I just reviewed our CQWW SSB log and found that my daughter logged DU7MHA and that there is a RED B next to the sequence number. Does this RED B indicate incorrectly entered call information? It has; /archives//html/WriteLog/2001-11/msg00155.html (7,953 bytes)
3. [WriteLog] Bad calls identified (score: 1): Author: Steve Baron - KB3MM" <SteveBaron@starlinx.com (Steve Baron - KB3MM); Date: Wed, 7 Nov 2001 04:55:50 -0000; OOPS!; /archives//html/WriteLog/2001-11/msg00162.html (8,176 bytes)
4. [WriteLog] Bad calls identified (score: 1): Author: kg0us@swbell.net (dr); Date: Wed, 07 Nov 2001 07:46:55 -0600; Tom, You are correct. Writelog logged one contact as FM for some reason and another as a freq of 163028 which was really on 10 meters. Maybe some RF is getting into the computer. I noticed the bandma; /archives//html/WriteLog/2001-11/msg00167.html (9,564 bytes)

Current List: 1 - 4
Page: [1]