Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+RTTY\]\s+Simple\s+thing\s+that\s+seemed\s+to\s+improve\s+my\s+S\&Ping\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+RTTY\]\s+Simple\s+thing\s+that\s+seemed\s+to\s+improve\s+my\s+S\&Ping\s*$/: 2 ]

Total 2 documents matching your query.

1. [RTTY] RTTY] Simple thing that seemed to improve my S&Ping (score: 1): Author: Salvatore Irato <iw1ayd@gmail.com>; Date: Tue, 16 Feb 2016 11:11:40 +0100; Yes Jim, you right but there are alternative(s), isn't? First of all anyone have to change the way as to send out back his call more times depending when, in a QSO, we get the clue that the other end; /archives//html/RTTY/2016-02/msg00119.html (13,102 bytes)
2. Re: [RTTY] RTTY] Simple thing that seemed to improve my S&Ping (score: 1): Author: Al Kozakiewicz <akozak@hourglass.com>; Date: Tue, 16 Feb 2016 13:36:22 +0000; The wise thing to do when in S&P is not to send your exchange until you're confident the runner has your call correct. Send your call 2/3 times (whatever your standard call reply is) until you see yo; /archives//html/RTTY/2016-02/msg00120.html (14,768 bytes)

Current List: 1 - 2
Page: [1]