The latest JTAlert version 2.60.5 is now available at https://hamapps.com/JTAlert/ Please note Alert priorities have been reset with this release. If you are running with custom Alert priorities you will need to adjust them after the install of this release. This is a one-off change. Full release notes are available at the end of this message. de Laurie VK3AMA (JTAlert author) Release Notes: 2.60.5 (2023-Feb-7) *** NOTICE : Alert priorities have been reset to their defaults with this release. New: Main Window: The main JTAlert window will now automatically reduce its width by half if the log fields display is not being shown. Callsigns Window: New "Decodes : CQ Alerted" view type. This view will show callsigns calling CQ or a directed CQ that also triggered one or more Alerts like Dxcc, State, etc. Alert Priorities: Directed CQ and Wanted Callsigns #2 and #3 Alerts now have their own priority setting. See the Main settings window "Alerts - Alerts Priority" section. Marathon Alert: Now has additional callsign coloring options for the three different Marathon Alert trigger combinations. New Zone and Country, new Zone only and new Country only. See the main JTAlert Settings window, "Alerts - Wanted CQ Marathon" section. Note: the existing Marathon Alert colors will have been reset to the defaults due to this change. Changes: Eqsl log upload: Uploads to Eqsl are automatically disabled when using DXKeeper logging and it is set to upload to Eqsl during logging. Clublog log upload: Uploads to Clublog are automatically disabled when using DXKeeper logging and it is set to upload to Clublog during logging. Rx Frequency Alert: This Alert has been removed. Start of Tx period Alert: This Alert has been removed. End of Tx/Rx period Alert: This Alert has been removed. Fixes: Wanted Callsign #3 Alert: Sound volume adjustment not working. Missing Callsign Prompt: The callsign input window not displaying for some users when starting JTAlert that does not have the station callsign stored in the Windows registry.

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

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

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).