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

The latest JTAlert version 2.16.4 is now available @ https://hamapps.com/JTAlert/ This is the official public release which has the HRD 6.7.0.269 FT4 compatibility fixes of the 2.6.3 build 0002 beta. Users of the beta need to upgrade to this version asap. All JTAlert beta release have an inbuilt 4 week expiry date after which the software becomes non-functional. The instructions provided here on correct JTAlert settings to work with HRD 6.7.0.269 are still correct except for the published beta download link which has now been removed. The JTAlert Help file also has these instructions. de Laurie VK3AMA Release Notes.

*** IMPORTANT PLEASE READ*** JTAlert users who have upgraded their version of HRD to 6.7.0.269 and followed HRD instructions on updating their existing FT4 QSOs to be adif 3.1.0 compliant, Mode-MFSK, Submode=FT4, need to do the following. * These instructions apply to HRD 6.7.0.269 *ONLY*. * Upgrade your JTAlert version to 2.16.4 or later. * Open the JTAlert Settings window. * Go to the Logging -> HRD V5/V6 section and enable the "This is a version 6.7.0.269 or later adif 3.1 compliant Log" setting. *Users of earlier versions of HRD DO NOT enable this option. * * * * Go to the Logging section and scroll the options to reveal the bottom check-boxes (use the right hand scrollbar). Enable the "Log FT4 as ADIF 3.1.0 compliant..." setting. *Users of earlier versions of HRD DO NOT enable this option. * * * * Go to the Scan Log & Rebuild section and run a scan all. This is needed to update the different Alert lists (DXCC, State, etc) to now consider the new MFSK/FT4 recorded QSOs. * NOTE: Any QSOs still in your log that are still set as Mode=FT4 will be ignored by the Scan Log operation. They will need to be update to MFSK/FT4 after which run the Scan Log again. de Laurie VK3AMA

The services running on the HamSpots Server that manage Band Activity data and Text Messaging for old (pre 2.15.0) versions of JTAlert have been disabled. Spots upload to HamSpots is not affected by this change. Server load has seen a significant increase in recent weeks. This change is part of the current Server load reduction activity. It is very unlikely they will be re-enabled in the future. If either of these two disabled services is important to you, a JTAlert upgrade to a more recent version will be needed. Sorry for the inconvenience. 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

Over the last week I received several direct emails requesting MSHV support in JTAlert. Below is the copy & paste answer sent to each emailer. The workaround (I am hesitant to call it a workaround) is to temporarily change mode whenever the Band or DXCall is changed. This would have to be manually initiated by the user. This is not practical solution and is not one I will embrace in order to provide JTAlert support. For those that will ask, yes the MSHV developer has been advised by myself and a MSHV user (who has been requesting JTAlert support). I will revisit MSHV integration testing when I receive word that this fundamental flaw in its code has been corrected. I will no longer waist my time routinely downloading and testing in the hope these defects have been corrected. de Laurie VK3AMA

Copyright 2011 - 2019, 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).

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