Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+After\s+the\s+tough\s+qso\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+After\s+the\s+tough\s+qso\s*$/: 9 ]

Total 9 documents matching your query.

1. [RTTY] After the tough qso (score: 1): Author: Pierre Fogal <pierre.fogal@gmail.com>; Date: Fri, 16 Feb 2018 13:09:26 -0500; Hi folks, I haven't been doing RTTY contesting all that long, and I have done what I can to read everything you sage folk out there write about exchanges. So, I hope I'm keeping mine succinct enough!; /archives//html/RTTY/2018-02/msg00097.html (7,695 bytes)
2. Re: [RTTY] After the tough qso (score: 1): Author: Jerry Flanders <jeflanders@comcast.net>; Date: Fri, 16 Feb 2018 13:30:26 -0500; If I hear a TU right after I send my exchange, I assume he is qsl'ing me. I don't remember a single time that I got a TU along with a request for a repeat. Jerry W4UK I haven't been doing RTTY contes; /archives//html/RTTY/2018-02/msg00098.html (8,078 bytes)
3. Re: [RTTY] After the tough qso (score: 1): Author: Ed W0YK <ed@w0yk.com>; Date: Fri, 16 Feb 2018 11:57:38 -0800; This is an excellent question, Pierre. I say log it. If he didn't log it, then you will get a NIL. But, if he did log it and you didn't then he gets the NIL. In a 50/50 situation like this, I tak; /archives//html/RTTY/2018-02/msg00100.html (8,339 bytes)
4. Re: [RTTY] After the tough qso (score: 1): Author: Jeff Stai <wk6i.jeff@gmail.com>; Date: Fri, 16 Feb 2018 15:16:05 -0800; What Ed said (I agree with Ed a lot...) I would add that in the case where you really feel you didn't finish - the other guy gave up - just call again. I do see that sometimes and I just resend my TU; /archives//html/RTTY/2018-02/msg00106.html (9,831 bytes)
5. Re: [RTTY] After the tough qso (score: 1): Author: David G3YYD via RTTY <rtty@contesting.com>; Date: Sat, 17 Feb 2018 04:09:57 -0500; Whether I log a potentially incorrect QSO or not depends on the contest scoring system. If there are no penalties for busted calls, incorrect SR and so forth then I will log it. But if there are pena; /archives//html/RTTY/2018-02/msg00107.html (9,912 bytes)
6. Re: [RTTY] After the tough qso (score: 1): Author: Ed W0YK <ed@w0yk.com>; Date: Sat, 17 Feb 2018 03:40:37 -0800; This is an excellent suggestion (X-QSO). It is easy with WriteLog. Just log the QSO and when convenient, right-click it in the log. Select 'Mark QSO as unclaimed' and it becomes an X-QSO line in t; /archives//html/RTTY/2018-02/msg00108.html (10,673 bytes)
7. Re: [RTTY] After the tough qso (score: 1): Author: Pierre Fogal <pierre.fogal@gmail.com>; Date: Sat, 17 Feb 2018 13:55:06 -0500; Thanks for the continuing education guys! I'm heading for VY0 in the morning, and I should be on with VY0ERC for the NAQP RTTY. Some of you may have worked VE1RUS who is currently on site, as VY0ERC; /archives//html/RTTY/2018-02/msg00113.html (11,336 bytes)
8. Re: [RTTY] After the tough qso (score: 1): Author: "Robert" <woodr90@gmail.com>; Date: Sat, 17 Feb 2018 13:22:35 -0600; X-<anything>: text Lines beginning with X- are ignored by the robot and log checking software. Use this for adding comment lines to your log. Exception: See X-QSO below. X-QSO: qso-data Any QSO mark; /archives//html/RTTY/2018-02/msg00114.html (13,163 bytes)
9. Re: [RTTY] After the tough qso (score: 1): Author: "Ed Muns" <ed@w0yk.com>; Date: Sun, 18 Feb 2018 11:39:08 -0800; Despite the quoted definition below of the X-QSO: Cabrillo tag, it is not "ignored". In fact, the whole point of X-QSO: is that the QSO is cross-checked with the log of the QSO partner. But the X-QSO; /archives//html/RTTY/2018-02/msg00116.html (14,546 bytes)

Current List: 1 - 9
Page: [1]