<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19403">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face="Lucida Console">Hi, Jim -</FONT></DIV>
<DIV><FONT size=2 face="Lucida Console"></FONT> </DIV>
<DIV><FONT size=2 face="Lucida Console">First, it's important to distinguish
between signing and logging.</FONT></DIV>
<DIV><FONT size=2 face="Lucida Console"></FONT> </DIV>
<DIV><FONT size=2 face="Lucida Console">Standard CW mobile signing protocol
for QSO parties is exactly what you say: CALL/CTY. All mobiles are
strongly encouraged to sign this way. On phone, too, or at least they
should frequently say the county they are in.</FONT></DIV>
<DIV><FONT size=2 face="Lucida Console"></FONT> </DIV>
<DIV><FONT size=2 face="Lucida Console">Entering CALL/CTY in your log is always
safe. But if your </FONT><FONT size=2
face="Lucida Console">logger is QSO-party-aware, you don't need suffix on the
call - just enter the callsign where it belongs and the county abbreviation
where it belongs. This will save a few keystrokes. </FONT></DIV>
<DIV><FONT size=2 face="Lucida Console"></FONT> </DIV>
<DIV><FONT size=2 face="Lucida Console">If your program is not QSO-party-aware,
please DO NOT enter weird suffixes to trick the program so it won't complain
about dupes. If it tricks your program, it will probably trick our log
check software, too. As I said above, entering CALL/CTY is always
safe. If your logger can't accept this, maybe you need a different
one.</FONT></DIV>
<DIV><FONT size=2 face="Lucida Console"></FONT> </DIV>
<DIV><FONT size=2 face="Lucida Console">Hope this helps,</FONT></DIV>
<DIV><FONT size=2 face="Lucida Console"> - Tom, K9BTQ</FONT></DIV>
<DIV><FONT size=2 face="Lucida Console"> WIQP team</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=jim.gmforum@gmail.com href="mailto:jim.gmforum@gmail.com">Jim GM</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=wiqp-mail@warac.org
href="mailto:wiqp-mail@warac.org">wiqp-mail@warac.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, March 15, 2013 11:00
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [WIQPmail] MOBILE Suffix</DIV>
<DIV><BR></DIV>Hi every one!
<DIV>
<DIV><BR></DIV>
<DIV>I found it hard to figure out what stations were mobile. Took a lot
of time away for hunting and pouncing. What made it easy were the stations
like my old friend W9DND would send W9DND/BAR. This helped a lot.</DIV>
<DIV><BR></DIV>
<DIV>Some stations just signed their call not even a /M</DIV>
<DIV><BR></DIV>
<DIV>Other problem was my logging program. Not sure if others had this
issue but /BAR or /M just was not acceptable with the program I was running.
What helped was /1, /2, /3 ..... This way the computer program did
not see it as a DUP or call not recognized.</DIV>
<DIV><BR></DIV>
<DIV>Any comments?</DIV>
<DIV><BR></DIV>
<DIV>By the way I have an Apple computer and was running a program called
RumPed. Ran real fast.<BR clear=all>
<DIV><BR></DIV>-- <BR>Jim K9TF / WA9YSD</DIV></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>WIQP-mail mailing
list<BR>WIQP-mail@warac.org<BR>http://mail.warac.org/mailman/listinfo/wiqp-mail_warac.org<BR></BLOCKQUOTE></BODY></HTML>