To: rsgb_lf_group@blacksheep.org
References: <398020934.20180218013459@gmail.com>
 <161a806502c-c90-2da46@webjas-vaa192.srv.aolmail.net>
 <431409c2-605d-ab52-3ea1-99c770617e8b@n1bug.com> <5A898C3A.3020405@posteo.de>
 <8585b760-e9e6-c101-0c71-9aa0bb353f66@n1bug.com> <5A89AF0B.1050906@posteo.de>
 <28A1224F-3FE3-4852-9B75-CA997EA4C37A@hurontel.on.ca>
From: N1BUG <paul@n1bug.com>
Message-ID: <58415c7f-cd79-2a4a-a95d-a724f2a31051@n1bug.com>
Date: Sun, 18 Feb 2018 12:39:04 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <28A1224F-3FE3-4852-9B75-CA997EA4C37A@hurontel.on.ca>
Content-Language: en-US
Subject: Re: LF: Wow, busy busy on 136!!
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

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