Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-df01.r1000.mx.aol.com (Internet Inbound) with ESMTP id 52F16380000E8; Thu, 27 Oct 2011 13:31:46 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1RJTmR-0000qy-U0 for rs_out_1@blacksheep.org; Thu, 27 Oct 2011 18:30:15 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1RJTmR-0000qp-ET for rsgb_lf_group@blacksheep.org; Thu, 27 Oct 2011 18:30:15 +0100 Received: from relay2.uni-heidelberg.de ([129.206.210.211]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1RJTmQ-0004mm-8n for rsgb_lf_group@blacksheep.org; Thu, 27 Oct 2011 18:30:15 +0100 Received: from freitag.iup.uni-heidelberg.de (freitag.iup.uni-heidelberg.de [129.206.29.204]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id p9RHUDIp022709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 27 Oct 2011 19:30:13 +0200 Received: from [129.206.22.206] (pc206.iup.uni-heidelberg.de [129.206.22.206]) by freitag.iup.uni-heidelberg.de (8.12.11.20060308/8.11.2) with ESMTP id p9RHUDIR029053 for ; Thu, 27 Oct 2011 19:30:13 +0200 Message-ID: <4EA994E9.10406@iup.uni-heidelberg.de> Date: Thu, 27 Oct 2011 19:29:13 +0200 From: =?ISO-8859-1?Q?Stefan_Sch=E4fer?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <4EA925BE.4030306@iup.uni-heidelberg.de> <003301cc94c5$6a6083c0$0401a8c0@xphd97xgq27nyf> In-Reply-To: <003301cc94c5$6a6083c0$0401a8c0@xphd97xgq27nyf> X-Spam-Score: 1.4 (+) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001,RATWARE_GECKO_BUILD=1.426 Subject: Re: LF: vo1na 27-10.jpg Content-Type: multipart/alternative; boundary="------------080400040409040805020208" 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_40_50,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-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:505693248:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d40d54ea995816707 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. --------------080400040409040805020208 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by relay2.uni-heidelberg.de id p9RHUDIp022709 Mal Am 27.10.2011 18:28, schrieb mal hamilton: > Stefan > The majority of signals on LF es MF are suitable for a QSO but the=20 > present culture seems to favour BEACONS, QRS MODE when it is not=20 > necessary and QSL via Internet. > In the beginning it was all CW QSO mode and it worked FB. > I do not bother any more because it is a waste of time=20 > listening/watching useless repeative part callsigns. > It has all been done before and better so what are current operators=20 > trying to achieve. What are you doing on HF that wasn't done before? > My suggestion is to get back to CW QSO mode Have thought the same, some days ago. I will try to move activity to CW=20 a bit more, at least on the weekend... 73, Stefan > , use QRS only under vy poor propagation condx if you think it helps. > Use LF es MF like all the other bands, HF es VHF where CW is the norm,=20 > SSB as appropriate and likewise data modes. > 73 de mal/g3kev > > ----- Original Message ----- > *From:* Stefan Sch=E4fer > *To:* rsgb_lf_group@blacksheep.org > > *Sent:* Thursday, October 27, 2011 9:34 AM > *Subject:* Re: LF: vo1na 27-10.jpg > > Hi Joe, LF, > > Your signal in a QRSS-10 window. Would be suitable for a QSO :-) > http://dl.dropbox.com/u/19882028/LF/10_402283.jpg > > 73, Stefan/DK7FC > > Am 27.10.2011 10:35, schrieb henny van elst: >> Gm LF, >> Capture vo1na, >> henny pa3cpm >> 73's >> Het bericht kan nu met het volgende bijlagen of koppelingen >> worden verzonden: >> vo1na 27-10.jpg >> >> Opmerking: Sommige e-mailprogramma's staan ter beveiliging tegen >> virussen het verzenden of ontvangen van bepaalde bestandsbijlagen >> niet toe. Controleer de beveiligingsinstellingen voor uw e-mail >> als u wilt weten hoe bijlagen worden afgehandeld. > --------------080400040409040805020208 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mal

Am 27.10.2011 18:28, schrieb mal hamilton:
Stefan
The majority of signals on LF es MF are suitable for a QSO but the present culture seems to favour BEACONS, QRS MODE when it is not necessary and QSL via Internet.
In the beginning it was all CW QSO mode and it worked FB.
I do not bother any more because it is a waste of time listening/watching useless repeative part callsigns.
It has all been done before and better so what are current operators trying to achieve.
What are you doing on HF that wasn't done before?


My suggestion is to get back to CW QSO mode
Have thought the same, some days ago. I will try to move activity to CW a bit more, at least on the weekend...


73, Stefan


, use QRS only under vy poor propagation condx if you think it helps.
Use LF es MF like all the other bands, HF es VHF where CW is the norm, SSB as appropriate and likewise data modes.
73 de mal/g3kev
 
 
----- Original Message -----
Sent: Thursday, October 27, 2011 9:34 AM
Subject: Re: LF: vo1na 27-10.jpg

Hi Joe, LF,

Your signal in a QRSS-10 window. Would be suitable for a QSO :-)
http://dl.dropbox.com/u/19882028/LF/10_402283.jpg

73, Stefan/DK7FC

Am 27.10.2011 10:35, schrieb henny van elst:
Gm LF,
Capture vo1na,
henny pa3cpm
73's
Het bericht kan nu met het volgende bijlagen of koppelingen worden verzonden:
vo1na 27-10.jpg

Opmerking: Sommige e-mailprogramma's staan ter beveiliging tegen virussen het verzenden of ontvangen van bepaalde bestandsbijlagen niet toe. Controleer de beveiligingsinstellingen voor uw e-mail als u wilt weten hoe bijlagen worden afgehandeld.
--------------080400040409040805020208--