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

Results:

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

Total 25 documents matching your query.

1. [CQ-Contest] unIDs (score: 1): Author: Doug Smith <w9wi@earthlink.net>; Date: Sun, 27 Nov 2011 18:30:14 -0600; (a term from the broadcast DX world used to refer to stations you hear that are probably good DX but can't be identified. Of course, the FCC broadcasting regulations only require stations to give the; /archives//html/CQ-Contest/2011-11/msg00418.html (8,077 bytes)
2. Re: [CQ-Contest] unIDs (score: 1): Author: "Ron Notarius W3WN" <wn3vaw@verizon.net>; Date: Sun, 27 Nov 2011 21:44:22 -0500; If you don't know who they are, don't call them. If, as a S&P station, you don't want to wait for an ID, move on to work someone else. Some stations ID after every contact. Some after every other. So; /archives//html/CQ-Contest/2011-11/msg00420.html (10,025 bytes)
3. [CQ-Contest] unIDs (score: 1): Author: Ken Claerbout <k4zw@verizon.net>; Date: Sun, 27 Nov 2011 21:56:04 -0600 (CST); It wasn't just you Doug. The problem has been discussed before but it exploded this weekend like I've never heard it before. I don't know why. I get not ID'ing after every QSO at times. But going 5 o; /archives//html/CQ-Contest/2011-11/msg00422.html (8,410 bytes)
4. Re: [CQ-Contest] unIDs (score: 1): Author: "Tom Osborne" <w7why@frontier.com>; Date: Sun, 27 Nov 2011 21:22:05 -0800; Hi Ron True, but if someone is sending '5nn23', I'd sure like to know who it is. If they are sending '5nn13', I'd probably not be all that excited and move on. 73 Tom W7WHY "If you don't know who the; /archives//html/CQ-Contest/2011-11/msg00423.html (7,800 bytes)
5. Re: [CQ-Contest] unIDs (score: 1): Author: PaulKB8N@aol.com; Date: Mon, 28 Nov 2011 02:29:57 -0500 (EST); FYI, here is what I posted in my 3830 writeup, FWIW. I posted this before I realized there was a thread started on CQ-Contest. "Same old irritant! We need to make a rule that when running, stations; /archives//html/CQ-Contest/2011-11/msg00425.html (8,332 bytes)
6. Re: [CQ-Contest] unIDs (score: 1): Author: Paul O'Kane <pokane@ei5di.com>; Date: Mon, 28 Nov 2011 09:18:42 +0000; The problem is recent, and getting worse. It stems from those stations assuming everyone else knows their call from spots or the RBN. For as long as they get a steady stream of callers, they have no; /archives//html/CQ-Contest/2011-11/msg00426.html (8,677 bytes)
7. Re: [CQ-Contest] unIDs (score: 1): Author: Barry <w2up@comcast.net>; Date: Mon, 28 Nov 2011 05:45:20 -0700; Solutions: 1. Tune by without working the non-IDer. 2. Ask for his call BEFORE you give your exchange. For example: TUer: TU You: K4ZW TUer: K4ZW ENNN You: CALL? etc. I've had the occasional TUer say; /archives//html/CQ-Contest/2011-11/msg00427.html (8,431 bytes)
8. Re: [CQ-Contest] unIDs (score: 1): Author: Ron Notarius W3WN <wn3vaw@verizon.net>; Date: Mon, 28 Nov 2011 07:47:24 -0600 (CST); I understand. And I know it's frustrating. But it's one thing to wait (as frustrating as it is) on a "rare" Zone 23 station. Odds are pretty good he knows he has the zone to himself and can do things; /archives//html/CQ-Contest/2011-11/msg00429.html (8,859 bytes)
9. Re: [CQ-Contest] unIDs (score: 1): Author: Don Field <don.field@gmail.com>; Date: Mon, 28 Nov 2011 14:24:26 +0000; The flip side is that it behoves callers to actually listen. I was mis-spotted late yesterday as G4XTT and the spotter corrected it less than a minute later with an apology. But I ended up with a bun; /archives//html/CQ-Contest/2011-11/msg00430.html (10,745 bytes)
10. Re: [CQ-Contest] unIDs (score: 1): Author: "Larry" <lknain@nc.rr.com>; Date: Mon, 28 Nov 2011 10:51:56 -0500; The problem goes in cycles. It is getting worse at the moment. There will be some backlash as a result of discussion. The situation will improve some for awhile and then get worse again if it follows; /archives//html/CQ-Contest/2011-11/msg00438.html (10,374 bytes)
11. Re: [CQ-Contest] unIDs (score: 1): Author: PaulKB8N@aol.com; Date: Mon, 28 Nov 2011 11:02:38 -0500 (EST); Paul, I agree that every third or fourth call is ideal. We have the technology to enforce it. I believe that RBN can actually record the entire contest and play back individual stations. It would be; /archives//html/CQ-Contest/2011-11/msg00440.html (10,027 bytes)
12. Re: [CQ-Contest] unIDs (score: 1): Author: Ron Notarius W3WN <wn3vaw@verizon.net>; Date: Mon, 28 Nov 2011 10:55:49 -0600 (CST); Well, heck yes Paul, it's a form of pile-up management. Not IMHO a good practice, nevertheless, it's there. But it's not recent, nor can it be blamed on the cluster or RBN. Those may exacerbate it, b; /archives//html/CQ-Contest/2011-11/msg00448.html (10,291 bytes)
13. Re: [CQ-Contest] unIDs (score: 1): Author: Doug Smith <dougw9wi@gmail.com>; Date: Mon, 28 Nov 2011 10:48:00 -0600; I respond to this with "CALL?". (they usually *do* then ID. Whether they get the point -- as to why I just called them for the 3rd/4th/5th time -- I have no idea.) -- Doug Smith W9WI Pleasant View, T; /archives//html/CQ-Contest/2011-11/msg00449.html (8,509 bytes)
14. Re: [CQ-Contest] unIDs (score: 1): Author: Jack/W6NF <vhfplus@gmail.com>; Date: Mon, 28 Nov 2011 10:19:45 -0800; I programmed "NIL" into one of the "F" keys in N1MM Logger. I only had to use it once when I got the "QSO B4" back. I had not received proper confirmation on the previous attempt and the Q was not lo; /archives//html/CQ-Contest/2011-11/msg00457.html (11,508 bytes)
15. Re: [CQ-Contest] unIDs (score: 1): Author: Barry <w2up@comcast.net>; Date: Mon, 28 Nov 2011 17:02:11 -0700; That's another brilliant move - spending more time telling the guy you worked before, rather than simply working him (again). Barry W2UP -- Barry Kutner, W2UP Lakewood, CO ___________________________; /archives//html/CQ-Contest/2011-11/msg00482.html (11,445 bytes)
16. Re: [CQ-Contest] unIDs (score: 1): Author: "Yuri" <ve3dz@rigexpert.net>; Date: Tue, 29 Nov 2011 04:47:14 -0500; Looks like this thread appears annually after each CQ WW CW Contest. It reminds me exactly of a "pedestrian-driver" situation. If the guy is a pedestrian, he would complain on "those fast and dangero; /archives//html/CQ-Contest/2011-11/msg00498.html (12,739 bytes)
17. Re: [CQ-Contest] unIDs (score: 1): Author: "Edward Sawyer" <SawyerEd@earthlink.net>; Date: Tue, 29 Nov 2011 06:55:14 -0500; Guys, you are all missing the best way to police the offenders. Work them but don't log them. If they see their UBN rate climbing, they will change their practice. After all, they are trying to win.; /archives//html/CQ-Contest/2011-11/msg00525.html (8,741 bytes)
18. Re: [CQ-Contest] unIDs (score: 1): Author: "Larry" <lknain@nc.rr.com>; Date: Tue, 29 Nov 2011 21:17:59 -0500; As someone else observed the detection by the offender is much too late to be useful. The offender would probably conclude "you" messed up by not logging the QSO. There is nothing that would lead me,; /archives//html/CQ-Contest/2011-11/msg00528.html (10,248 bytes)
19. Re: [CQ-Contest] unIDs (score: 1): Author: Jukka Klemola <jpklemola@gmail.com>; Date: Wed, 30 Nov 2011 18:02:10 +0200; Gents, Two Euro cents in this: 1. Most of the people behaving irrationally are absolutely not driving for a good score. Some do but I claim most do not. 2. Making a contest QSO and not deliberately n; /archives//html/CQ-Contest/2011-11/msg00535.html (9,614 bytes)
20. Re: [CQ-Contest] unIDs (score: 1): Author: "Edward Sawyer" <SawyerEd@earthlink.net>; Date: Wed, 30 Nov 2011 21:19:31 -0500; The reason I believe it is acceptable to work them and not log them is because if you run out of patience in waiting for them to sign, then you honestly don't know what to log. I believe its no diffe; /archives//html/CQ-Contest/2011-11/msg00578.html (8,484 bytes)

Current List: 1 - 20
Page: [1] [2]