[wsjt-devel] WSPR Updates Linux / FreeBSD

2014-12-21 Thread ki7mt
Hello All, Following dianora's commits to upgrade WSPR for FreeBSD ( which was badly needed !!), I had to make a few changes for Linux, some were already in the pipeline, others were to fix some syntax issues that caused configure to fail. Details of the changes will be in the commit log, but want

[wsjt-devel] WSJT-X Public Beta

2014-12-21 Thread Jim Brown
Hi Guys, Mostly I just lurk here, but now I've got some input for you. I've been using WSJT-X 1.3 for a year or so, mostly 6M and 160M. Tonight, I loaded the posted public beta, 1.4 and fired it up. I'm using a K3 with a hardware serial port (Quatech 2-port PCMCIA card) in a T61 Thinkpad runn

Re: [wsjt-devel] WSPR crashes, error starting rx thread

2014-12-21 Thread Alan VK2ZIW
Hi Greg and all, Can we please focus on the "crash " problem? WSPR runs perfectly fine for 10+ hours then crashes: spawning new thread: Resource temporarily unavailable Error starting rx thread     11 The "pillow" issue is resolved. Just do:

Re: [wsjt-devel] WSPR crashes, error starting rx thread

2014-12-21 Thread ki7mt
Hi Alan, Your package situation is not resolved, not by any stretch of the imagination, but if you want to consider it good that's your call. I would take Joe's advice ( given 2 maybe even 3 times now ), run WSPR0, see it if fails, cut the problem in half, or start isolating possibilities. You c

[wsjt-devel] WSPR Crash on ARM, was : Re: WSPR crashes, error starting rx thread

2014-12-21 Thread Bill Somerville
On 21/12/2014 11:01, Alan VK2ZIW wrote: Hi Greg and all, Hi Alan, Can we please focus on the "crash " problem? WSPR runs perfectly fine for 10+ hours then crashes: spawning new thread: Resource temporarily unavailable Error starting rx thread 11 I don't know the WSPR code base apart from a c

Re: [wsjt-devel] WSPR Updates Linux / FreeBSD

2014-12-21 Thread Diane Bruce
On Sun, Dec 21, 2014 at 01:12:29AM -0700, ki7mt wrote: > Hello All, > > Following dianora's commits to upgrade WSPR for FreeBSD ( which was > badly needed !!), I had to make a few changes for Linux, some were > already in the pipeline, others were to fix some syntax issues that > caused configure