Hello !
I'm observing a strange behavior with WSJTX r4784.
For historical reasons, my working directory is still in ~/.wsjtx/bin/.
I starts the program from this directory. Now, I'm surprised not to see
the files named wsjtx.log timer.out wsjtx.ini ALL.TXT decoded.txt
wsjtx_status.txt having
On 18/12/2014 11:25, Claude Frantz wrote:
> Hello !
Hi Claude
>
> I'm observing a strange behavior with WSJTX r4784.
>
> For historical reasons, my working directory is still in
> ~/.wsjtx/bin/. I starts the program from this directory. Now, I'm
> surprised not to see the files named wsjtx.log ti
Hello All,
I added a Windows script (Complements to StackOverflow) to JTSDK v2.0.0
\scripts directory that allows timing of commands, for example,
Need to run the update first to get the new file, then:
[1] Open JTSDK-QT
[2] cd /d < WSJTX JT9.exe location >
[3][ Run command < using Joe's example
Yes
Joe,
We'll let you know what we
find.
And yes, I'm using ARMv7 hardware, because size of
equipment
and power are VERY
important.
How many hams in India could afford to run a 100W PC
24x7
for
WSPR?
That's $300 per year here in
Australia.
Can yo
Hi Laurie,
installed and working for me.
Ill try on other machines.
73 Sandro IW3RAB
Il 18/12/2014 04:51, Laurie VK3AMA ha scritto:
>
> Sandro,
>
> JTAlert holding the WSJT-X temp directory open is a defect with the
> current 2.5.5 release of JTAlert. I have a patched JTAlert.exe that
> corre
Big idea,
this remember me in 1985 with timex command
Tomorrow night I update JTSDK
By the way the execution time difference seem be relevant only on non
desktop computers ( Intel turbo mode ? video drivers/hardware ? direct X ?)
Merry Christmas to all
73 de Sandro IW3RAB
Il 18/12/2014 19:24,
Alan --
For several years already the SVN repository has included two
lightweight WSPR tools:
wspr0.exe
wspr_nogui.py
If running on minimal hardware is a high-priority goal for you (or for
your balloonists, or ???) have you considered either of these?
These programs have not received mu
