While I permit discussion of WSJT-X, JTDX and MSHV issues here on this forum, especially when they relate to JTAlert, this group is not for WSJT-X, JTDX or MSHV 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.freeforums.net/* *MSHV https://groups.io/g/MSHV/* de Laurie VK3AMA (JTAlert author)

The latest JTAlert version 2.60.7 is now available at https://hamapps.com/JTAlert/ Full release notes are available at the end of this message. de Laurie VK3AMA (JTAlert author) Release Notes: > 2.60.7 (2023-May-25) > > New: > > - Callsigns window: Dedicated POTA, SOTA and VOTA directional CQ > badges and > border colors. Badge text is limited to two character, PO, SO > and VO. > These will only be displayed for directed CQ decodes. See the > Badges section > of the Callsigns window Options display (left-click the cog > icon, lower- > right of the Callsigns window). > > - Callsigns window: Callsign context menu (right-click menu) entry > to copy the > decode DF to the clipboard. > > > Changes: > > - QSO History: The "First QSO" message is no longer shown for the > unsupported > Alert modes like Q65 and MSK144. Note B4 reporting and B4 > decode coloring > for unsupported modes is unchanged and works correctly. > > - User defined alert: Now supports 5 and 10 second repeat intervals. > Previously 15 seconds was the minimum interval. > > > Fixes: > > - Decodes window: An inability to clear the filter applied from a > previous > JTAlert session where the filter was for a decode property > that no longer > exists in the decodes database. This resulted in the > non-display of new > decodes. This was frequently encountered when decodes were > filtered for > a callsign that was no longer present in the database. > > - Callsign click: The UDP instruction sent to WSJTX (and clones) > was not sending > the Alt key pressed state. The instruction was formatted as if > no key was > pressed at the time of the click event. The Ctrl key pressed > state was not > affected by this defect. >

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