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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*WKD\s+B4\s*$/: 17 ]

Total 17 documents matching your query.

1. WKD B4 (score: 1): Author: tekbspa!tavan@uunet.UU.NET (tekbspa!tavan@uunet.UU.NET); Date: Tue Dec 8 16:05:04 1992; RE W3CPB commented on alleged dupes. Here is my personal policy: When a dupe calls me, I tell him. If the exchange is short, I send it anyway and log the dupe. If the exchange is long (SS), I attempt; /archives//html/CQ-Contest/1992-12/msg00103.html (7,654 bytes)
2. WKD B4 (score: 1): Author: oo7@astro.as.utexas.edu (Derek Wills); Date: Tue Dec 8 23:24:48 1992; I really get ticked off when someone blows me away as a dupe and refuses to work me again even tho I am using computer logging and am absolutely sure he is not yet in my log. Rick N6XI -- This annoys; /archives//html/CQ-Contest/1992-12/msg00104.html (8,560 bytes)
3. WKD B4 (score: 1): Author: 71662.17@CompuServe.COM (BILL FISHER); Date: Wed Dec 9 09:19:22 1992; To: CQ-CONTEST@TGV.COM This past SS I had a number of guys call me and I blew them off with the usual "QSO B4 TU TEST DE N4RJ". After the contest Jeff (KR0Y) told me that one of his buddies tried to; /archives//html/CQ-Contest/1992-12/msg00110.html (9,365 bytes)
4. WKD B4 (score: 1): Author: mraz@maverick.aud.alcatel.com (Kris Mraz); Date: Wed Dec 9 08:35:03 1992; CT assumes you want to keep a dupe and makes you hit ALT W to clear it. I think a better way would be for it to assume that you don't want the dupe and clear is automatically. If you want to keep it; /archives//html/CQ-Contest/1992-12/msg00111.html (7,484 bytes)
5. WKD B4 (score: 1): Author: sellington@mail.ssec.wisc.edu (sellington); Date: Wed Dec 9 09:14:33 1992; Certainly, the safe thing to do is to work the dupe, especially in a contest with a short exchange, and log it for zero points. Then, of course, don't delete it from your log. For any one of a number; /archives//html/CQ-Contest/1992-12/msg00112.html (7,669 bytes)
6. WKD B4 (score: 1): Author: tucker@eedsp.gatech.edu (Jeff Tucker N9HZQ); Date: Wed Dec 9 11:42:41 1992; If you do work the guy a second time, even though you think it's a dupe, then what do you do with the log? If you remove the first contact, or count it for zero points, then maybe he finds your first; /archives//html/CQ-Contest/1992-12/msg00115.html (8,899 bytes)
7. WKD B4 (score: 1): Author: 71662.17@CompuServe.COM (BILL FISHER); Date: Wed Dec 9 13:51:18 1992; TO: CQ-CONTEST@TGV.COM re: In response to AA5UO's comments on CT... The one thing that I wish Ken would add is a NUKE button like K8CC has in his program (CNTRL-K = KILL). No matter what field you ar; /archives//html/CQ-Contest/1992-12/msg00120.html (8,669 bytes)
8. WKD B4 (score: 1): Author: reisert@mast.enet.dec.com (Alpha Personal Workstations -- DTN 223-5747 -- MLO3-6/B8 09-Dec-1992 1405); Date: Wed Dec 9 14:01:59 1992; --Reply to mail dated 9-DEC-1992 13:51:42.85-- I agree with Eric, K3NA. If you exchange reports with someone, even if s/he is a dupe, log it anyway. If you send "dupe" and the other station agrees, t; /archives//html/CQ-Contest/1992-12/msg00121.html (8,280 bytes)
9. WKD B4 (score: 1): Author: hurta@ap040.dseg.ti.com (Dwaine Hurta); Date: Wed Dec 9 13:43:43 1992; /archives//html/CQ-Contest/1992-12/msg00126.html (7,245 bytes)
10. WKD B4 (score: 1): Author: mikemr@microsoft.COM (mikemr@microsoft.COM); Date: Wed Dec 9 06:57:42 1992; I have found that when a station replies SRI B4, a simple WHEN? usually results in a Q, at least in the short-exchange contests. Mike N6MZ; /archives//html/CQ-Contest/1992-12/msg00130.html (7,070 bytes)
11. WKD B4 (score: 1): Author: reisert@mast.enet.dec.com (Alpha Personal Workstations -- DTN 223-5747 -- MLO3-6/B8 09-Dec-1992 1556); Date: Wed Dec 9 15:53:44 1992; --Reply to mail dated 9-DEC-1992 15:49:32.74-- I sure hope so! It's part of the exchange, and should be checked. BTW, this is another good reason not to remove duplicate QSOs in contests that have se; /archives//html/CQ-Contest/1992-12/msg00131.html (7,637 bytes)
12. WKD B4 (score: 1): Author: rhealy@arrl.org (Rus Healy NJ2L); Date: Wed Dec 9 15:54:19 1992; Yes. (Well, to be specific, the computer does it.) If you bust the serial number--or any other part of a QSO--you'll lose the Q (assuming that the Contest Branch checks your log, that is). Not true.; /archives//html/CQ-Contest/1992-12/msg00132.html (8,089 bytes)
13. WKD B4 (score: 1): Author: sellington@mail.ssec.wisc.edu (sellington); Date: Wed Dec 9 15:14:07 1992; Another reason to just work and log the dupes is the proliferation of similar calls: K3NA, K5NA, K3ZO, K9ZO, etc. With so many of the short callsigns in use by active contest operators, that's not su; /archives//html/CQ-Contest/1992-12/msg00137.html (7,539 bytes)
14. WKD B4 (score: 1): Author: sellington@mail.ssec.wisc.edu (sellington); Date: Wed Dec 9 09:14:33 1992; Certainly, the safe thing to do is to work the dupe, especially in a contest with a short exchange, and log it for zero points. Then, of course, don't delete it from your log. For any one of a number; /archives//html/CQ-Contest/1992-12/msg00302.html (7,801 bytes)
15. WKD B4 (score: 1): Author: sellington@mail.ssec.wisc.edu (sellington); Date: Wed Dec 9 15:14:07 1992; Another reason to just work and log the dupes is the proliferation of similar calls: K3NA, K5NA, K3ZO, K9ZO, etc. With so many of the short callsigns in use by active contest operators, that's not su; /archives//html/CQ-Contest/1992-12/msg00307.html (7,374 bytes)
16. WKD B4 (score: 1): Author: sellington@mail.ssec.wisc.edu (sellington); Date: Wed Dec 9 09:14:33 1992; Certainly, the safe thing to do is to work the dupe, especially in a contest with a short exchange, and log it for zero points. Then, of course, don't delete it from your log. For any one of a number; /archives//html/CQ-Contest/1992-12/msg00348.html (7,888 bytes)
17. WKD B4 (score: 1): Author: sellington@mail.ssec.wisc.edu (sellington); Date: Wed Dec 9 15:14:07 1992; Another reason to just work and log the dupes is the proliferation of similar calls: K3NA, K5NA, K3ZO, K9ZO, etc. With so many of the short callsigns in use by active contest operators, that's not su; /archives//html/CQ-Contest/1992-12/msg00353.html (7,414 bytes)

Current List: 1 - 17
Page: [1]