Hi the ADIF-HRD version includes all QSL info ! 73

Hi It _may_ be what you have set for conformation - worked, LOTW, etc. ADIF does not usually have the QSL info - HRD may have an extended export option that does include it - I would double check

Any plans to allow the main window to be re-sized? I would love to be able to essentially rotate the window 90 degrees – in other words, have tall columns. Instead of choices of 1-4 X 6-9, be

Hi probably I solved, creating a new DB in HRD from scratch and importo the ADIF exported before . Now with last version of HRD and last version of JTALERT no more crash . Only a thing seems to be

I'm having the same problem. Started a day or two ago, possibly after a Windows update. I have multicast set up. After one or two QSOs, it looks like JTAlert stops responding. JTAlert 2.16.4 (also

Hi first of all thank you for suggests . I contacted also the HRD team support and they didn't know about problems in the last revision ( 6.7.0.301 ) . What I saw is that when all tools are up, HRD,

I'm seeing the same thing here on 2.3.0-rc1 FIrst start...JTAlert sees no packets at all...no band info or such in title bar Second start...JTAlert sees band info...but no decodes Third start...all is

Here's my Help -> About JTAlert JTAlert Instance : #1 JTAlert Start Params : /wsjtx WSJT-X Window Title : WSJT-X - IC7300 v2.2.2 by K1JT, G4WJS, and K9AN WSJT-X Command Line :

It looks like the broadcast is going out okay, but still the same result. "Unable to communicate with the WSJT-X process"

Try setting wsjtx to use a multicast address for the UDP Server address. I suggest 239.255.0.0 After making the change restart both wsjtx & JTAlert de Laurie

What does the Help/About show? It shows all the JTAlert processes. What antivirus are you running? Mike W9MDB

I'm a bit puzzled. JTAlert stopped showing any decodes. I am getting the dreaded "Unable to communicate with the WSJT-X process" see below. I am running WSJT-X v2.2.2 0d9b96 with JTAlert version

What version of WSJT-X? What are your PC specs, cpu type, # cores, memory installed? de Laurie VK3AMA

From the JTAlert window menu... Within the Settings window... de Laurie VK3AMA

OK, I think I found it. I went to Standard ADIF file and imported there. It does not appear to indicate that this is where one scans an existing log for new users, but I have it now. 73, John

The program was working like a charm with WSJT-X. Then all of a sudden its starting to fall behind. Sometimes it doesn't show anything at all. I know its connected, because it reads the mode and band

Thank you for the reply. Excuse my ignorance - I was in that section, but I do not see anywhere to scan my existing ADIF log like the previous version. 73, John K9EL

From the release notes... de Laurie VK3AMA

I downloaded the latest version, but the "scan log" setting is not there. Perhaps there is some other setting that must be enabled for the scan log option to appear? Thanks John K9EL

I am running version 2.16.14. It seems like the ADIF Export from DX4WIN includes the DXCC Prefix in the output, even for /MM stations. I'll have to fix this and rebuild. groups.io