To: | [email protected] |
---|---|
Subject: | Re: LF: Wow, busy busy on 136!! |
From: | N1BUG <[email protected]> |
Date: | Sun, 18 Feb 2018 12:39:04 -0500 |
In-reply-to: | <[email protected]> |
References: | <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> |
Reply-to: | [email protected] |
Sender: | [email protected] |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 |
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, StefanI’ve found WSPR-X to be quite stable in my WinXP box as well. 73, J.B., VE3EAR |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: LF: Wow, busy busy on 136!!, John Bruce McCreath |
---|---|
Next by Date: | Re: LF: Wow, busy busy on 136!!, Markus Vester |
Previous by Thread: | Re: LF: Wow, busy busy on 136!!, John Bruce McCreath |
Next by Thread: | Re: LF: Wow, busy busy on 136!!, Markus Vester |
Indexes: | [Date] [Thread] [Top] [All Lists] |