Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Cut\s+Numbers\s+Revisited\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Cut\s+Numbers\s+Revisited\s*$/: 5 ]

Total 5 documents matching your query.

1. [RTTY] Cut Numbers Revisited (score: 1): Author: "DickT-W0RAA" <dickt@w0raa.com>; Date: Tue, 7 Jan 2014 14:12:53 -0700; I am somewhat mystified why RTTY contesters send TOO for 599 in a RTTY Contest or 5NN. Are they saving anything (characters or time)? I had one station in Ohio (I won't give his call) that was sendin; /archives//html/WriteLog/2014-01/msg00030.html (7,438 bytes)
2. Re: [RTTY] Cut Numbers Revisited (score: 1): Author: Aubrey Mansfield <w7oly@comcast.net>; Date: Tue, 7 Jan 2014 14:22:09 -0800; Receiving TOO instead of 599 is not uncommon. Ive always thought it was because a SHIFT was lost in either transmission or reception. If you look at the International Telegraphy Alphabet No. 2 (Baudo; /archives//html/WriteLog/2014-01/msg00031.html (8,049 bytes)
3. Re: [RTTY] Cut Numbers Revisited (score: 1): Author: Michael Clarson <wv2zow@gmail.com>; Date: Tue, 7 Jan 2014 17:47:55 -0500; I worked this station also, and I was copying TOO 9h. Several times. It was obviously 599 OH, but always came in as TOO 9h. --Mike, WV2ZOW _______________________________________________ RTTY mailing; /archives//html/WriteLog/2014-01/msg00033.html (8,788 bytes)
4. Re: [RTTY] Cut Numbers Revisited (score: 1): Author: Peter Laws <plaws@plaws.net>; Date: Tue, 7 Jan 2014 18:06:39 -0600; It is. The OP needs to make sure he has unshift on space (USOS) turned ON. OR ... you can look at the top row of keys on your keyboard. :-) I know from experience that "FFGIERYWBENCSJKFVHSFI&%^&%SFT7; /archives//html/WriteLog/2014-01/msg00035.html (8,137 bytes)
5. Re: [RTTY] Cut Numbers Revisited (score: 1): Author: "Rex Maner" <k7qq@netzero.net>; Date: Tue, 07 Jan 2014 22:14:56 -0500; I'm not sure I worked this person, however from the comments from numerous Operators about the TOO 9h, I suspect that the calling station had something set incorrectly on the TX end. Rex k7qq I worke; /archives//html/WriteLog/2014-01/msg00036.html (10,307 bytes)

Current List: 1 - 5
Page: [1]