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*$/: 11 ]

Total 11 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/RTTY/2014-01/msg00116.html (7,951 bytes)
2. Re: [RTTY] Cut Numbers Revisited (score: 1): Author: "Joe Subich, W4TV" <lists@subich.com>; Date: Tue, 07 Jan 2014 16:34:43 -0500; I had one station in Ohio (I won't give his call) that was sending a Those weren't CUT NUMBERS - your decoder was in the wrong LTRS/FIGS shift. Check the top two rows of the keyboard to see the relat; /archives//html/RTTY/2014-01/msg00121.html (9,565 bytes)
3. 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/RTTY/2014-01/msg00131.html (8,189 bytes)
4. 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/RTTY/2014-01/msg00140.html (9,344 bytes)
5. Re: [RTTY] Cut Numbers Revisited (score: 1): Author: "WW3S" <ww3s@zoominternet.net>; Date: Tue, 7 Jan 2014 18:19:07 -0500; _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists.contesting.com/mailman/listinfo/rtty; /archives//html/RTTY/2014-01/msg00147.html (8,906 bytes)
6. 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/RTTY/2014-01/msg00155.html (8,571 bytes)
7. 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/RTTY/2014-01/msg00164.html (10,833 bytes)
8. Re: [RTTY] Cut Numbers Revisited (score: 1): Author: Bill Turner <dezrat1242@wildblue.net>; Date: Tue, 07 Jan 2014 19:37:52 -0800; ORIGINAL MESSAGE: (may be snipped) REPLY: True for both transmitting and receiving. I have noticed when I receive a station with USOS transmit turned off, it is almost invariably a JA. Don't know why; /archives//html/RTTY/2014-01/msg00166.html (8,307 bytes)
9. Re: [RTTY] Cut Numbers Revisited (score: 1): Author: "Rex Maner" <k7qq@netzero.net>; Date: Tue, 07 Jan 2014 23:27:06 -0500; The RTTY message I most dislike is K7QQ DE W6WRT 599004 599004 Or whatever QSO nr. K7qq ORIGINAL MESSAGE: (may be snipped) On Tue, 7 Jan 2014 18:06:39 -0600, Peter wrote: REPLY: True for both transmi; /archives//html/RTTY/2014-01/msg00170.html (9,417 bytes)
10. Re: [RTTY] Cut Numbers Revisited (score: 1): Author: Bill Turner <dezrat1242@wildblue.net>; Date: Tue, 07 Jan 2014 21:54:35 -0800; ORIGINAL MESSAGE: (may be snipped) REPLY: Don't know why Rex used my call in his example, but just for the record, I never use that format. And if you are using N1MM Logger, you can click anywhere in; /archives//html/RTTY/2014-01/msg00174.html (8,487 bytes)
11. Re: [RTTY] Cut Numbers Revisited (score: 1): Author: Salvatore Irato <iw1ayd@gmail.com>; Date: Wed, 8 Jan 2014 12:29:33 +0100; May be that it is a common mistake for, let me say, the exchange field in the log. Where there is the exchange field some peoples enter what is EXCHANGE in the wrong way. So EXCHANGE is RST and seria; /archives//html/RTTY/2014-01/msg00177.html (10,534 bytes)

Current List: 1 - 11
Page: [1]