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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+10\s+GHz\s+spots\s*$/: 3 ]

Total 3 documents matching your query.

1. [TRLog] 10 GHz spots (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 2 Oct 1999 14:54:30 -0000; Spots for > 2 GHz will be ignored in 6.45. This should prevent the Runtime 107 error. Tree -- FAQ on WWW: http://www.contesting.com/trlogfaq.html Submissions: trlog@contesting.com Administrative requ; /archives//html/TRLog/1999-10/msg00005.html (6,441 bytes)
2. [TRLog] 10 GHz spots (score: 1): Author: dl2zav@online.de (Udo Lautenbach DL2ZAV); Date: Thu, 30 Sep 1999 23:19:16 +0200; FYI: clx cluster software allows spots that look like 10368100.0 OK2BLE I have filtered those spots out, but there is no filter for the sh/dx command. When such a spot is listed with sh/dx, TR always; /archives//html/TRLog/1999-09/msg00118.html (6,637 bytes)
3. [TRLog] 10 GHz spots (score: 1): Author: ua9cdc@dialup.mplik.ru (Igor Sokolov); Date: Fri, 1 Oct 1999 03:42:14 +0600; I think that is known problem. Been mentioned by Tree before. Igor, UA9CDC --Èñõîäíîå ñîîáùåíè&; /archives//html/TRLog/1999-09/msg00119.html (7,861 bytes)

Current List: 1 - 3
Page: [1]