Ah, Laurie! Must be Aussie Hacker humor to point out settings and info based on code released just hours before, ha! Thought I was bad when running the code distributions for Fido and Opus, et al. <lo

#Beta

Note: The previously announced build 0001 file has been removed due to a defect. If you were quick and installed build 0001 before it was removed you need to install this build. A new JTAlert build is

#Announcement #Beta

The download link for this Beta has been removed due to a defect just now identified. It should be restored within the hour (maybe two). QRX de Laurie VK3AMA

#Announcement #Beta

A new JTAlert build is available for HRD 6.7.0.269 users experiencing problems with FT4 decodes and qso logging. https://dnl.HamApps.com/Beta/JTAlert.2.16.3.build.0001.Beta.Setup.exe After installing

#Announcement #Beta

Franco, I'll be blunt, unless the MSHV developer fixes the Status reporting bug in his software, JTAlert will never support MSHV. The bug is that MSHV NEVER generates a status packet when the Band cha

#Beta

Great to see Ft4 out. We bit of testing and things to sort. But I'm sure they will. With me jt alert not working properly. And auto logging to eqsl. But I like it. Fast. 2. Great job guys . I'll keep

#Beta

Jim, What is the error message shown by JTAlert? The error messages are placed in your Windows clipboard so you can paste it into a message. Very likely the UDP message is related to incorrect UDP Ser

#Beta

I have enough users testing this version. Topic is now closed. de Laurie, VK3AMA

#FT8 #Beta

I have enough users to test the HRD v6 logging. Topic now closed. de Laurie, VK3AMA

#Beta #FT8

Laurie, I have still been using the JTAlert 2.8.7 with HRD and have postponed the Update for this reason. Given the chance I would like to see or Try to Use a Updated JTAlert with the latest HRD. I ha

#Beta #FT8