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 w1JMTgVn006719 for ; Mon, 19 Feb 2018 23:29:45 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ents0-0002h1-AR for rs_out_1@blacksheep.org; Mon, 19 Feb 2018 22:25:12 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1entrt-0002gs-KO for rsgb_lf_group@blacksheep.org; Mon, 19 Feb 2018 22:25:05 +0000 Received: from omr-m003e.mx.aol.com ([204.29.186.3]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from ) id 1entrq-0001lC-9K for rsgb_lf_group@blacksheep.org; Mon, 19 Feb 2018 22:25:04 +0000 Received: from mtaomg-aah02.mx.aol.com (mtaomg-aah02.mx.aol.com [172.27.1.144]) by omr-m003e.mx.aol.com (Outbound Mail Relay) with ESMTP id AEA6D3800042 for ; Mon, 19 Feb 2018 17:25:00 -0500 (EST) Received: from core-ace05e.mail.aol.com (core-ace05.mail.aol.com [172.27.23.5]) by mtaomg-aah02.mx.aol.com (OMAG/Core Interface) with ESMTP id 717EC38000084 for ; Mon, 19 Feb 2018 17:25:00 -0500 (EST) Received: from 188.194.222.230 by webjas-vae034.srv.aolmail.net (10.96.23.37) with HTTP (WebMailUI); Mon, 19 Feb 2018 17:24:59 -0500 Date: Mon, 19 Feb 2018 17:25:00 -0500 From: Markus Vester To: rsgb_lf_group@blacksheep.org Message-Id: <161b02b8b60-c8c-319b4@webjas-vae034.srv.aolmail.net> In-Reply-To: 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=1519079100; bh=kjnehPmgixw9pFiUv2hKB//lVrsj2JFys6jjTYMuF88=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=BVd7rUwxfbuGetFWXpZBW5KTQ7Zve6FQkTZYGsMpWtTtSz4GMB3HzvaiCTvh4BUnA o2JzsAWEIHbmes7v0gH7sRBKc6ynWcU5WnUos7WVBMacUAm5zdFlDl20oIvFETl+gl IM+pBtZvoTem974rgfrs/K2JZcNiOgkW65YQjXIw= x-aol-sid: 3039ac1b01905a8b4ebc24fb 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: Also monitoring -15 from here tonight. > Aloha Lucky you ;-) 73 and good DX, Markus (DF6NM) [...] 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.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: 571129b349252c35b2bc09d7a1c6d0f3 Subject: Re: LF: Re: Wow, busy busy on 136!! Content-Type: multipart/alternative; boundary="----=_Part_262096_1211325934.1519079099231" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.8 required=5.0 tests=HTML_30_40,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_262096_1211325934.1519079099231 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Also monitoring -15 from here tonight. > Aloha Lucky you ;-) 73 and good DX, Markus (DF6NM) -----Urspr=C3=BCngliche Mitteilung-----=20 Von: Laurence KL7 L An: rsgb_lf_group Verschickt: Mo, 19. Feb 2018 23:09 Betreff: Re: LF: Re: Wow, busy busy on 136!! Hi Rob - ive put on a wsprx15 137 instance on the rx in AK - KL7L on till i= t falls over - will be subject to 137/475 tx qrm Aloha Laurence in kh6 today On Feb 19, 2018, at 9:32 AM, Rob Renoud wrote: Tnx to all for the spots and comments on the recent 136 activity! =20 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% dut= y cycle, 612 window frequency (137 612 Hz). =20 73, Rob - K3RWR =20 =20 =20 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!! =20 =20 > 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 mi= nor peculiarities - WSPRx occasionally writes wav and c2 files to the \save folder even thou= gh it shouldn't, requiring occasional deleting. - Uploads sometimes stall completely after detection of an invalid callsig= n. This can be fixed by manually removing the offending line in the wsprd.o= ut 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 ------=_Part_262096_1211325934.1519079099231 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Also monitoring -15 from here  tonight.=

> Aloha
Lucky you ;-)

73 and g= ood DX,
Markus (DF6NM)

-----Urspr=C3=BCngliche Mittei= lung-----
Von: Laurence KL7 L <hellozerohellozero@hotmai= l.com>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org= >
Verschickt: Mo, 19. Feb 2018 23:09
Betre= ff: Re: LF: Re: Wow, busy busy on 136!!

Hi Rob - ive put on a wsprx15 137 instance on the rx in AK= - KL7L on till it falls  over - will be subject to 137/475 tx qrm

Aloha
Laurence in kh6 today



On Feb 19, 2018, at 9:32 AM, Rob Renoud <k3rwr@= md.metrocast.net> wrote:

 
Sent: Sunday, February 18, 2018 3:03 PM=
Subject: Re: LF: Wow, busy busy on 136!= !
 
> PS: Still running WSPR v0.8 r3058 here because this version can also d= o wspr-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-----
Von: N1BUG <paul@n1bug.com>
An: rsgb_lf_group <rsgb_lf_group@blackshe= ep.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 W= in7.
>>
>> 73, Stefan
>
> I=E2=80=99ve found WSPR-X to be quite stable in my WinXP box as well.<= br abp=3D"712"> >
> 73, J.B., VE3EAR

------=_Part_262096_1211325934.1519079099231--