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

Results:

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

Total 17 documents matching your query.

1. [CQ-Contest] What's BUSTED ? (score: 1): Author: n5nj@gte.net (Bob Naumann - N5NJ); Date: Mon Mar 6 17:08:23 2000; I agree with Mike that this is a great convention that should be adopted by all in the contest. Seeing AP9Z followed by AP9Z/Busted was not only informative, but amusing too. In this case, it was 8P9; /archives//html/CQ-Contest/2000-03/msg00051.html (9,981 bytes)
2. [CQ-Contest] What's BUSTED ? (score: 1): Author: thompson@mindspring.com (thompson@mindspring.com); Date: Mon Mar 6 12:45:46 2000; Jim KH2D answered the oft asked question what is a "bust" in a contest. A bust is simply a mislogged call. LY2DR is really LY1DR. Today's log checking can quicly ferret out a bust. But a bust can als; /archives//html/CQ-Contest/2000-03/msg00052.html (8,732 bytes)
3. [CQ-Contest] What's BUSTED ? (score: 1): Author: sdelling@facstaff.wisc.edu (Scott Ellington); Date: Mon Mar 6 12:14:35 2000; I'm told the odds of a packet spot being busted are pretty high. That's not necessarily a bad thing. 73, Scott K9MA -- Scott Ellington Madison, Wisconsin USA sdelling@facstaff.wisc.edu -- CQ-Contest; /archives//html/CQ-Contest/2000-03/msg00054.html (8,205 bytes)
4. [CQ-Contest] What's BUSTED ? (score: 1): Author: kharker@cs.utexas.edu (Kenneth E. Harker); Date: Mon Mar 6 12:23:41 2000; I think it would be much more useful if the person who detected the "busted" callsign spot would instead spot the correct callsign. -- -- Kenneth E. Harker "Vox Clamantis in Deserto" kharker@cs.utexa; /archives//html/CQ-Contest/2000-03/msg00055.html (8,907 bytes)
5. [CQ-Contest] What's BUSTED ? (score: 1): Author: mgilmer@gnlp.com (Gilmer, Mike); Date: Mon Mar 6 13:24:50 2000; If is No, that's when one gets penalized for it. It's busted (wrong) as soon as one logs it incorrectly. Your version says that it's not a busted call if one doesn't get caught. Hmm, maybe that's tr; /archives//html/CQ-Contest/2000-03/msg00056.html (8,956 bytes)
6. [CQ-Contest] What's BUSTED ? (score: 1): Author: jjreisert@alum.mit.edu (Jim Reisert AD1C); Date: Mon Mar 6 15:03:00 2000; Ken, you need to do BOTH. I originally disliked the busted thing (you can't work HP9ZBUSTED so why spot it?) but I have seen the light. I hope more people do this. If I have HP9Z in my ANNOUNCE windo; /archives//html/CQ-Contest/2000-03/msg00061.html (9,681 bytes)
7. [CQ-Contest] What's BUSTED ? (score: 1): Author: n1eu@yahoo.com (N1EU); Date: Mon Mar 6 13:00:34 2000; If busted spots go uncorrected, the unwilling participant ends up being the dx station at the other end greeted by 100 callers on frequency who think they're trying to work a new mult and he has to s; /archives//html/CQ-Contest/2000-03/msg00064.html (8,414 bytes)
8. [CQ-Contest] What's BUSTED ? (score: 1): Author: kharker@cs.utexas.edu (Kenneth E. Harker); Date: Mon Mar 6 15:03:08 2000; I don't know - this logic seems kind of software-specific to me. (I don't even know what the ANNOUNCE window is.) I use TR Log, and the way needed mults show up is that the entry in the band map has; /archives//html/CQ-Contest/2000-03/msg00065.html (12,246 bytes)
9. [CQ-Contest] What's BUSTED ? (score: 1): Author: aa4lr@radio.org (Bill Coleman AA4LR); Date: Mon Mar 6 16:19:45 2000; Why can't we just teach people to LISTEN more carefully before calling? If you don't know what the DX callsign is on a packet spot, DO NOT CALL. I'm no longer afraid to ask a DX station for his calls; /archives//html/CQ-Contest/2000-03/msg00067.html (8,927 bytes)
10. [CQ-Contest] What's BUSTED ? (score: 1): Author: kg5u@hal-pc.org (Dale Martin); Date: Mon Mar 6 19:20:53 2000; Ah, there's the rub! People hear what they want to hear. Frequent use of the callsign may not be that effective in getting the call corrected in the busted call-filled callsign window. Also, the sma; /archives//html/CQ-Contest/2000-03/msg00072.html (8,928 bytes)
11. [CQ-Contest] What's BUSTED ? (score: 1): Author: ku7y@dri.edu (Monte Stark); Date: Mon Mar 6 20:55:08 2000; Lets see now...... Maybe someone who isn't all that nice posts the wrong call just to help the other stations get some points taken away! If you don't stick around and get the call with your own ears; /archives//html/CQ-Contest/2000-03/msg00073.html (8,511 bytes)
12. [CQ-Contest] What's BUSTED ? (score: 1): Author: oo7@pan.as.utexas.edu (Derek Wills); Date: Mon Mar 6 23:48:54 2000; I guess that's why it's called "assisted". I've sometimes spotted stations just by the prefix, to let people know that there is a 9G or a BY on a particular frequency, but was asked not to do that..; /archives//html/CQ-Contest/2000-03/msg00074.html (8,359 bytes)
13. [CQ-Contest] What's BUSTED ? (score: 1): Author: vr2bg@harts.org.hk (VR2BrettGraham); Date: Tue Mar 7 06:53:48 2000; AK1A set the defacto standard for cluster spots: frequency, call, comments, time. "G3XYZBUSTED" is not a call. "G3XYZ" is a call & "BUSTED" is a comment. When someone spots a wrong call, either they'; /archives//html/CQ-Contest/2000-03/msg00076.html (8,382 bytes)
14. [CQ-Contest] What's BUSTED ? (score: 1): Author: aa4lr@radio.org (Bill Coleman AA4LR); Date: Tue Mar 7 10:24:59 2000; I think the problem exists with some contesting software. Say someone spots BD2X, which would be a new multiplier -- so it shows up in the packet window. Someone else correctly spots 6D2X, who you've; /archives//html/CQ-Contest/2000-03/msg00084.html (8,572 bytes)
15. [CQ-Contest] What's BUSTED ? (score: 1): Author: w7why@freewwweb.com (Tom Osborne); Date: Wed Mar 8 01:29:53 2000; Another good scenerio: XE2XXX is a few Q's behind 6D2X so he sends a spot "BD2X is on xxx.xx khz" so 6D2X spends the next half hour working dupes. Tom W7WHY -- CQ-Contest on WWW: http://www.contesti; /archives//html/CQ-Contest/2000-03/msg00088.html (8,530 bytes)
16. [CQ-Contest] What's BUSTED ? (score: 1): Author: vr2bg@harts.org.hk (VR2BrettGraham); Date: Thu Mar 9 09:50:10 2000; AA4LR suggested: Yes, it looks to be a workaround for a particular program's behavior. Hopefully, the behavior will be corrected so that everyone else need not be subjected to the workaround. Rather; /archives//html/CQ-Contest/2000-03/msg00106.html (8,455 bytes)
17. [CQ-Contest] What's BUSTED ? (score: 1): Author: vr2bg@harts.org.hk (VR2BrettGraham); Date: Fri Mar 10 01:02:04 2000; N2MG further commented: Let the software do whatever it wants - but it should not be a reason to muck up spots as a workaround. The spots are a common resource used by who knows what all which work b; /archives//html/CQ-Contest/2000-03/msg00117.html (8,590 bytes)

Current List: 1 - 17
Page: [1]