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

Results:

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

Total 11 documents matching your query.

1. [CQ-Contest] Cut numbers in SSCW (score: 1): Author: KI9A@aol.com; Date: Mon, 9 Nov 2009 20:56:18 EST; I've noticed in the last couple of years, there seems to be more and more use of cut numbers in SS. Guys, this is NOT the place to use them. With the mix of numbers and letters, the confusion is much; /archives//html/CQ-Contest/2009-11/msg00203.html (7,361 bytes)
2. Re: [CQ-Contest] Cut numbers in SSCW (score: 1): Author: "Robert Brandon" <rb@austin.rr.com>; Date: Tue, 10 Nov 2009 08:27:19 -0600; I agree. Cut numbers are definitely disorienting, especially on a weak signal. It makes you wonder if he's repeating his precedence, if you missed the last letter of his call on the first go-round, e; /archives//html/CQ-Contest/2009-11/msg00208.html (9,575 bytes)
3. Re: [CQ-Contest] Cut numbers in SSCW (score: 1): Author: Jim Roller <n4ir@charter.net>; Date: Tue, 10 Nov 2009 09:32:59 -0500; Chuck, I agree. SS is no place for cut numbers. How much time do you "save" vs. the requests for fills? Then there are the ops who send the call sign in the exchange at 75+ wpm. Whether running or S&; /archives//html/CQ-Contest/2009-11/msg00210.html (8,348 bytes)
4. Re: [CQ-Contest] Cut numbers in SSCW (score: 1): Author: Ed K1EP <k1ep.list@gmail.com>; Date: Tue, 10 Nov 2009 10:23:39 -0500; I agree 110%. Almost as bad as having someone send an R as dit dahdit (instead of TU or CFM or QSL or even a correctly spaced R) in the Stew Perry contest. I begin to copy it as grid square EN and th; /archives//html/CQ-Contest/2009-11/msg00213.html (9,070 bytes)
5. Re: [CQ-Contest] Cut numbers in SSCW (score: 1): Author: Zack Widup <w9sz.zack@gmail.com>; Date: Tue, 10 Nov 2009 10:19:02 -0600; I heard a few people use cut numbers and in a couple of cases for me the last digit of their serial number happened to be a cut number. I automatically typed it in as their precedence. My logging pro; /archives//html/CQ-Contest/2009-11/msg00216.html (9,401 bytes)
6. Re: [CQ-Contest] Cut numbers in SSCW (score: 1): Author: "Felipe J Hernandez" <fhdez@islandnetjm.com>; Date: Tue, 10 Nov 2009 14:26:58 -0400; True, ... when you are already spending 20 secs on an exchange why worry about saving one and confusing the whole thing... I found that I was being asked for repeats on nr and ck using complete numbe; /archives//html/CQ-Contest/2009-11/msg00217.html (9,534 bytes)
7. Re: [CQ-Contest] Cut numbers in SSCW (score: 1): Author: Jim Reisert AD1C <jjreisert@alum.mit.edu>; Date: Tue, 10 Nov 2009 12:21:48 -0700; "EVERY guy that gave me cut numbers, I asked for a fill on purpose." Good for you! Add to that: - people who don't send MY call as part of the exchange NOTE: it's apparently not required according to; /archives//html/CQ-Contest/2009-11/msg00219.html (8,389 bytes)
8. Re: [CQ-Contest] Cut numbers in SSCW (score: 1): Author: John Laney <k4bai@worldnet.att.net>; Date: Tue, 10 Nov 2009 14:46:41 -0500; Sending the call sign as a part of the exchange (at a reasonable speed) is a very good way of advertising to those who have just tuned across your frequency. Much better than having to send a new CQ; /archives//html/CQ-Contest/2009-11/msg00221.html (7,917 bytes)
9. Re: [CQ-Contest] Cut numbers in SSCW (score: 1): Author: "Robert Brandon" <rb@austin.rr.com>; Date: Tue, 10 Nov 2009 13:58:16 -0600; Great point, John. When I'd get a little pileup going, I'd just send a "TU" after each QSO and not feel the slightest twinge of guilt. :-) Robert K5PI Sending the call sign as a part of the exchange; /archives//html/CQ-Contest/2009-11/msg00222.html (9,250 bytes)
10. Re: [CQ-Contest] Cut numbers in SSCW (score: 1): Author: "Jon" <w4zw@comcast.net>; Date: Tue, 10 Nov 2009 15:32:22 -0500; Amen! Nothing gets you like an unexpected cut number or omission or transposition of the exchange. My brain gets it, but my fat fingers don't! Invariably I mess up the keyboard entry, lose concentrat; /archives//html/CQ-Contest/2009-11/msg00224.html (9,178 bytes)
11. Re: [CQ-Contest] Cut numbers in SSCW (score: 1): Author: "hank.k8dd" <hank.k8dd@gmail.com>; Date: Tue, 10 Nov 2009 17:09:01 -0500; It was neat with N1MM, using ESM ...... If they sent a cut number for NR 4T7 or CK TN and that's what I automatically typed in and hit enter, N1MM sends AGN .... every time! Made 'em repeat the whole; /archives//html/CQ-Contest/2009-11/msg00232.html (8,754 bytes)

Current List: 1 - 11
Page: [1]