Currently JTAlert does not support Log4OM V2. The Log4OM V2 log file schema is radically different from the V1 log file schema. The two are not compatible and JTAlert will fail most Log4OM specific functions when it encounters a V2 log since JTAlert is coded to expect a V1 log structure/data. There are differences between the V1 & V2 config file structure and location and any reads of the config will either fail or produce incorrect results. The following will not work, either silently failing, producing incorrect results or error messages... * Logging & logged QSO confirmation * Worked B4 checks. * Callsign (DX Call) QSO history * Callsign (DX Call) confirmed/worked Bands. * Scan Log to update the Wanted Lists. Fundamentally any function that involves reading of the Log4OM log will not work. I was unaware of the V2 release date and hadn't completed coding/testing the V2 support when it became publicly available. I expect that full support for V2 (sqlite log file only) to be available with the next public release of JTAlert. V2 MySQL log file support may not be available with the next release. de Laurie VK3AMA

The Latest JTAlert version 2.15.7 is now available @ https://hamapps.com/JTAlert/ de Laurie VK3AMA The Release Notes...

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 60 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", 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 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. 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

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.yahoo.com/neo/groups/wsjtgroup/info JTDX https://jtdx.groups.io/g/main 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