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 w1IK9O0M002362 for ; Sun, 18 Feb 2018 21:09:25 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1enVBE-0007go-Uw for rs_out_1@blacksheep.org; Sun, 18 Feb 2018 20:03:24 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1enVB6-0007gf-PU for rsgb_lf_group@blacksheep.org; Sun, 18 Feb 2018 20:03:16 +0000 Received: from omr-a004e.mx.aol.com ([204.29.186.52]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from ) id 1enVB3-00043t-D4 for rsgb_lf_group@blacksheep.org; Sun, 18 Feb 2018 20:03:15 +0000 Received: from mtaomg-aad02.mx.aol.com (mtaomg-aad02.mx.aol.com [172.26.127.228]) by omr-a004e.mx.aol.com (Outbound Mail Relay) with ESMTP id ACC303800098 for ; Sun, 18 Feb 2018 15:03:10 -0500 (EST) Received: from core-acc01f.mail.aol.com (core-acc01.mail.aol.com [172.26.125.11]) by mtaomg-aad02.mx.aol.com (OMAG/Core Interface) with ESMTP id 37DCA38000094 for ; Sun, 18 Feb 2018 15:03:10 -0500 (EST) Received: from 188.194.222.230 by webjas-vab214.srv.aolmail.net (10.96.18.217) with HTTP (WebMailUI); Sun, 18 Feb 2018 15:03:10 -0500 Date: Sun, 18 Feb 2018 15:03:10 -0500 From: Markus Vester To: rsgb_lf_group@blacksheep.org Message-Id: <161aa835884-c88-4ea39@webjas-vab214.srv.aolmail.net> In-Reply-To: <58415c7f-cd79-2a4a-a95d-a724f2a31051@n1bug.com> MIME-Version: 1.0 X-MB-Message-Source: WebUI X-MB-Message-Type: User X-Mailer: JAS STD X-Originating-IP: [188.194.222.230] x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1518984190; bh=GxV/m946BqFllMSiqoRjeWLH1NqC37orGCuDgDkIoMI=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=kxGlWOc6NtBSx3tVj30uLOpqttz73XcaO/fQxcmDVxBReFtEsn8Ho7uuO5Fr5Bw7s XbeMFvBP5pBFMgizmmpMQW0hm+QzXQepJZOafU6B/miXZrp0ILNw9JujwUt4sw1t4Q RwAmJdHq+9M134NfFWJr2S/hwO1M/G28DOVZSRl0= x-aol-sid: 3039ac1a7fe45a89dbfe79ca 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: > 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. [...] Content analysis details: (0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.6 URIBL_SBL Contains an URL's NS IP listed in the Spamhaus SBL blocklist [URIs: n1bug.com] 0.1 URIBL_SBL_A Contains URL's A record listed in the Spamhaus SBL blocklist [URIs: n1bug.com] 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 20fb97b64762a0bd80c12a4b2f6724b0 Subject: Re: LF: Wow, busy busy on 136!! Content-Type: multipart/alternative; boundary="----=_Part_415971_229006518.1518984190084" 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 ------=_Part_415971_229006518.1518984190084 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > PS: Still running WSPR v0.8 r3058 here because this version can also do w= spr-15 mode. Running nicely under good old XP here, no crashes. There seem to be two min= or peculiarities - WSPRx occasionally writes wav and c2 files to the \save folder even thoug= h 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.ou= t file. 73, Markus PS Everyone keeps telling me that XP is no longer safe. But I have to say t= hat 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 ------=_Part_415971_229006518.1518984190084 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
> 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 sho= uldn't, requiring occasional deleting.
- Uploads someti= mes stall completely after detection of an invalid callsign. This can be fi= xed by manually removing the offending line in the wsprd.out file.

73, Markus

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




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

So the = problem is Windows 10. Unfortunately that is all I have
ava= ilable. Even if I had an older version of Windows to install, it
would take days to get everything configured again.
I will probably try transmitting WSPR-15 and DFCW after a bit= more
time testing the amplifier on WSPR-2. I did have one = FET die night
before last but that was my fault for not wat= ching the antenna
impedance closely enough.
=
Hopefully in a couple of weeks there will be a somewhat big= ger
amplifier here to play with. :-)

73,
Paul


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

------=_Part_415971_229006518.1518984190084--