Re: [wsjt-devel] 4000 PSKReporter User

Hi Mike, Just to add a bit to this; as of ~0200 UTC April month to date, approx 3,649,776 WSPR spots made by WSJT-X v1.6.0 thru v1.7.0. I know the PSKreporter site lists WSPR as a mode, but I am not sure if the WSJT-X WSPR users are being counted in the rolled up numbers. Just another data

Re: [wsjt-devel] wsjtx lock file location

On 15/04/2016 18:36, Richard Bown wrote: > OK Bill, I'll attempt the udp route Hi Richard, if you take the source of the UDPDaemon.cpp program as a starting point and hack it to do the stuff you need then compile it and link it with the object files you get by compiling NetworkMessage.cpp,

Re: [wsjt-devel] wsjtx lock file location

On Fri, 15 Apr 2016 17:43:18 +0100 Bill Somerville wrote: > On 15/04/2016 17:25, Richard Bown wrote: > > Actually in /tmp:) > Oops, sorry about that. %TMP% on Windows and $TMPDIR on Mac. > > But as well as the lockfile, I also found /tmp/WSJTX > > and lurking in that

Re: [wsjt-devel] wsjtx lock file location

On 15/04/2016 17:25, Richard Bown wrote: > Actually in /tmp:) Oops, sorry about that. %TMP% on Windows and $TMPDIR on Mac. > But as well as the lockfile, I also found /tmp/WSJTX > and lurking in that directory is a file wsjtx_status.txt > which I can check for its existence, its only there when

Re: [wsjt-devel] wsjtx lock file location

Hi Bill Actually in /tmp :) But as well as the lockfile, I also found /tmp/WSJTX and lurking in that directory is a file wsjtx_status.txt which I can check for its existence, its only there when WSJTX is running which means the lockfile is untouched. Thanks On Fri, 15 Apr 2016 16:50:05 +0100

[wsjt-devel] wsjtx lock file location

Hi where is the lock file stored when wsjtx is running ? I'd like to change the screen resolution when running wsjtx and looking for a file to test, as an alternative to greping from the process ID. I could start wsjtx from a shell script and change the screen res there, but I still need to test

Re: [wsjt-devel] WSJTX on ARMHF SBC ,

Our postings crossed All builds made were using JTSDK, much easier than manually building. When getting the failed build first of all I tried several different versions , 1.5.0, 1.6.0rc2, and exp versions all with the same build failure right at the end of the build. Each time a new build was