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 w1KAJEYp008796 for ; Tue, 20 Feb 2018 11:19:15 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eo4wS-0003oY-2F for rs_out_1@blacksheep.org; Tue, 20 Feb 2018 10:14:32 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eo4wN-0003oP-8F for rsgb_lf_group@blacksheep.org; Tue, 20 Feb 2018 10:14:27 +0000 Received: from mail-wr0-x236.google.com ([2a00:1450:400c:c0c::236]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eo4wK-0003xm-4p for rsgb_lf_group@blacksheep.org; Tue, 20 Feb 2018 10:14:25 +0000 Received: by mail-wr0-x236.google.com with SMTP id p104so11351476wrc.12 for ; Tue, 20 Feb 2018 02:14:23 -0800 (PST) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=BZkZUtZFC58BC4i+J/0bI88iB1DnSI5RnAuycEurgJs=; b=TVrq/LUtsnQ4vIsQZS4nkFLEd9hwnoWEVSrD0xC2VIohGymig8yANOn5mpSZbw2mRB Z0chQfdUiSuROoD955NMZzCsnzbUyTbrCErsW87K9x0dl7TeVxA+5bPIU/hkjGZkdaeZ fhdH7hn3VdeULODDea2nmo5DpKkv2sX/yWTKKzbeJ+2Vn/QmfWR8cPqEy2igefgEIYKm /MsRfoWOoL0eK6TRe5mLgbfbGezh5r5zhoTt7QZpC5u49V72+0xAHDP4YxfIqawc2Urq akEW6KRBOoGyy0Ka16AyHYi6y+xFKz6nl93XfNYvMnJj07sEoqjrUf7EFjIpCvgEUHyi eN+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=BZkZUtZFC58BC4i+J/0bI88iB1DnSI5RnAuycEurgJs=; b=B2IGqloLTPe50HjMD/2pa0mbMwIP0mer2FCNrgjtjaQaaX58sxzGTf4ARnvCqfqXL2 N0C6a0jPlfuQJXP1bHJwA+rfvyMA+ZhpY71CRsTaPTwGq/x3Aja076N+Mfa3+XMeEf7E MFbv7oZH63qarZAi9xAOkx6sTd4gOV7scYmU57qJNs+7aMH92YoyXU1GtRFUNi2KXHcS 5YmOy0UrqtSYc+F9ClhoYocrk+9UMo3NL1tFzXg0hqr3wOkndjvlnBUkAbof29Rz2+UL 7is5rZhspx0N0r9d0QMWNO5zXz7X9F3gyYpj4P20EgNfgH/WtbwF+hEfRAv82NNvIVpa q5AA== X-Gm-Message-State: APf1xPC4yXb0WIR+bUrNQcg5bw18SgguVEfKJrLEV2+KBSynQ7zmZFJY MeyErZhZK0I5G16/RkuarWITNuH081lwWI8aucWe1Q== X-Google-Smtp-Source: AH8x227td/quUzI8kivn9BeWeauU6N51duxVNRDnXscRu/HG8+efkf+Ay0FRuQOO11RxPd7sWauWw+BhHoVmIHL2fUU= X-Received: by 10.80.194.89 with SMTP id t25mr16544577edf.11.1519121662969; Tue, 20 Feb 2018 02:14:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.179.204 with HTTP; Tue, 20 Feb 2018 02:14:22 -0800 (PST) In-Reply-To: <5A8BEEA7.20965.19752596@mike.dennison.ntlworld.com> References: <161aa835884-c88-4ea39@webjas-vab214.srv.aolmail.net> <3E3B283424E94B879955DC6E3D55B533@Rob64PC> <5A8BEEA7.20965.19752596@mike.dennison.ntlworld.com> From: Andy Talbot Date: Tue, 20 Feb 2018 10:14:22 +0000 Message-ID: To: LineOne 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: After reading this, I installed WSPR-X on my new Win-10 notebook. It didn't work in "normal" mode. But when modified to run in XP compatibilty mode, worked fine. I ran it in parallel with WSJT-X for a bit last night on 7MHz, and, as was stated here a while back, it wasn't quite as good. Taking longer to decode than WSJT-X did, and also missing a couple of stations that WSJT-X managed to get. And they weren't necessarily the weak ones. [...] Content analysis details: (0.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (andy.g4jnt[at]gmail.com) 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 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: f6bad70c4aa77b0bf5528aff34072d8d Subject: Re: LF: Re: Wow, busy busy on 136!! Content-Type: multipart/alternative; boundary="94eb2c1cc990178e880565a213d7" 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=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 --94eb2c1cc990178e880565a213d7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable After reading this, I installed WSPR-X on my new Win-10 notebook. It didn't work in "normal" mode. But when modified to run in XP compatibilty mode, worked fine. I ran it in parallel with WSJT-X for a bit last night on 7MHz, and, as was stated here a while back, it wasn't quite as good. Taking longer to decode than WSJT-X did, and also missing a couple of stations that WSJT-X managed to get. And they weren't necessarily the weak ones. Andy G4JNT On 20 February 2018 at 09:47, Mike Dennison wrote: > 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 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > Tnx to all for the spots and comments on the recent 136 activity! > > > > I=C2=B4ll 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=C3=BCngliche 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=C2=B4ve found WSPR-X to be quite stable in my WinXP box as well. > > > > > > 73, J.B., VE3EAR > > > > > > > > --94eb2c1cc990178e880565a213d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
After reading this, I installed WSPR-X on my new Win-10 no= tebook.=C2=A0 It didn't work in "normal" mode.=C2=A0 But when= modified to run in XP compatibilty mode, worked fine.

I= ran it in parallel with WSJT-X for a bit last night on 7MHz, and, as was s= tated here a while back, it wasn't quite as good.=C2=A0 Taking longer t= o decode than WSJT-X did, and also missing a couple of stations that WSJT-X= managed to get.=C2=A0 And they weren't necessarily the weak ones.

Andy=C2=A0 G4JNT

On 20 February 2018 at 09:47, Mike Dennison= <mike.dennison@ntlworld.com> wrote:
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

> Tnx to all for the spots and comments on the recent 136 activity!
>
> I=C2=B4ll be running WSPR-15 for the next week or so if it continues t= o
> run satisfactorily under the XP compatibility mode.=C2=A0 Even sequenc= e,
> 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@blac= ksheep.org
> Subject: Re: LF: Wow, busy busy on 136!!
>
> > PS: Still running WSPR v0.8 r3058 here because this version can a= lso
> > 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<= br> > say that without those updates, it seems to be better and more stable<= br> > than ever...
>
>
>
>
> -----Urspr=C3=BCngliche Mitteilung-----
> Von: N1BUG <paul@n1bug.com>= ;
> An: rsgb_lf_group <= rsgb_lf_group@blacksheep.org>
> 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=C2=B4ve found WSPR-X to be quite stable in my WinXP box as well= .
> >
> > 73, J.B., VE3EAR
>
>




--94eb2c1cc990178e880565a213d7--