Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w1JJZuFM006234 for ; Mon, 19 Feb 2018 20:35:57 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1enr8k-00024c-4J for rs_out_1@blacksheep.org; Mon, 19 Feb 2018 19:30:18 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1enr8h-00024T-7p for rsgb_lf_group@blacksheep.org; Mon, 19 Feb 2018 19:30:15 +0000 Received: from cust-smtp-lb.metrocast.net ([65.175.128.166] helo=proofpoint-cluster.metrocast.net) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1enr8e-00011S-95 for rsgb_lf_group@blacksheep.org; Mon, 19 Feb 2018 19:30:13 +0000 Received: from Rob64PC (d-208-90-143-11.cpe.metrocast.net [208.90.143.11]) by grape.metrocast.net (8.14.7/8.14.4) with SMTP id w1JJU7T0049701 for ; Mon, 19 Feb 2018 19:30:07 GMT Message-ID: <3E3B283424E94B879955DC6E3D55B533@Rob64PC> From: "Rob Renoud" To: References: <161aa835884-c88-4ea39@webjas-vab214.srv.aolmail.net> In-Reply-To: <161aa835884-c88-4ea39@webjas-vab214.srv.aolmail.net> Date: Mon, 19 Feb 2018 14:30:06 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3528.331 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.19.17,1.0.8,0.0.0000 definitions=2018-02-19_08:2018-02-19,2018-02-19,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1603290000 definitions=main-1802190241 X-Spam-Score: 0.7 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Tnx to all for the spots and comments on the recent 136 activity! I’ll be running WSPR-15 for the next week or so if it continues to run satisfactorily under the XP compatibility mode. Even sequence, 50% duty cycle, 612 window frequency (137 612 Hz). [...] Content analysis details: (0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.1 URIBL_SBL_A Contains URL's A record listed in the Spamhaus SBL blocklist [URIs: n1bug.com] 0.6 URIBL_SBL Contains an URL's NS IP listed in the Spamhaus SBL blocklist [URIs: n1bug.com] X-Scan-Signature: 13ce2d45c6831942db3d21680606cc2e Subject: LF: Re: Wow, busy busy on 136!! Content-Type: multipart/alternative; boundary="----=_NextPart_000_00F9_01D3A98E.23618480" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_OUTLOOK_NAME 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 This is a multi-part message in MIME format. ------=_NextPart_000_00F9_01D3A98E.23618480 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Tnx to all for the spots and comments on the recent 136 activity! I=E2=80=99ll be running WSPR-15 for the next week or so if it continues = to run satisfactorily under the XP compatibility mode. Even sequence, = 50% duty cycle, 612 window frequency (137 612 Hz). 73, Rob - K3RWR From: Markus Vester=20 Sent: Sunday, February 18, 2018 3:03 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: Wow, busy busy on 136!! > PS: Still running WSPR v0.8 r3058 here because this version can also = do wspr-15 mode. Running nicely under good old XP here, no crashes. There seem to be two = minor peculiarities - WSPRx occasionally writes wav and c2 files to the \save folder even = though it shouldn't, requiring occasional deleting. - Uploads sometimes stall completely after detection of an invalid = callsign. This can be fixed by manually removing the offending line in = the wsprd.out file. 73, Markus PS Everyone keeps telling me that XP is no longer safe. But I have to = say that without those updates, it seems to be better and more stable = than ever... -----Urspr=C3=BCngliche Mitteilung-----=20 Von: N1BUG An: rsgb_lf_group Verschickt: So, 18. Feb 2018 18:43 Betreff: Re: LF: Wow, busy busy on 136!! OK Stefan, Bill, So the problem is Windows 10. Unfortunately that is all I have=20 available. Even if I had an older version of Windows to install, it=20 would take days to get everything configured again. I will probably try transmitting WSPR-15 and DFCW after a bit more=20 time testing the amplifier on WSPR-2. I did have one FET die night=20 before last but that was my fault for not watching the antenna=20 impedance closely enough. Hopefully in a couple of weeks there will be a somewhat bigger=20 amplifier here to play with. :-) 73, Paul On 02/18/2018 12:10 PM, John Bruce McCreath wrote: >=20 >=20 >> The problem is Windows 10, not WSPR-X. Here it runs for weeks on = Win7. >> >> 73, Stefan >=20 > I=E2=80=99ve found WSPR-X to be quite stable in my WinXP box as well. >=20 > 73, J.B., VE3EAR ------=_NextPart_000_00F9_01D3A98E.23618480 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Tnx to all for the spots and comments on the recent 136 = activity!
 
I=E2=80=99ll be running WSPR-15 for the next week or so if it = continues to run=20 satisfactorily under the XP compatibility mode.  Even sequence, 50% = duty=20 cycle, 612 window frequency (137 612 Hz).
 
73,
Rob - K3RWR
 
 
 
Sent: Sunday, February 18, 2018 3:03 PM
To: rsgb_lf_group@blacksheep.org =
Subject: Re: LF: Wow, busy busy on 136!!
 
> PS: Still running WSPR v0.8 r3058 here because this = version can=20 also do wspr-15 mode.

Running nicely = under good old=20 XP here, no crashes. There seem to be two minor peculiarities
-=20 WSPRx occasionally writes wav and c2 files to the \save folder even = though it=20 shouldn't, requiring occasional deleting.
- Uploads = sometimes stall=20 completely after detection of an invalid callsign. This can be fixed by = manually=20 removing the offending line in the wsprd.out file.
73, Markus

PS Everyone keeps = telling me=20 that XP is no longer safe. But I have to say that without those updates, = it=20 seems to be better and more stable than ever...



-----Urspr=C3=BCngliche = Mitteilung----- Von: N1BUG <paul@n1bug.com>
An: = rsgb_lf_group=20 <rsgb_lf_group@blacksheep.org>
Verschickt: So, 18. = Feb 2018=20 18:43
Betreff: Re: LF: Wow, busy busy on 136!!
OK Stefan, Bill,

So the = problem is=20 Windows 10. Unfortunately that is all I have
available. = Even if I=20 had an older version of Windows to install, it
would = take days to=20 get everything configured again.

I will = probably try=20 transmitting WSPR-15 and DFCW after a bit more
time = testing the=20 amplifier on WSPR-2. I did have one FET die night
before = last but=20 that was my fault for not watching the antenna
impedance = closely=20 enough.

Hopefully in a couple of weeks = there will be=20 a somewhat bigger
amplifier here to play with. :-)
73,
Paul

On 02/18/2018 12:10 PM, John Bruce McCreath wrote:
>=20
>
>> The problem is Windows 10, = not WSPR-X.=20 Here it runs for weeks on Win7.
>>
>> 73,=20 Stefan
>
> I=E2=80=99ve found = WSPR-X to be quite stable=20 in my WinXP box as well.
>
> 73, = J.B.,=20 VE3EAR
------=_NextPart_000_00F9_01D3A98E.23618480--