Return-Path: Received: from rly-dg09.mx.aol.com (rly-dg09.mail.aol.com [172.19.151.93]) by air-dg08.mail.aol.com (v121_r5.5) with ESMTP id MAILINDG082-5ef4955f93060; Sat, 27 Dec 2008 04:45:30 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-dg09.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINDG094-5ef4955f93060; Sat, 27 Dec 2008 04:45:22 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LGVjC-00071L-Pu for rs_out_1@blacksheep.org; Sat, 27 Dec 2008 09:45:02 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LGVjA-00071A-4G for rsgb_lf_group@blacksheep.org; Sat, 27 Dec 2008 09:45:00 +0000 Received: from smtp-out-2.talktalk.net ([62.24.128.232] helo=smtp.talktalk.net) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LGVj6-000234-Bu for rsgb_lf_group@blacksheep.org; Sat, 27 Dec 2008 09:45:00 +0000 X-Path: TTSMTP X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArcEADWIVUlOkGVg/2dsb2JhbACCPzCBZoZKBrFqWI8fhkQ Received: from unknown (HELO mal769a60aa920) ([78.144.101.96]) by smtp.talktalk.net with SMTP; 27 Dec 2008 09:44:46 +0000 Message-ID: <01aa01c96807$c07bd310$0301a8c0@mal769a60aa920> From: "mal hamilton" To: "rsgb" Date: Sat, 27 Dec 2008 09:44:45 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: LF: 500 QSO Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A7_01C96807.C02AA5D0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-AOL-IP: 193.82.116.20 ------=_NextPart_000_01A7_01C96807.C02AA5D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable LF/MF info Tnx Jay WE2XGR/2 for the QSO last nite on 500 khz on CW/QRS3. When u started calling about 2157 I was able to see ur sig OOO copy and stro= ng. There was some slow qsb during the evening but at QRS 3 it did not seem=20= to be a problem this speed was fast enough to get the info before a fade too= k place, however QRS 1 would probably have been better and in fact even norm= CW. In the past you signal has been audible.=20 Now that we have established a contact procedure on 500 I will try this more= often. I think there is a possibility that had u called earlier I would have detect= ed your signal, however 2200utc - 2400 is a good time. I have been working W= stns on 160m at times as early as 2000 utc, still daylight over ur way. I can have another bash tonight and if any others want to participate please= do so. I will TX on 502.57 khz and use QRS3 and then speed up if necessary. A good=20= USA freq would be around 508.5 khz which is perfectly clear here. If all W stns intererested in a TR QSO work around this freq with a little=20= separation I would be able to see who is about, and QSO accordingly. QRU now and agn tnx and looking forward to another QSO soon.I will have to c= k the QRB. de mal/g3kev/IO94SH ------=_NextPart_000_01A7_01C96807.C02AA5D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

LF/MF info

Tnx Jay WE2XGR/2 for the QSO last nite on 5= 00 khz=20 on CW/QRS3.

When u started calling about 2157 I was abl= e to see=20 ur sig OOO copy and strong. There was some slow qsb during the evening but a= t=20 QRS 3 it did not seem to be a problem this speed was fast enough to get the=20= info=20 before a fade took place, however QRS 1 would probably have been better and=20= in=20 fact even norm CW. In the past you signal has been audible.

Now that we have established a contact proc= edure on=20 500 I will try this more often.

I think there is a possibility that had u c= alled=20 earlier I would have detected your signal, however 2200utc - 2400 is a good=20 time. I have been working W stns on 160m at times as early as 2000 utc, stil= l=20 daylight over ur way.

I can have another bash tonight and if any=20= others=20 want to participate please do so.

I will TX on 502.57 khz and use QRS3 and th= en speed=20 up if necessary. A good USA freq would be around 508.5 khz which is perfectl= y=20 clear here.

If all W stns intererested in a TR QSO= =20 work around this freq with a little separation I would be able to see=20= who=20 is about, and QSO accordingly.

QRU now and agn tnx and looking forward to=20= another=20 QSO soon.I will have to ck the QRB.

de mal/g3kev/IO94SH

------=_NextPart_000_01A7_01C96807.C02AA5D0--