Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+CQ\s+was\s+logged\s+as\s+QSO\s*$/: 3 ]

Total 3 documents matching your query.

1. [TRLog] CQ was logged as QSO (score: 1)
Author: je1cka@nal.go.jp (Tack Kumagai)
Date: Thu, 28 Nov 2002 16:23:53 +0900
In the following situation TR logged CQ as a QSO with "CT" Rig control and band map was enabled. TRlog version =6.70 when I push F1 or C/R, CQ message was sent and "CQ/## 21025.3" was displayed on th
/archives//html/TRLog/2002-11/msg00156.html (6,936 bytes)

2. [TRLog] CQ was logged as QSO (score: 1)
Author: n2mg@eham.net (Mike Gilmer, N2MG)
Date: Thu, 28 Nov 2002 07:39:14 -0500
Having done exactly what you did: I CQed for a while, bandmap shows CQ/##, then I tuned off the frequency, then back to the CQ freq. The "CQ/##" gets loaded in the log. I had to delete it, or I very
/archives//html/TRLog/2002-11/msg00158.html (7,393 bytes)

3. [TRLog] CQ was logged as QSO (score: 1)
Author: vr2bg@harts.org.hk (VR2BrettGraham)
Date: Thu, 28 Nov 2002 23:18:28 +0000
JE1CKA reported: When S&Ping, the CQ/##s in bandmap would appear in call window as I tuned across my previous run frequencies. Using 6.71B. Luckily, didn't inadvertently log such a call. 73, VR2Brett
/archives//html/TRLog/2002-11/msg00159.html (7,273 bytes)


This search system is powered by Namazu