You have probably seen my earlier posts tracking down the cause of lost decode
cycles, or more often, decoding just completely stops on a new HP laptop when
CPU utilization is < 10%. Above that all is fine. This is on a new 8th gen
Core i5 8265U, Intel UHD620 GPU, 8GB RAM, 256GB SSD, and
Barry,
or this might be what you are after:
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/Versions.cmake. The
Mark I eyeball may also be what you are after, since there is no obvious
(to me, at least) reliably parsable version information file to be seen.
Bill's suggestion and mine are
On 28/01/2019 22:40, Barry Jackson wrote:
In order to keep the packages I maintain up-to-date, especially prior
to our distro releases I run a script which parses and extracts the
latest stable version numbers and compares them to our current packages.
To do this I use lynx --dump and parse
In order to keep the packages I maintain up-to-date, especially prior to
our distro releases I run a script which parses and extracts the latest
stable version numbers and compares them to our current packages.
To do this I use lynx --dump and parse the page text to extract
the version
Good day allPosted over in general wsjtx list not much joy - Been playing and need some adviceOne PC, multiple Audio connections to two separate transceivers - wsjtx v2.0.0Start one wsjtx —rig-name=test wsjt starts up and runs fineStart another instance but no —rig-name - wsjtx starts up
