OM, What version of JTAlert? I suspect it is not current. Recent Hardware /Software changes on the HamSpots server broke BandActvity data collection for older JTAlert

For some reason the Band Activity has stopped. Is there some menu item that I accidently used to stop it or is there a problem?

I was away for a while, so I clicked off the [Monitor] in WSJT-X before I left ... with JTalert still open. Came back a couple of hours later, clicked on [Monitor] and waterfall began ... worked a

I was loading QSO Relay this afternoon, in preparation for HRD. I was getting errors about unable to log QSO. I went & uninstalled QSO Relay, did a restart and getting the same error. I'm now set set

Brad, If JTAlert is clearing the Callsigns after 5 seconds, that indicates that JTAlert is not receiving decode packets from WSJT-X and processing the decodes until well into

John, Thanks for the update. Saves me having to engage in an extensive debugging exercise trying to identify a JTAlert defect that doesn't exists.. de Laurie

Hi, Wayne N4GIL has asked that I explain the setup that enables WSJT-X/JTAlert log qso’s directly into Logger 32. I’m using the latest versions of Logger 32, WSJT-X and JTAlert and have two

Fred, What are you asking for? Do you want JTAlert to support Swisslog logging? In the past JTAlert supported Swisslog logging but that was abandoned back in 2012.

Neil, That's correct. The last few days have been rather hectic with the MS Defender false-positives of 2.10.11 and the quick release of 2.10.12 that the release notes didn't get updated with the

Huh- sw and fingertrouble. When deleting JTDX ver 17.9 in 'add/remove programs' before the update, I thought the JTDX 17.9 was deleted. It was not and all program shortcuts was pointing to the old

Is it possible to make swisslog compatible with JTALertX?? Thanks and 73 Fred NZ4DX

What version of JTDX are you running and is there any reason you can't upgrade? de Mike W9MDB

The checkbox was in ver. 2.10.11, but removed in the newest version. So I have installed ver. 2.10.11 again. Hope the checkbox reappear in the next version. 73 de Gorm.

Oops...wrong dude.... Fixed. 73's Mike

Looks like the option has been deprecated and you need to upgrade your JTDX. de Mike W9MDB

FWIW ... it looks like there was a code reversion somewhere, as the checkbox is missing in v2.10.12. It was there in v2.10.10 and I beleive in v2.10.11. Neil, KN3ILZ

Additional Information: I tried: Settings, Window section, "Show dB (DXCC Name)" option That did not work until I also enabled Show DXCC Names Below Callsigns Now I have what I need. 73

Laurie, I just upgraded to JTDX v18.1.0.69 this morning and the problem has gone away. Sorry to have bothered you. . . . John (WA3CAS)

Hi. JTAlert waits for JTDX starting even if the JTDX already is running. Laurie wrote for some time ago: The correct fix, a one-time event that will not need to be repeated with future JTDX versions

Sorry I got the terminology incorrect. It is the main window that clears after 5 seconds and it is in the main window that a signal report would be most helpful. The program, as is, is great and