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 w1K9qJI2008662 for ; Tue, 20 Feb 2018 10:52:20 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eo4WF-0003hU-01 for rs_out_1@blacksheep.org; Tue, 20 Feb 2018 09:47:27 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eo4WE-0003hL-FO for rsgb_lf_group@blacksheep.org; Tue, 20 Feb 2018 09:47:26 +0000 Received: from know-smtprelay-omc-9.server.virginmedia.net ([80.0.253.73]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eo4WB-0003m2-Lx for rsgb_lf_group@blacksheep.org; Tue, 20 Feb 2018 09:47:25 +0000 Received: from [192.168.1.2] ([82.31.180.39]) by cmsmtp with ESMTP id o4W7eDF1eYHrXo4W9ephgx; Tue, 20 Feb 2018 09:47:21 +0000 X-DKIM-Result: Domain=ntlworld.com Result=Signature OK X-Originating-IP: [82.31.180.39] X-Authenticated-User: X-Spam: 0 X-Authority: v=2.3 cv=NJ77BXyg c=1 sm=1 tr=0 a=sVtWtjZQCe36+A3m2HleAg==:117 a=sVtWtjZQCe36+A3m2HleAg==:17 a=8nJEP1OIZ-IA:10 a=x7bEGLp0ZPQA:10 a=F3M5lZpKAAAA:8 a=79bTZUIPAAAA:8 a=fYSQNe0VFg09nxxOIT8A:9 a=wPNLvfGTeEIA:10 a=slCku8JSH3TyizEDQ3pD:22 a=ISTIEq08UyDe2sYTrcO4:22 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ntlworld.com; s=meg.feb2017; t=1519120041; bh=mmVBi1Lwl9z8V3038BAYdd2tWYYHfUpGc3my+Q8Nlac=; h=From:To:Date:Subject:Reply-to:In-reply-to:References; b=SvER/5i/JEXMNECMkM95DUhYQj5mEaRL7OyRzwPUeUu1BjXhZECTdFL2C7Azhs32I 2PaDlh+GGvfrLrayy5N9RyKGvjrRNO3UAOdN8GGi8AyHYTLATkGHVR9QEZDZ5tP1G5 sohALwaZi1cDl2nsM98ip2MwcSjJT0uh46KW81wh85PUDUetSsHM+Z7SJb5Z27jd6j CmChw41oGTfKvd/0JIsdiJ0GxlL49KoFChdcmCIiFPqpx5UsNz27dnR2LQMMrRop86 8vtAjbWUYduJgENXehWoCe44eJVitPP/qyoYyldsNGiCYJL0y6Sen2QfQHOloQ2twX 63CEFZNiql7jw== From: "Mike Dennison" To: rsgb_lf_group@blacksheep.org Date: Tue, 20 Feb 2018 09:47:19 -0000 MIME-Version: 1.0 Message-ID: <5A8BEEA7.20965.19752596@mike.dennison.ntlworld.com> In-reply-to: <3E3B283424E94B879955DC6E3D55B533@Rob64PC> References: <161aa835884-c88-4ea39@webjas-vab214.srv.aolmail.net>, <3E3B283424E94B879955DC6E3D55B533@Rob64PC> X-mailer: Pegasus Mail for Windows (4.72.572) Content-description: Mail message body X-CMAE-Envelope: MS4wfGreBTni678J8H0ToNt3qh9Jrxiw6vtlwqaVkQTYz+6cCB7umPNpTyuWZRn/mvLifHgEs9lPWpETLtVvnWhd2cHT8iFDdM6zAYVOeFJrDusY37W67vSz 3blgKBzGdyZ09xODLY4nFTuuabjSsLi69/G5DojJ903Aur0JgppOyDSqEw2kyTfo05pb5h2LJKVhKw== X-Spam-Score: 0.8 (/) 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: I will be monitoring. In fact I have been running WSPR-X (the necessary software for receiving WSPR-15) for a few days now. The computer uses Win-10 and the software runs reliably, but I am not sure if I originally set it up in compatibility mode. In fact I am able to run WSJT-X (for WSPR-2), Opera and WSPR-X at the same time. [...] Content analysis details: (0.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 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] 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 1bc6486c2865e7dc2ff7578e6d7fc226 Subject: Re: LF: Re: Wow, busy busy on 136!! Content-type: text/plain; charset=ISO-8859-1 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from Quoted-printable to 8bit by klubnl.pl id w1K9qJI2008662 I will be monitoring. In fact I have been running WSPR-X (the necessary software for receiving WSPR-15) for a few days now. The computer uses Win-10 and the software runs reliably, but I am not sure if I originally set it up in compatibility mode. In fact I am able to run WSJT-X (for WSPR-2), Opera and WSPR-X at the same time. Mike, G3XDV ========== > 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). > > 73, > Rob - K3RWR > > > > From: Markus Vester > 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 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üngliche Mitteilung----- > 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 > available. 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 watching the antenna > impedance closely enough. > > Hopefully in a couple of weeks there will be a somewhat bigger > amplifier here to play with. :-) > > 73, > Paul > > > On 02/18/2018 12:10 PM, John Bruce McCreath wrote: > > > > > >> The problem is Windows 10, not WSPR-X. Here it runs for weeks on > >> Win7. > >> > >> 73, Stefan > > > > I´ve found WSPR-X to be quite stable in my WinXP box as well. > > > > 73, J.B., VE3EAR > >