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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+WPX\s+suggestion\s*$/: 40 ]

Total 40 documents matching your query.

21. Re: [RTTY] WPX suggestion (score: 1): Author: David VE3VID <ve3vid@hotmail.com>; Date: Thu, 7 Feb 2013 21:33:23 -0500; I had my macros set wrong in a contest last year and the obligatory 599 was not sent....no one asked for it :-D VE3VID Located in rural Canada Solar power. Wood heat. Mosley tribander @ 10m Lots of s; /archives//html/RTTY/2013-02/msg00077.html (9,053 bytes)
22. Re: [RTTY] WPX suggestion (score: 1): Author: Claude Du Berger <duberger.miousse81@globetrotter.net>; Date: Thu, 07 Feb 2013 21:33:16 -0500; And the Rules is: VI. Exchange: RST report plus a progressive contact serial number starting with 001 for the first contact. Note: Multi-Two and Multi-Unlimited entrants use separate serial number se; /archives//html/RTTY/2013-02/msg00078.html (9,164 bytes)
23. Re: [RTTY] WPX suggestion (score: 1): Author: "Jamie WW3S" <ww3s@zoominternet.net>; Date: Thu, 7 Feb 2013 21:44:21 -0500; and after you send # 598, just move to 600....eliminates the 599 599 599 and then "yea but whats my number?" And the Rules is: VI. Exchange: RST report plus a progressive contact serial number starti; /archives//html/RTTY/2013-02/msg00079.html (9,629 bytes)
24. Re: [RTTY] WPX suggestion (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Thu, 07 Feb 2013 18:47:17 -0800; REPLY: I used to have a macro that said "RST REQURED BY THE RULES. PLEASE SEND RST." I used it a few times and gave it up. Nobody seemed to care one way or the other. Bill, W6WRT ____________________; /archives//html/RTTY/2013-02/msg00080.html (8,371 bytes)
25. Re: [RTTY] WPX suggestion (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Thu, 07 Feb 2013 19:30:37 -0800; REPLY: You're no fun! One of my favorite things in a contest is explaining that 599 really is the serial number. Strange, I know. :-) Bill, W6WRT _______________________________________________ RTTY; /archives//html/RTTY/2013-02/msg00082.html (8,839 bytes)
26. Re: [RTTY] WPX suggestion (score: 1): Author: "Don Hill AA5AU" <aa5au@bellsouth.net>; Date: Thu, 7 Feb 2013 22:27:13 -0600; I usually send the serial number 599 exchange manually with: 599 AND SERIAL NUMBER ALSO 599 599 73, Don AA5AU and after you send # 598, just move to 600....eliminates the 599 599 599 and then "yea bu; /archives//html/RTTY/2013-02/msg00087.html (10,144 bytes)
27. Re: [RTTY] WPX suggestion (score: 1): Author: Keith Maton <g6nhu@me.com>; Date: Fri, 08 Feb 2013 08:06:12 +0000 (UTC); If you really want to speed things up, throw away the spaces between report and number and in between the numbers and replace them with dashes. 599-123-123-123 Is faster to send than 599 123 123 123; /archives//html/RTTY/2013-02/msg00092.html (10,352 bytes)
28. Re: [RTTY] WPX suggestion (score: 1): Author: Roger Cooke <g3ldi@g3ldi.co.uk>; Date: Fri, 08 Feb 2013 08:36:22 +0000; It's those that WILL send numerous CR and LF at the end of their exchange macro!! Chasing it up the screen is a pain. 73 de Roger, G3LDI On 08/02/2013 00:37, Rick Ellison wrote: I am having a hard ti; /archives//html/RTTY/2013-02/msg00093.html (12,187 bytes)
29. Re: [RTTY] WPX suggestion (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Fri, 08 Feb 2013 04:10:50 -0800; REPLY: If you're using N1MM Logger, there are two things you can do that will almost completely eliminate chasing things up the screen: 2. At the end of all macros except F5, put {END}{CLRRX}. This w; /archives//html/RTTY/2013-02/msg00095.html (9,754 bytes)
30. Re: [RTTY] WPX suggestion (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Fri, 08 Feb 2013 04:19:58 -0800; REPLY: Please, please, please, NO dashes. While it does speed up sending, it interferes with the USOS (Un Shift On Space) function which most folks agree is a much better thing to have. USOS greatly; /archives//html/RTTY/2013-02/msg00096.html (9,179 bytes)
31. Re: [RTTY] WPX suggestion (score: 1): Author: Phil Sussman <psussman@pactor.com>; Date: Fri, 08 Feb 2013 09:38:08 -0500; OK, Master Chen -- I remember reading something that you authored a while ago about (-) dashes and USOS and the best way to structure your set-up. As I recall, perhaps mistakenly, (-) dashes were in; /archives//html/RTTY/2013-02/msg00099.html (10,059 bytes)
32. Re: [RTTY] WPX suggestion (score: 1): Author: Kok Chen <chen@mac.com>; Date: Fri, 08 Feb 2013 08:45:26 -0800; It is another myth that an extra character helps when you are transmitting all numerals. The extra FIGS that follows the Space actually hurt. The reason is this: if the probability of the error of a; /archives//html/RTTY/2013-02/msg00111.html (12,229 bytes)
33. Re: [RTTY] WPX suggestion (score: 1): Author: "John GW4SKA" <ska@bartg.org.uk>; Date: Fri, 08 Feb 2013 11:57:53 -0500; Manually ... you mean typing something on the keyboard? John GW4SKA I usually send the serial number 599 exchange manually with: 599 AND SERIAL NUMBER ALSO 599 599 73, Don AA5AU and after you send #; /archives//html/RTTY/2013-02/msg00113.html (11,343 bytes)
34. Re: [RTTY] WPX suggestion (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Fri, 08 Feb 2013 08:59:52 -0800; REPLY: I disagree. Your example only sends the exchange once. Nearly everyone sends the exchange twice. Using USOS and a space gives two chances to get the print right. Using dashes between two excha; /archives//html/RTTY/2013-02/msg00114.html (10,155 bytes)
35. Re: [RTTY] WPX suggestion (score: 1): Author: "Andreas Rehberg" <arehberg@gmx.de>; Date: Fri, 08 Feb 2013 18:04:42 +0100; only true if the number is sent once only; with 599 123 123 the probability that both USOS characters are hit is just marginal.. I vote for "no dashes"! Andy, DF4WC -- Original-Nachricht -- _________; /archives//html/RTTY/2013-02/msg00115.html (14,093 bytes)
36. Re: [RTTY] WPX suggestion (score: 1): Author: Kok Chen <chen@mac.com>; Date: Fri, 08 Feb 2013 10:22:16 -0800; Someone who knows what "TOO" means should also know how to decode "PPQ" into 001 by sight. And this does not even take into account software which can do the conversion between FIGS and LTRS for you; /archives//html/RTTY/2013-02/msg00119.html (11,010 bytes)
37. Re: [RTTY] WPX suggestion (score: 1): Author: Ktfrog007@aol.com; Date: Fri, 8 Feb 2013 13:40:00 -0500 (EST); What about variations on a theme, like: W1ABC 599-001 001 W1ABC W1ABC 599-001 001-001 W1ABC (used under poor conditions) I've tried these, just to experiment. Sometimes they seem to work OK, while ot; /archives//html/RTTY/2013-02/msg00120.html (11,738 bytes)
38. Re: [RTTY] WPX suggestion (score: 1): Author: "Tom Osborne" <w7why@frontier.com>; Date: Fri, 8 Feb 2013 11:14:42 -0800; I vote for 'send me whatever you want', but call me :-) 73 Tom W7WHY only true if the number is sent once only; with 599 123 123 the probability that both USOS characters are hit is just marginal.. I; /archives//html/RTTY/2013-02/msg00124.html (9,335 bytes)
39. Re: [RTTY] WPX suggestion (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Fri, 08 Feb 2013 11:58:40 -0800; REPLY: That's quite true, but a single error on a non-dash or non-figs character only garbles that single character. An error on a dash or figs character garbles everything that follows it until USOS; /archives//html/RTTY/2013-02/msg00125.html (10,533 bytes)
40. Re: [RTTY] WPX suggestion (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Fri, 08 Feb 2013 12:07:36 -0800; REPLY: Anytime you use a dash in the exchange it prevents USOS from working. USOS is a good thing, it was invented for a good reason. Let it do its job. Bill, W6WRT __________________________________; /archives//html/RTTY/2013-02/msg00127.html (8,398 bytes)

Current List: 21 - 40
Page: [1] [2]