Since JTAlert was released in 2011, there have NEVER been any documented virus/malware/trojan infections caused by JTAlert. Prior to making a new JTAlert release publicly available, the JTAlert Installer is submitted to the VirusTotal Online Scanner where scans from over 70 commercial scanners are performed. Detection's that don't identify a specific named threat, but contain words like "Gen", "Generic", "Malicious", "Confidence", "Malware", "Riskware", "Reputation", "Score", "Heuristic", "Autoit", "Script", are typically false-positives. They don't identify a genuine threat. These sort of threat identifications are typically due to the compiler used to generate the JTAlert code or due to a lack of use among the user base of this Virus protection software (typically for niche-market Amateur Radio software) If your concerned about unsafe JTAlert files reported by your Virus/Malware software please do the following... Don't install the software. Send a false-positive submission to your Protection software company. Wait for them to confirm that the file is safe and they update their definitions files before installing/upgrading JTAlert. Reputable Protection software companies offer a false-positive reporting/testing service. If your software doesn't provide this fundamental service, you should seriously consider changing to a company that does. Users are ultimately responsible for their PC/Windows infrastructure, as such they should take the initiative and report suspicious files to their Protection software provider, rather than simply accepting third party advice to apply file/directory exemptions. If you believe there is a genuine threat contained within the JTAlert files, stop using/installing the program and immediately submit the file to your Protection software vendor for analysis. If your vendor reports a threat (not a possible threat or potential risk) submit a message to this group. de Laurie, VK3AMA

While I permit discussion of JTDX and WSJT-X issues here on this forum, especially when they relate to JTAlert, this group is not for JTDX or WSJT-X specific bug reports or operation questions. These application specific questions (bug reports, how-to questions) should be posted to the support groups of those applications. For your convenience, the official support groups are... *WSJT-X https://groups.io/g/WSJTX/ JTDX https://jtdx.groups.io/g/main* de Laurie VK3AMA

Copyright 2011 - 2022, Laurie VK3AMA, All Rights Reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to use the Software subject to the following conditions. The software is provided "AS IS", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and non-infringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software. Specifically: 1. You may install and use an unlimited number of copies of JTAlert on any number of computers for personal use ONLY. Commercial use is expressly forbidden. 2. You are not permitted to sell JTAlert or any portion of it. 3. You are not permitted to host JTAlert files on external websites, forums, bulletin-boards, blogs, etc. 4. You are not permitted to distribute JTAlert in any form. 5. You are not permitted to include JTAlert or any portion of it in any commercial software. 6. You are not permitted to decompile, disassemble, reverse engineer or modify the JTAlert executable or any portion of it, including support files (eg. plugin, sound and callsign files).

The latest JTAlert version 2.60.0 is now available at https://hamapps.com/JTAlert/ Full release notes are available at the end of this message. *** IMPORTANT : CRITICAL *** This version requires the Microsoft NET 6 Desktop Runtime to be installed. The old out-of-support NET 5 Desktop Runtime will not work with this JTAlert release. The official direct download links for the NET 6 Desktop Runtime are... for 64bit Windows windowsdesktop-runtime-6.0.8-win-x64.exe for 32bit Windows windowsdesktop-runtime-6.0.8-win-x86.exe *** WARNING *** Due to significant internal code changes the Callsigns window configuration will be reset to its default. You will need to set your personal Callsigns window options (via the gear icon, bottom-right of the window in the statusbar) This release includes... MSHV support (limited) Callsign override management Additional DXKeeper automation 2 additional Wanted Callsign Alerts. New callsigns display customization. Please review the release notes at the end of this message. de Laurie VK3AMA Release Notes: 2.60.0 (2022-Aug-11) *** IMPORTANT : CRITICAL : This version requires the NET 6 Desktop Runtime *** New: - NET 6 Desktop Runtime: This version will not work with the old no longer supported by Microsoft NET 5 Desktop Runtime. See the JTAlert download page on HamApps.com for official Microsoft download links for the Desktop Runtime. - MSHV support: Support for MSHV has special restrictions. Only a single instance of the 64bit MSHV is supported, 32bit MSHV is not supported. MSHV must be set to use multicast UDP on 224.0.0.1 port 2237, other addresses and ports will not work. See the "MSHV UDP Setup" help file topic. - Callsign override management: Useful for special event stations using obscure callsigns that don't accurately convey their operating location or those pesky US based stations using KH6, KG4 or KL7 callsigns that have not made it into the callsigns database. There is no limit on the number of overrides that can be set. Open via the "Settings -> Manage callsign overrides ..." menu. Changes made via this window will be seen by JTAlert in real-time, but if you are setting an override for a callsign that has already been decoded in your current JTAlert session you will need to restart JTAlert so that old cached location data is cleared. - DXKeeper Automation: New setting to instruct DXKeeper to deduce missing QSO data like ARRL sections. This is off by default, see the main JTAlert Settings window, "Logging -> DXLab DXKeeper" section. - Callsigns Window: New option to clear callsigns when a mode change has occurred. See the "Automation" section of the Callsigns window Options popup (click gear icon) - Callsigns Window: New option to replace Country name display with the callsigns 4 character grid when operating on 8m and lower (vhf bands). See the "Callsigns" section of the Callsigns window Options popup (click the gear icon) - Wanted Callsigns Alert: Two additional, independent, Wanted Callsigns Alerts. New options to restrict a Wanted Callsign alert to either HF, VHF or all bands. See the "Alerts -> Miscellaneous Alerts" section of the main JTAlert window Settings window. Open via the "Settings" menu or use the F2 hotkey.