Maybe this has shown up before. If it has, I've missed it. WA8YRS sez... This brings up a questions that I've (kinda) worried about for a while... Having a Q 'in the log' is fine, BUT does it matter
I am pretty sure that some contests only look at callsigns and they dont really care about the times. Why would his software remove it fromt he log - it should only mark it as a DUPE and give it zero
Thus spoke Tom Hammond: The proper thing for your contest software to do is to mark it as a dupe, give it 0 points, but leave it in the log. If your software is actually removing dupes from the log,
... I have found it eaiser and faster to work dupes that call me when I am CQing in every contest ... [Huml Martin] I agree. I always work dupes - now in WW DX CW as IH9/OL5Y I worked 2113 Qs and 167
Hi ! Some years ago I still told people "QSO B4". Today I will just work them again and again and again. There could be so many reasons, why he calls again. It doesn't help, when he is in your log -
The bottom line is: "It's not possible to know." In the 1998 ARRL November Sweepstakes (CW), I had my logging program crash/lock up on me about 50 times over the weekend, which was quite a nuisance,
N5KO Trey's story is a good lesson. You just don't know why he's calling again... working and having a dupe doesn't take any longer and doesn't hurt your score... saying qso b4 takes about as much ti
I think most of these have been mentioned in the past, but maybe not all in one place? Here are the reasons I can think of for a dupe calling you: 1. He busted your call the first time he worked you
More? Sincerely, dr. bafoofnik -- End of Forwarded Message -- CQ-Contest on WWW: http://www.contesting.com/_cq-contest/ Administrative requests: cq-contest-REQUEST@contesting.com
snop Various bone-head operations, like a typo before the dupe check. 73, Scott K9MA -- Scott Ellington sdelling@facstaff.wisc.edu Madison, Wisconsin USA -- CQ-Contest on WWW: http://www.contesting.c
Author: K4BAI@worldnet.att.net (John T. Laney, III)
Date: Thu Dec 10 13:49:17 1998
Of course, the answer to the problem is NEVER to delete a duplicate QSO. Just leave it in as a duplicate for zero credit. 73, John, K4BAI/8P9HT. -- CQ-Contest on WWW: http://www.contesting.com/_cq-co
Hi Dave. This is about 99.9% of my dupes. I keep forgetting to change the computer when I change bands. Too bad the programs couldn't be set up so the bands change automatically when the op changes b
Thus spoke Tom Osborne: Tr Log will do this with a radio that is interfaced to the computer. -- -- Kenneth E. Harker "Vox Clamantis in Deserto" kharker@cs.utexas.edu University of Texas at Austin Ama
Tom, All the logging programs do this...as long as your radio is capable of being controlled by a computer. 73, Tom K5IID Tom Horton K5IID That's WEST , by gawd, Virginia !!! -- CQ-Contest on WWW: ht
Hello: I have a question about working dupes. I looked up a couple of major contests and the rules that apply to them. I sure most of you know them already, but I put them here for clarity. These rul
I learned (painfully) last year that many of my CQ CW dupes resulted from my call being busted on a couple of packet spots. The "packeteers" then worked me, not bothering to listen to whom they were
I agree with you Ben, I used to B4 but not any longer. You waste more time explaining than working them again. Computer counts it only once, anyway. So does Q Rate... 73 Ivo 5B4ADA/C4A -- CQ-Contest
snip. . . What if you (the CQer) are REALLY not in the other ops (the S&Per) log? What if he was working someone else, or needed a fill on your exchange and you went on to the next caller and he cou
So, why not leave it marked "Dupe" and leave it in the log? That helps clarify everything. Steve / N9FD -- End of Forwarded Message -- CQ-Contest on WWW: http://www.contesting.com/_cq-contest/ Admini
snop Various bone-head operations, like a typo before the dupe check. 73, Scott K9MA -- Scott Ellington sdelling@facstaff.wisc.edu Madison, Wisconsin USA -- CQ-Contest on WWW: http://www.contesting.c