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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ARRL\s+CAC\s+input\s+sought\s*$/: 3 ]

Total 3 documents matching your query.

1. ARRL CAC input sought (score: 1): Author: albraun@socketis.net (albraun@socketis.net); Date: Thu Aug 1 18:00:06 1996; I agree with this completely. The 10-minute rule is a real hindrance to a m-s moving to 10 or 160 since you frequently can't count on enough activity (other than the mult you want to move or the one; /archives//html/CQ-Contest/1996-08/msg00003.html (10,270 bytes)
2. ARRL CAC input sought (score: 1): Author: k9uwa@cris.com (John Goller); Date: Fri Aug 2 01:18:42 1996; OH....so as ABRAUN pointed out now we can "rubber clock"3-5 minutes and thats OK !!!! 10 minute rule has outlived its usefullness!! What we really need is a "2 RADIO RULE" any more than 2 RADIOS and; /archives//html/CQ-Contest/1996-08/msg00004.html (8,185 bytes)
3. ARRL CAC input sought (score: 1): Author: albraun@socketis.net (albraun@socketis.net); Date: Sat Aug 3 02:18:24 1996; As a veteran of 2 DXpeditions to V3 for the ARRL contest, I agree 1000% with this idea. My trips to Belize were one-radio operations, but we went M/S due to their being more than one operator taking; /archives//html/CQ-Contest/1996-08/msg00008.html (18,491 bytes)

Current List: 1 - 3
Page: [1]