SS CW Score de KF3P

Fri Nov 12 02:15:34 EST 1993

SS CW Single Op High Power Score from MDC

1265 Q's - 75 Sections = 189,750 points

80 was HOT on east coast...high bands NOT!

CU on Phone!

Tyler, KF3P
/ex

>From k2mm at MasPar.COM (John Zapisek)  Fri Nov 12 07:36:52 1993
From: k2mm at MasPar.COM (John Zapisek) (John Zapisek)
Date: Thu, 11 Nov 93 23:36:52 PST
Subject: Two-Edged SprINT Busts
Message-ID: <9311120736.AA10309 at greylock.local>

Charlie, Alan, and all you other Internet SprINTers:  This note explains
some of the rationale behind "two-edged scoring".  It also asks that you
include in your log's comments any notes about mis-sent names or numbers.

> [K2MM]  The name Alan survived OK for six QSOs.  It was correctly received
> by KD5PJ on the sixth hop.  On the seventh hop, KD5PJ worked K6XO who
> recorded Max in his log. . . .

> [Charlie/KD5PJ]  I need to come clean here.  I fouled this up. . . .
> I panicked.  I sent Max to K6XO.

If you know you sent the wrong name, please say so in your log's comments.
The log-checking software assumes you sent the name previously received,
but it can handle the odd exception.  So far, we have allowed credit for
QSOs with the wrong sent-name or sent-number -- provided they are clearly
indicated and not excessive.  Remember that this averts wrongfully busting
not just your QSO, but the other op's as well.

> [Alan/K6XO]  . . . this points up the scenario where if either station
> makes an error, the scores of both stations suffer.  Not a fair way to
> assess operator performance and accuracy, in my opinion.

Note to Alan:  The two-edged bust rule works in your favor in this case.
Charlie's log says he sent you Alan.  Your log says you received Max.  With
classical scoring, *your* QSO would be busted for mis-copying Alan, but
Charlie would suffer no penalty.  It assumes (wrongly) that sending and
logging errors do not occur, just receiveing errors.  With two-edged
scoring, Charlie also pays the price for mis-logging the sent name.  This
gives him more incentive to correctly log the QSO, thereby reducing the odds
of your suffering a wrongful bust.

I think this makes sense.  73.  --John/K2MM

>From Takao Kumagai <je1cka at asuka.aerospace-lab.go.jp>  Fri Nov 12 16:04:55 1993
From: Takao Kumagai <je1cka at asuka.aerospace-lab.go.jp> (Takao Kumagai)
Date: Fri, 12 Nov 93 16:04:55 JST
Subject: Should any ops call not be appeard on any other logs?
Message-ID: <9311120704.AA14589 at asuka.aerospace-lab.go.jp>

re:PJ1B's M/S operation

I've never imagine those kind of operation technique so far.
These operations are legal in most countries and ok in PJ land.
Does CQ WW rule prohibit this clearly? No I don't think so.
So this N3ED/PJ4 operation with PJ1B might not be considered as
M/M? But this operation is in the gray zones between M/S & M/M.
Did any other M/S station do this? Is this never tried?

Will you fellow contesters accept this from the view of M/S ethic?
I say "NO". 
I strongly recommend to add one comment in CQ WW rule that;
*Any operators' callsign would not be appeared on anyone's log.

I heard that M/S or M/M operators did work the M/S or M/M stations
for their multiplier. for example at KH0AM m/m, AH0K is one of the
ops and he can work KH0AM using KH0AM's equipments for KH0AM's multi
with his AH0K callsign.
It is impossible to get the own country mult while you are the 
only one station in that country but I've never did this at KH0AM.
If this has been widely accepted ever, PJ1B technique will be accepted.
I feel there is no difference between two cases(PJ1B and KH0AM)
This might be discussed at the CQ WW Contest Committee.
(I believe most contest committee members are e-mail accessible
and reading this reflecter. So now the time Bob?)

I saw the comment in some (yes some not one) M/M stations operating 
guide that;
If you got a call from the stations which be other bands multi, you
should requst hir to move the bands for mult. 
But do this only when you are called. (or something like that)

Tack KUMAGAI
JE1CKA/KH0AM
One of the crazy contesters in the risingsun country.

>From Jim Reisert AD1C  12-Nov-1993 1021 <reisert at wrksys.enet.dec.com>  Fri Nov 12 15:16:34 1993
From: Jim Reisert AD1C  12-Nov-1993 1021 <reisert at wrksys.enet.dec.com> (Jim Reisert AD1C 12-Nov-1993 1021)
Date: Fri, 12 Nov 93 10:16:34 EST
Subject: new MERGE for CT Version 8
Message-ID: <9311121516.AA27444 at us1rmc.bb.dec.com>

[The original bounced, hope this copy makes it OK]

  Ken just put a new MERGE.ZIP on the CT BBS (508-460-8877).  This has both
  MERGE.EXE and MERGE386.EXE.  The new MERGE is compatible with CT version 8.
  Previous versions of MERGE (even those that were distributed on the version
  8 disks) would only really work with .BIN files created with CT version 7.

  As a reminder, MERGE.EXE can run on any computer 8086-80486, while MERGE386
  can run on only 80386 and above machines.  It does not matter which kind of
  computer created the .BIN file, the .BIN file format is the same whether
  you're using CT86.EXE, CT286.EXE or CT386.EXE.

  73 - Jim AD1C

>From george fremin iii <geoiii at wixer.bga.com>  Fri Nov 12 15:51:42 1993
From: george fremin iii <geoiii at wixer.bga.com> (george fremin iii)
Date: Fri, 12 Nov 93 9:51:42 CST
Subject: cw ss scores
Message-ID: <9311121551.AA11092 at wixer>

11-12   1548z
single op high power
WM5G    1604 76
W5WMU   1557 77
N4RJ    1529 77
K5GN    1462 77
W7RM    1444 77
K6LL    1428 77
N2IC    1422 77
K0RF    1414 77
NC0P    1409 77
K9FD    1400 77

NM5M    1383 77
K5MR    1377 76
K3LR    1372 76
VE3EJ   1364 76
K7UP    1357 76
AH3C    1351 77
N6TV    1313 77
KZ2S    1300 76
W6EEN   1298 77
K1TO    1292 76

N8RR    1281 77
W1XE    1271 77
KF3P    1265 75
K1DG    1257 76
K4VX    1253 77
N6RO    1248 77
W6QHS   1248 77
AA7NX   1238 77
KQ8M	1238 76
KI3L    1237 77

AA4NC   1230 76
W5KFT	1227 76
KT3Y    1220 75
WA8ZDT  1218 76
K3ZO    1215 76
K6KM    1199 77
W2SC    1190 76
KW8N    1187 76
AA6KX   1094 77
KE9I    1053 77

W2RQ	1050 75
K2MM    1038 77
WB1GQR  1016 74
W5ASP   1000 76
WG9L     903 77
WE9V     874 76
KF8QE    894 76
W9YH     848 76
AA8U	 831 75
W1IHN    715 76

N6AZE    281 73
N4TQO    213 57
K5EC      63 33

single op low power
NP4A    1388 77
N5RZ    1315 76
KY7M    1217 75
AD5Q    1210 77
K0EU    1173 75
W1FEA   1106 77
AB6FO   1075 76
K4XU    1070 76
N4AA    1030 77
N0AT    1016 76

N4TY    1006 74
WA2SRQ   950 76
W6UQF    939 77
AC5K     923 76
VE4VV    916 77
KZ4H     913 76
KQ7I     912 76
NJ2L     901 76
KO9Y     852 77
KP4TQ    840 73

N6MZ     823 77
N9JF     804 75
AI6E     782 74
N7LOX    718 76
NN5T     712 75
N6PN     685 76
AA6MC    682 76
KE4GY    682 74
N0AX     615 76
WN3K     567 76

W5XD     565 72
WA1U     529 76
WT0K     471 70
KF9PL    455 73
ND1H     429 70
K7GM     425 72
KI4HN    347 69
N6KL     340 70
AC9CH    310 72
NG0X     260 31

KJ5JC    194 55
KU4A     152 61
AA5UO    149 52
NV3V     111 47

single op qrp
K0FRP    824 75
W2GD     814 76
W9UP     788 76
AA2U     757 75
W9RE     751 76
K1TR     686 76
WA4PGM   667 76
W7YAQ    590 73
KB4GID   569 72
N5NMX    465 73

WB2CPU   353 69
VE5VA    193 65
WA7BNM   100 52
N0BSH     16 14

multi-op
AA5B    1501 77
W4AQL   1379 77
N6VR    1321 77
WX0B    1308 76
K5OJI   1284 77
K6XT    1220 77
KB0S    1161 77
K0PP    1095 77	
W6BIP   1048 77
KI6X    1004 76

NV6O     666 77
K6XO     549 75