Visit https://HamApps.com for the download link and upgrade/install instructions This release is available in two builds, the traditional build (menus and band activity displayed on the titlebar) plus a new "Alternate Layout" build created for those Win10 users who are experiencing missing menus and band activity display with the traditional JTAlert build. Release Notes... Fixes: - HRD V5 logging failing. (2.12.8 defect) Changes: - 3 and 4 alpha character directional CQ messages (previous only 1 and 2 alpha character) are now alerted and spotted. eg. "CQ TEST VK3AMA QF22" is now alerting and spotting the Callsign, "VK3AMA". de Laurie VK3AMA

Please, if your sending a Contact Support request from JTAlert, in response to a request I have made in this group, include a description of the fault you want me to examine. A note like "As requested" is not very helpful (I have 3 like this today) and will result in me focusing on other Support Requests first. de Laurie VK3AMA

If you want to take captures of individual windows, the entire desktop or arbitrary areas of your screen, it is extremely easy using a tool built into Windows since Vista. The Snipping Tool its called. Screen/Window captures are the preferred method of capturing images for posting to the forum. Taking a digital photo using your cell/mobile phone is not suitable and takes far longer (more steps) and often produces oversized/slanted images A couple of simple online tutorials... https://support.microsoft.com/en-au/help/13776/windows-use-snipping-tool-to-capture-screenshots https://computertutorflorida.com/2011/10/windows-7-built-in-screenshot-tool/ 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, all JTAlert files and the Installer are submitted to the VirusTotal Online Scanner where scans from over 60 commercial scanners are performed. Detection's that don't identify a specific named threat, but contain words like "Gen", "Generic", "Malicious", "Confidence", "Malware", "Reputation", "Heuristic", "Autoit", 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... * Submit the file(s) yourself to VirusTotal and see what over 60 other Scanners report about the file(s). * Don't install the software. Send a false-positive submission to your Virus protection software company. Wait for them to confirm that the file is safe and they update their definitions files before installing/upgrading JTAlert. * Reputable Virus/Malware 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. If you believe there is a *genuine* threat contained within the JTAlert files, stop using/installing the program and post a message to this group. de Laurie, VK3AMA

Visit https://HamApps.com for the download link and upgrade/install instructions This release is available in two builds, the traditional build (menus and band activity displayed on the titlebar) plus a new "Alternate Layout" build created for those Win10 users who are experiencing missing menus and band activity display with the traditional JTAlert build. Release Notes... New Features: - Logging of WSJT-X Contest Exchanges (SRX_STRING & STX_STRING). Requires WSJT-X v2.0.0. Available for DXKeeper, Log4OM, HRD V5/V6 and ADIF only. Changes: - All Alert sounds are now disabled if JTAlert is set to use the same Soundcard output device as that configured in WSJT-X & JTDX. A warning popup message is shown and and all sounds are disabled for the duration of the current JTAlert session. - WSJT-X decodes will no longer be processed (no alerting or spotting) if a band change has occured during an FT8 15 second period. There are no longer any attempts to determine the true band of the spots based on where in the 15 second period (early, mid or late period). - Increased timeout before showing the unable to communicate with WSJT-X error window. Timout changed from 30 seconds to 2 minutes. JTAlert needs to receive its first UDP packet from WSJT-X within this time period. - Distance value for the "Out of Shack" distance trigger is now manually set up to 5 numeric digits (previously a dropdown list of discrete values). - Header added to LastQSO.adi file. - ?->About window now reports the enabled WSJT-X special operation mode. Fox, Hound and supported Contests. WSJT-X v2.0.0 only. - Callsign validation extended to accept non-traditional callsign naming. eg "DM152ZYA", "TC630MECCA", "DL70PADER", "SX60RAAG", "DF1000ZEIL" Typically seen with special event Station callsigns that are now being decoded by 77 bit FT8 (since WSJT-X 2.0.0). Fixes: - VK portable Callsigns (CALL/VK & VK/CALL) incorrectly alerted as Antarctica. - Callsigns shown as "<callsign>" in WSJT-X decodes not processed and alerted. de Laurie VK3AMA

From the JTAlert Help File, "Tutorials -> ARRL International Grid Chase 2018" topic... The Wanted Grids Scan Log operation should be performed at the start of each UTC Month. This will reset the Wanted Grid Lists so that all Grids regardless of being worked B4 will produce alerts for the new Month. The Scan can be run multiple times during the month, but ideally this should be done after you have updated your log with the latest LoTW confirmations. de Laurie, VK3AMA

Copyright 2011 - 2017, 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. You may install and use an unlimited number of copies of JTAlert for personal use ONLY. Commercial use is expressly forbidden. You are not permitted to sell JTAlert or any portion of it. You are not permitted to distribute JTAlert in any form. You are not permitted to include JTAlert or any portion of it in any commercial software. 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).