Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Pet\s+Peeve\s+\#\s+2\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Pet\s+Peeve\s+\#\s+2\s*$/: 14 ]

Total 14 documents matching your query.

1. [RTTY] Pet Peeve # 2 (score: 1): Author: W0YR@aol.com; Date: Mon, 18 Oct 2004 09:38:47 EDT; Jerry, I've experienced the same thing -- answering CQers and they disappear. I think it's due either to QSB or someone we can't hear who's moved in near to the frequency or who is tuning up on or cl; /archives//html/RTTY/2004-10/msg00197.html (6,757 bytes)
2. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: Kok Chen <chen@mac.com>; Date: Mon, 18 Oct 2004 06:57:29 -0700; On Oct 18, 2004, at 6:38 AM, W0YR@aol.com wrote: I've experienced the same thing -- answering CQers and they disappear. I think it's due either to QSB or someone we can't hear who's moved in near to; /archives//html/RTTY/2004-10/msg00199.html (7,597 bytes)
3. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: "Shelby Summerville" <k4ww@arrl.net>; Date: Mon, 18 Oct 2004 10:43:38 -0400; <W0YR@aol.com> wrote: "Maybe I've missed it. Is there some RTTY operating guide" Once upon a time, in a land far away, such a "guide" was posted! In collaboration with several others, I wrote a "RTTY; /archives//html/RTTY/2004-10/msg00205.html (8,543 bytes)
4. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: Bill Turner <dezrat1242@ispwest.com>; Date: Mon, 18 Oct 2004 07:51:04 -0700; _________________________________________________________ Amen, brother. Send your exchange first, last, in the middle, whatever. I'll get it, and if I don't, I have buffers asking for repeats. Works; /archives//html/RTTY/2004-10/msg00208.html (7,419 bytes)
5. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: "FireBrick" <w9ol@billnjudy.com>; Date: Mon, 18 Oct 2004 10:11:32 -0500; Amen, brother. Send your exchange first, last, in the middle, whatever. I'll get it, and if I don't, I have buffers asking for repeats. Works for me. Eventually the newbies figure out what works best; /archives//html/RTTY/2004-10/msg00209.html (8,738 bytes)
6. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: Bill Turner <dezrat1242@ispwest.com>; Date: Mon, 18 Oct 2004 08:29:43 -0700; Very important. New guys, listen up! Also very important. Using the hyphen in your exchange destroys the working of UnShift On Space (USOS) and will cause many requests for repeats when conditions ar; /archives//html/RTTY/2004-10/msg00211.html (8,596 bytes)
7. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: Jim Reisert AD1C <jjreisert@alum.mit.edu>; Date: Mon, 18 Oct 2004 09:12:51 -0700 (PDT); Wouldn't this give you the best of both worlds: W9OL 599-61 61 DE W6WRT 73 - Jim AD1C == Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <jjreisert@alum.mit.edu>,; /archives//html/RTTY/2004-10/msg00218.html (8,498 bytes)
8. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: Jerry Flanders <jeflanders@comcast.net>; Date: Mon, 18 Oct 2004 17:35:27 +0000; I start all my buffers with a space. No <CR> anywhere in any of my buffers. I wish everyone did it this way. Reason: Your second point below - getting case synchronization with the USOS function. Why; /archives//html/RTTY/2004-10/msg00220.html (9,975 bytes)
9. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: W0YR@aol.com; Date: Mon, 18 Oct 2004 15:03:00 EDT; Which is easier to read? S78WXXKW4UK or S78WXXK W4UK ? NOT USING <CR> at the beginning and end of EVERY macro is a big mistake. If you want your call to stand out from the endless lines of garbage an; /archives//html/RTTY/2004-10/msg00228.html (8,178 bytes)
10. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: Jerry Flanders <jeflanders@comcast.net>; Date: Mon, 18 Oct 2004 19:18:32 +0000; A separator is definitely wanted, which is why I said I wish all would start their buffers with a space, which accomplishes the USOS thingie in addition to separating it from the preceding garbage. S; /archives//html/RTTY/2004-10/msg00230.html (8,629 bytes)
11. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: W0YR@aol.com; Date: Mon, 18 Oct 2004 15:44:51 EDT; NO, that's not necessarily the case. In a weak signal situation a space is often decoded as an "A". Look on your screen when someone is sending 599 56 599 56 and you will see it variously as: TOOATYA; /archives//html/RTTY/2004-10/msg00237.html (7,911 bytes)
12. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: Jerry Flanders <jeflanders@comcast.net>; Date: Mon, 18 Oct 2004 20:54:41 +0000; Hi, Mike The space character 00100 could actually be decoded in several different ways if a single bit were corrupted. But the "A" character is 00011. It would take 3 corrupted bits for one to print; /archives//html/RTTY/2004-10/msg00241.html (10,152 bytes)
13. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: "Tom Osborne" <w7why@charter.net>; Date: Mon, 18 Oct 2004 17:39:12 -0700; W0YR wrote (among other things): Right on--at the beginning of each buffer and also at the end! Even a couple of <CR> at the end of each buffer don't hurt. Hey, we ain't wasting paper here :-) Tom W7; /archives//html/RTTY/2004-10/msg00251.html (8,211 bytes)
14. Re: [RTTY] Pet Peeve # 2 (score: 1): Author: Bill Turner <dezrat1242@ispwest.com>; Date: Mon, 18 Oct 2004 20:41:39 -0700; _________________________________________________________ Nope. The hyphen defeats USOS and that's not good. If the first FIGS shift is lost and the second 61 is garbled, you are dead in the water. W; /archives//html/RTTY/2004-10/msg00259.html (9,052 bytes)

Current List: 1 - 14
Page: [1]