[SOC] BW FOC-SOC etc
Davies, John (SSGM)
john.davies at kelvinhughes.com.sg
Thu Jun 7 02:38:23 EDT 2007
> FOC material, and I know it. With any luck, the rest of my
> incompetence in life will keep me in SOC, which is for me the ECV of
ham radio.
Myself also Fred. My Dad of course could do 60 wpm but then again he was
an old time naval telegraphist from the olden day mould of WW1 when that
was the leading edge of communication.
72/73's
Ian C. Purdie
Hello All,
Very nice posts and I likes Ian's in particular. I have read your
tutorials many time in the past. Good stuff. I am new to SOC and
enjoying it, just wish I could have more QSO's with you guys. The
conditions are terrible.
On the subject of speed, is it really the mark of a great operator? I
have heard some ops using keyboards at 50-60 wpm. I much prefer
listening to a slow swingy bug or stuttering straight key than a
machine....maybe that's why I am Second Class, being a straight key man
mostly all these years since joining the merchant navy.
Although I must say listening to some FOC's is also good. James / 9 V 1
Y C is a compatriot and Shin / J A 1 N U T likes to QSO with the
lowliest, including me.
73 de John 9 V 1 V V
PS This bounced back due to me using a wrong email address... typical
SOC. I hope this gets to you..
</table> </Pre>
<HTML>
<br>
<br>
************************************************<br>
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.<br>
************************************************<br>
</HTML>
More information about the SOC
mailing list