Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+WAE\s+QTC\s+receiving\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+WAE\s+QTC\s+receiving\s*$/: 4 ]

Total 4 documents matching your query.

1. [TRLog] WAE QTC receiving (score: 1): Author: dl2zav@online.de (Udo Lautenbach DL2ZAV); Date: Wed, 18 Aug 1999 11:25:55 +0200; Von: Paul Hicks, VE3BBH / VE3ZT For me too it was the first real attempt, so I can't speak for more experienced ops. Well, it really is a challenge. I'm not an excellent op anyway, but tried to do my; /archives//html/TRLog/1999-08/msg00074.html (8,741 bytes)
2. [TRLog] WAE QTC receiving (score: 1): Author: ua9cdc@dialup.mplik.ru (Igor Sokolov); Date: Wed, 18 Aug 1999 23:27:02 +0600; to Look at the last year SSB results. UA9XL claimed the multiplier of 722(impossible even with 4000 qso) with only 276 QSO made and no log checker noticed that. In fact I doubt all logs are carefull; /archives//html/TRLog/1999-08/msg00076.html (8,134 bytes)
3. [TRLog] WAE QTC receiving (score: 1): Author: Clive_Whelan@compuserve.com (Clive Whelan); Date: Wed, 18 Aug 1999 18:33:25 -0400; Hi Udo, << Wouldn't it make sense if the software automatically sent QTCs a bit slower than the QSO text? Maybe also simply double spaces between time, call and number could help keep up with full sp; /archives//html/TRLog/1999-08/msg00078.html (8,630 bytes)
4. [TRLog] WAE QTC receiving (score: 1): Author: Clive_Whelan@compuserve.com (Clive Whelan); Date: Fri, 20 Aug 1999 18:45:49 -0400; Udo, Thanks to the SENDCW command, here's how to make a sort of QTC simulator for practice. In POST make an ARRL type log of your WAE log.dat ( or any other with serial numbers), say DL2ZAV.log. Then; /archives//html/TRLog/1999-08/msg00090.html (7,771 bytes)

Current List: 1 - 4
Page: [1]