Still haven't been able to test the compile install. Rats... Is there an automated way to uninstall, or would I need to track down the individual files and delete? Thanks.

George, Thanks for your reply. The "Show DXCC" tick was what I needed. -J WB5JJJ - George wrote on 4/12/2019 4:15 PM:

Start small and work up. Try things in this order/color and checks. Gradually add a new one above the CQ in message highlight and see what happens. This works great in my setup as I see the CQ in

Please help with my incorrect setting(s). Despite having all colors checked except CQ in Message, all Band Activity lines are white. If I check CQ in Message, all lines are green. What am I doing

Jim, as an example, here is why it matters - FT8 QSOs are normally logged by UDP message. I noticed two days ago that the UDP port was closed. No problem, I will just load the wsjtx_log.adi file into

On 12/04/2019 16:56, Bob wrote: Bob, your request was noted, I have not had time to investigate yet. 73 Bill G4WJS.

For logging, why should one second matter?

The silence is deafening. I assume that not even a huh? reply means this is a known problem. Anyway, let me rephrase the question - Any chance the QSO time on in a UDP QSO logging message could be the

Any chance the ADIF TIME_ON field could be modified so that it matches the time used in the UDP logging message? Thanks. SeventyThree(s).

For a few weeks, so now and then, I don't have TX audio. Furthermore everything works properly. RX and PTT are okay, Setup: Windows 10 with WSTJ-X Microham USB Interface III with latest

HI Rick, comments in line below. On 09/04/2019 16:02, Rick Hatton wrote: Well done! The INSTALL file is generic, it is not meant to be specific to any

This is meant to be informational and not criticism. I did compile and install. Several tools/libraries listed in INSTALL are not named the same in Debian Stable. I used Synaptic to search for the

Hi Rick, no it will not, it is statically linked into WSJT-X and the only parts that get installed that might clash have modified names to avoid issues (rigctl-wsjtx, rigctld-wsjtx, rigctlcom-wsjtx).

Will the hamlib included with the WSJTX tarball impact/interfere with the hamlib already present in the system? Thanks for the info.

Hi Rick, these days most autotools projects recommend building outside of the source tree, it is de rigueur for CMake projects. Create a build directory somewhere, CWD to it and run the CMake

On Mon, Apr 8, 2019 at 06:45 PM, Bill Somerville wrote: On 08/04/2019 23:42, R Gape wrote:The INSTALL file in the source tar is pretty clear on what needs to be done. However, it uses Cmake rather

Dave, I think you hit the proverbial nail on the head. The default appears to be 200ms. Add that to the unspecified and unaccounted for other delays, the station I'm decoding will appear to have his

On 08/04/2019 23:42, R Gape wrote: Robin, that is misleading, it uses CMake to generate the Makefiles. GNU make is still the way the project is built on Linux. 73 Bill

Bill, looking at it from the point of view of a learning user, who is not as au fait with Linux as some on this list, then it might seem pretty much essential to make it clear that it

Hi Rick, I assume you mean the WSJT-X project page https://physics.princeton.edu/pulsar/k1jt/wsjtx.html . It does list Debian but gives no version, so it is not technically incorrect. If you were