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

[Andy Talbot <andy.g4jnt@gmail.com>]

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 <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
==========

> Tnx to all for the spots and comments on the recent 136 activity!
>
> I´ll 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üngliche 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´ve found WSPR-X to be quite stable in my WinXP box as well.
> >
> > 73, J.B., VE3EAR
>
>