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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+Cut\s+numbers\s*$/: 85 ]

Total 85 documents matching your query.

21. [CQ-Contest] Cut Numbers (score: 1): Author: David Gilbert <xdavid@cis-broadband.com>; Date: Sat, 02 Dec 2006 13:44:15 -0700; Unless you're using cut numbers that are readily recognizable by the majority of people operating in the contest you're totally kidding yourself that you are saving time. All it takes is a handful of; /archives//html/CQ-Contest/2006-12/msg00097.html (6,944 bytes)
22. Re: [CQ-Contest] cut numbers (score: 1): Author: "Art Boyars" <art.boyars@verizon.net>; Date: Mon, 04 Dec 2006 09:38:29 -0500; N6TJ said: "Simply asked: why send more than required to get the message across?" Indeed: "... to get the message across...." Well we knew that even before Claude Shannon explained it. So it works OK; /archives//html/CQ-Contest/2006-12/msg00128.html (8,253 bytes)
23. Re: [CQ-Contest] cut numbers (score: 1): Author: "Paul O'Kane" <pokane@ei5di.com>; Date: Mon, 4 Dec 2006 17:49:51 -0000; . It has been confirmed that CQ's checking software does not check RST. You have to send RST because it's in the CQWW rules :-) Time to update the rules? 73, Paul EI5DI ______________________________; /archives//html/CQ-Contest/2006-12/msg00135.html (7,321 bytes)
24. Re: [CQ-Contest] cut numbers (score: 1): Author: Hank Kohl K8DD <k8dd@arrl.net>; Date: Mon, 04 Dec 2006 17:39:48 -0500; So ...... to save sending time ...... and if the RST doesn't much matter ..... EEEE RST 555 zone 5 EEEV RST 555 zone 4 Is that going too far with the cut numbers? 73 Hank K8DD ______________________; /archives//html/CQ-Contest/2006-12/msg00145.html (7,719 bytes)
25. Re: [CQ-Contest] cut numbers (score: 1): Author: "Bob Henderson" <bob@5b4agn.net>; Date: Tue, 5 Dec 2006 08:22:06 -0000; Inherent in the deployment cut numbers should be an assessment by the sender of whether they will firstly, be understood and secondly, whether it matters if they are not. If in CQWW, neither RST nor; /archives//html/CQ-Contest/2006-12/msg00170.html (9,406 bytes)
26. Re: [CQ-Contest] cut numbers (score: 1): Author: Alan Zack <k7acz@cox.net>; Date: Tue, 05 Dec 2006 17:55:58 -0800; If you have to change the RST (or anything else in the log) you can just edit the cabrillo file before you submit it. When this happens to me I scribble out a yellow sticky reminding me to make the c; /archives//html/CQ-Contest/2006-12/msg00223.html (10,632 bytes)
27. Re: [CQ-Contest] cut numbers (score: 1): Author: Bill Coleman <aa4lr@arrl.net>; Date: Sun, 31 Dec 2006 09:46:57 -0500; The log-checking will not bust you for a bad RST. We have to send it because it is in the rules. -- This reminds me of the times I'm watching television, and some character on a show does something t; /archives//html/CQ-Contest/2006-12/msg00670.html (7,887 bytes)
28. Re: [CQ-Contest] cut numbers (score: 1): Author: "Julio VE3FH" <ve3fh@rac.ca>; Date: Sun, 31 Dec 2006 14:58:27 -0500; Why? because it makes it easier to copy what's next that's why, at least that's the way it works for me. Think of it as the preamble and/or frame delimiter of an Ethernet frame, why is it there? to s; /archives//html/CQ-Contest/2006-12/msg00674.html (9,326 bytes)
29. Re: [CQ-Contest] cut numbers (score: 1): Author: "Tom Osborne" <w7why@verizon.net>; Date: Sun, 31 Dec 2006 15:11:07 -0800; I agree. I finally put a 'TU' before the grid in my macro and that seems to help also. Some guys come back so fast with the grid square only I'd miss the first letter and have to ask for a repeat. 73; /archives//html/CQ-Contest/2006-12/msg00680.html (8,277 bytes)
30. Re: [CQ-Contest] cut numbers (score: 1): Author: Ed K1EP <k1ep.list@gmail.com>; Date: Sun, 31 Dec 2006 18:13:27 -0500; The problem with the Stew Perry contest is that we are so accustomed to hearing the RST that we expect it. Many send 599 as 5NN. Some cut it even closer with ENN. So, now you are expecting to hear "E; /archives//html/CQ-Contest/2006-12/msg00681.html (11,116 bytes)
31. Re: [CQ-Contest] cut numbers (score: 1): Author: Ev Tupis <w2ev@yahoo.com>; Date: Sun, 31 Dec 2006 18:14:23 -0800 (PST); -- Original Message -- I agree. I finally put a 'TU' before the grid in my macro and that seems to help also. Some guys come back so fast with the grid square only I'd miss the first letter and have; /archives//html/CQ-Contest/2007-01/msg00001.html (7,694 bytes)
32. Re: [CQ-Contest] cut numbers (score: 1): Author: K6VVA <dx35@hilding.com>; Date: Sun, 31 Dec 2006 19:20:43 -0800; Interesting the subject of cut numbers has surfaced again. Basically, I hate cut numbers. However, just yesterday I was thinking about maybe using "Cut Characters" in the next CW Sprint. Since my leg; /archives//html/CQ-Contest/2007-01/msg00006.html (7,391 bytes)
33. Re: [CQ-Contest] cut numbers (score: 1): Author: Doug Smith W9WI <w9wi@earthlink.net>; Date: 01 Jan 2007 01:23:49 -0600; I got briefly confused when, at 1am, a station sent me "TU BK". Then, before I could hit ^K and send "GRID?", he sent "29". Turns out that was his grid - BK29. My brain just wasn't prepared to accept; /archives//html/CQ-Contest/2007-01/msg00012.html (8,055 bytes)
34. [CQ-Contest] cut numbers (score: 1): Author: Dennis OConnor <ad4hk2004@yahoo.com>; Date: Tue, 2 Jan 2007 04:48:37 -0800 (PST); I got on the SP for a short time... I found that a significant number of the stations I worked apparently heard EN73 as R 73... They would panic and send 'grid?' before I could qsy <they thought> Now; /archives//html/CQ-Contest/2007-01/msg00027.html (7,439 bytes)
35. Re: [CQ-Contest] cut numbers (score: 1): Author: Steve London <n2icarrl@gmail.com>; Date: Tue, 02 Jan 2007 09:13:56 -0500; Back when I lived in DN70, I quickly discovered that I needed to insert some space between the D and the N. I guess it sounded too much like /70 . I suggest putting in some space between the E and N; /archives//html/CQ-Contest/2007-01/msg00029.html (7,955 bytes)
36. Re: [CQ-Contest] cut numbers (score: 1): Author: Jimk8mr@aol.com; Date: Tue, 2 Jan 2007 09:27:09 EST; During the SP I called a guy who gave me an EM2N report. So I gave him back an ENNA report. And again. And again. Then I tried EN 91 and it got through. I did notice that EN was often interpreted as; /archives//html/CQ-Contest/2007-01/msg00030.html (6,982 bytes)
37. Re: [CQ-Contest] cut numbers (score: 1): Author: "Yuri VE3DZ" <ve3dz@rigexpert.net>; Date: Tue, 2 Jan 2007 19:05:06 -0500; Jim, I believe this is what differs a very good operator from ...e-e-e-h... the rest of good operators. He wants to maximize his QSO total and he quickly adjusts himself to: a) particular contest; b); /archives//html/CQ-Contest/2007-01/msg00035.html (8,728 bytes)
38. Re: [CQ-Contest] cut numbers (score: 1): Author: "Paul J. Piercey" <p.piercey@nl.rogers.com>; Date: Wed, 3 Jan 2007 00:40:44 -0000; I use cut numbers in the RST only and I don't think they should be used in any other part of a contest report. It seems to me that any advantage gained in time by their use would be lost in repeats w; /archives//html/CQ-Contest/2007-01/msg00037.html (8,794 bytes)
39. Re: [CQ-Contest] cut numbers (score: 1): Author: "Shelby Summerville" <k4ww@arrl.net>; Date: Wed, 3 Jan 2007 05:49:41 -0500; Jimk8mr@aol.com wrote: "I did notice that EN was often interpreted as R." I fall into that group, especially when "EN" was not preceded by "5NN, TU, GM, etc". I'm curious if "EM" is interpreted as "W; /archives//html/CQ-Contest/2007-01/msg00040.html (7,614 bytes)
40. [CQ-Contest] Cut Numbers (score: 1): Author: G3SJJ <g3sjj@btinternet.com>; Date: Sat, 17 Mar 2007 22:42:48 +0000; Is it considered acceptable to use cut numbers in a callsign when CQing in a contest? For instance, I use G8D, so could I use GUD, or for GU8D could I use GUUD? Chris G3SJJ __________________________; /archives//html/CQ-Contest/2007-03/msg00277.html (6,711 bytes)

Current List: 21 - 40
Page: [1] [2] [3] [4] [5]