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

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

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

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

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.17 is now available @ https://hamapps.com/JTAlert/ Please review the release notes at the end of this message, in particular the wsjtx 2.3.0-rc2 requirements. de Laurie VK3AMA Release Notes. > 2.16.17 (06-Dec-2020) > > *** Important note regarding FST4 mode: FST4 support is only partial. > *** Accurate FST4 B4 checks and FST4 logging are fully supported. > *** There is no Alerting for FST4 DXCCs, States, Grids, Prefixes, etc. > *** There is no reporting of FST4 activity in the Mode Activity window. > > *** Includes Callsign database file version 2020-12-06 (2020-Dec-06) > > New Features: > > - Callsigns Display Grid: New online for text messages indicator, > a filled > square, can be shown in the top-right corner of the Callsign > display. > See the "Windows -> Text Messages" section of the Settings window. > > - Logging: New option to 'Log USA District "DC" as State "MD"'. > This option > is off by default. If enabled "DC" based stations will have > their State > converted from "DC" to "MD" and logged as "MD" regardless of > the value > returned from XML lookups and previous QSO lookups. > > - Command Line Parameter: "/myid=" a user defined string that will > appear > in the status section of the JTAlert titlebar text. This > parameter is > not used internally by JTAlert except for the status display. > > - WSJT-X Multicast UDP: Due to the unrelaibility in automatically > determining which network interfaces are being used by WSJT-X for > multicast UDP, JTAlert now has an explicit setting to indicate > if WSJT-X multicast UDP is using a loopback interface. Ensure that > the "Settings -> WSJT-X UDP Multicast on Loopback" menu is ticked. > This applies for WSJT-X 2.3.0 -rc2 and later. The setting is > ignored when using WSJT-X 2.2.2 and earlier. > > Changes: > > - US State Alert: "Consider DC as MD" setting moved from the "Rebuild > Alert Database" section to the "Alerts -> Wanted US States" section > of the Settings window. This setting is now titled 'Alert "DC" > as "MD"'. > When this setting is enabled, all "DC" stations will alert as "MD". > > - Decodes Windows: Online for text messages indicator symbol > changed from > a filled circle to a square. > > Fixes: > > - FST4: Callsigns not being displayed in the Callsign display and > decodes not being displayed in the Decodes History window. > > - Decodes Window: Fatal error when changing the "Highlight excess DT" > threshold value in the Settings when the Windows regional-settings > utilizes a non-dot for the decimal separator. > > - Text Messages Window: Incorrectly being show at JTAlert startup > despite the "Receive text messages ..." option being turned off.