Return to KLUBNL.PL main page

rsgb_lf_group
[Top] [All Lists]

Re: LF: Wow, busy busy on 136!!

To: [email protected]
Subject: Re: LF: Wow, busy busy on 136!!
From: Markus Vester <[email protected]>
Date: Sun, 18 Feb 2018 15:03:10 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1518984190; bh=GxV/m946BqFllMSiqoRjeWLH1NqC37orGCuDgDkIoMI=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=kxGlWOc6NtBSx3tVj30uLOpqttz73XcaO/fQxcmDVxBReFtEsn8Ho7uuO5Fr5Bw7s XbeMFvBP5pBFMgizmmpMQW0hm+QzXQepJZOafU6B/miXZrp0ILNw9JujwUt4sw1t4Q RwAmJdHq+9M134NfFWJr2S/hwO1M/G28DOVZSRl0=
In-reply-to: <[email protected]>
Reply-to: [email protected]
Sender: [email protected]
> 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 <[email protected]>
An: rsgb_lf_group <[email protected]>
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

<Prev in Thread] Current Thread [Next in Thread>