|
locked
sticky
FAQ : Suspected Virus/Malware Detection. Some facts and what to do.
#FAQ
#Reminder
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 Instal
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
By HamApps Support (VK3AMA)
·
|
|
locked
sticky
#Announcement BandActivty & TextMessage services for pre 2.15.0 versions of JTAlert turned off 2 messages
#Announcement
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 t
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
By HamApps Support (VK3AMA)
·
|
|
locked
sticky
Where to post WSJT-X and JTDX specific help questions.
#FAQ
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
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
By HamApps Support (VK3AMA)
·
|
|
sticky
#Important #Announcement : The next release of JTAlert requires the .NET 5 desktop runtime
#Important
#Announcement
The next release of JTAlert, version 2.50.0, requires the installation of the Microsoft .NET 5 Desktop Runtime. The JTAlert installer will automatically check if you have the required runtime installe
The next release of JTAlert, version 2.50.0, requires the installation of the Microsoft .NET 5 Desktop Runtime. The JTAlert installer will automatically check if you have the required runtime installed. If the runtime is not found you will be given the option to install the needed file. The correct 64bit (x64) or 32bit (x86) version needs to be installed matching your Windows OS architecture If you wish to install the runtime ahead of the new JTAlert release, it can be obtained here... https://dotnet.microsoft.com/download/dotnet/5.0/runtime/ When JTAlert 2.50.0 is released the JTAlert download pages will be updated with this new requirement. JTAlert 2.50.0 will be publicly released in approx 7 days time. de Laurie VK3AMA
By HamApps Support (VK3AMA)
·
|
|
locked
sticky
#Announcement : Testing if .NET 5 Desktop Runtime is installed on your PC.
#Announcement
The upcoming JTAlert 2.50.0 release requires the .NET 5 Desktop Runtime to be installed. See this previous message. If you would like to test if your PC has the necessary runtime installed follow thes
The upcoming JTAlert 2.50.0 release requires the .NET 5 Desktop Runtime to be installed. See this previous message. If you would like to test if your PC has the necessary runtime installed follow these steps... Download https://dnl.HamApps.com/Beta/FrameworkCheck.zip Extract the contents of the zip file to a folder of your choosing, then run the executable, FrameworkCheck.exe If a suitable runtime is installed a window similar to this will be displayed. If a suitable runtime is not installed a window similar to this will be displayed. If after installing the runtime, executing FrameworkCheck.exe still produces the above error window, than you will not be able to use the new JTAlert 2.50.0 when released and will have to continue using the old 2.16.17 version. de Laurie VK3AMA
By HamApps Support (VK3AMA)
·
|
|
locked
sticky
FAQ : JTAlert Software Usage License
#FAQ
Copyright 2011 - 2021, 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 "Softwa
Copyright 2011 - 2021, 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).
By HamApps Support (VK3AMA)
·
|
|
locked
sticky
#Announcement #NewRelease JTAlert 2.50.0 is available - Unlimited Callsigns display + much more
#Announcement
#NewRelease
The latest JTAlert version 2.50.0 is now available @ https://hamapps.com/JTAlert/ Please review the release notes at the end of this message. This is a significant release with many changes. Please no
The latest JTAlert version 2.50.0 is now available @ https://hamapps.com/JTAlert/ Please review the release notes at the end of this message. This is a significant release with many changes. Please note the mandatory .NET 5 Desktop Runtime requirement. On everyone's wish list was the need for increased Callsigns display past the hard 36 callsign limit. There is now no limit on the number of Callsigns displayed at the end of a period. The Callsigns display has been removed from the main JTAlert window and is now a standalone, user-sizable and zoom-able, window with no limit on the number of Callsigns. There is a new dedicated "2.50.0 features" help file which covers all the recent changes with this release. If you encounter a breaking problem, it is a simple matter to downgrade to an earlier version by simply running the installer for that version. 2.16.17 is recommended if you need to downgrade. de Laurie VK3AMA Release Notes. 2.50.0 (2021-Apr-12) *** The Microsoft .NET 5 desktop runtime is required to be installed for this *** version of JTAlert (and all future versions). The JTAlert installer will *** automatically run a runtime check utility which will offer to install the *** necessary runtime if it is not detected installed on your PC. *** Important note regarding Q65 mode: Q65 support is only partial. *** Accurate Q65 B4 checks and Q65 logging are fully supported. *** There is no Alerting for Q65 DXCCs, States, Grids, Prefixes, etc. *** Includes Callsign database file version 2021-04-05 (2021-Apr-05) New Features: *** Important: Please review the new "JTAlert 2.50 features" help file for *** a complete description (with loads of images) of the new Callsigns, *** Activity, Messaging & BandHeat windows and the location of their *** respective settings. See under the "Help" window of the main JTAlert *** window or the shortcut in the "HamApps JTAlert" Windows start-menu group. - Callsigns window: This replaces the old callsigns display grid embedded in the main JTAlert window. This window is fully resizable with no limit on the number of Callsigns displayed, except for available screen space and the number of decodes produced at the end of a period. - Messaging window: This replaces the old Text Messages window. It will show both sent and received messages and retain them for 7 days. Previously sent/received messages can be saved for reuse. The message limit is 2048 character (old window was 256 characters). - Activity window: This replaces the old Mode Activity window. It is resizable, supports the new FST4 and Q65 modes as well as the 560m, 8m, & 5m bands. Individual bands and modes can be turned off and not displayed. - Band Heat window: This replaces the old Activity Bands display that was embedded in the main JTAlert window. It is now an independent window, supports the 560m, 8m & 5m bands, and can be set to display vertically or horizontally (the default). Individual bands can be turned off and hidden. Changes: - Decodes window: Frequency column can be set to either KHz or MHz. - QSL flags: The Lotw and Eqsl flag positions on the Callsigns display and Decodes window are no longer changeable. They are fixed in location. Lotw -> bottom left of the Callsign. Eqsl -> bottom right of the Callsign. - Hotkeys: No longer user-changeable, they are now hard-coded. F1 -> Help window F2 -> Settings window F3 -> Callsigns window F4 -> Decodes window F5 -> Text Messages widow F6 -> Call History window F7 -> Alert Status window F8 -> Macros window F9 -> not used F10 -> not used F11 -> Activity window F12 -> BandHeat window Alt + H -> Open browser to HamSpots.net Alt + Q -> Open browser to QRZ.com - Callsign Display Grid: Has been removed and is now a separate, resizable window, simply called the "Callsigns" window. - Text Messages Window: Now called "Messaging" Window, is only launchable from the JTAlert first instance (#1). - WSJT-X: B4 & Ignored callsigns are now highlighted in WSJT-X when they are hidden in JTAlert due to filtering. - Menus: Several menus associated with the new Windows introduced with this release (Activit
By HamApps Support (VK3AMA)
·
|
|
JT Alert 2.50.0 stopped by FrameworkCheck 19 messages
Laurie I’m having a problem getting by the Framework Check with an Error Code 216. It says it is not compatible with my system. I’m running 7 Pro, 32 bit and I have .NET5 , 32 bit installed and Comman
Laurie I’m having a problem getting by the Framework Check with an Error Code 216. It says it is not compatible with my system. I’m running 7 Pro, 32 bit and I have .NET5 , 32 bit installed and Comman
|
By Melvin L. Nichols
·
|
|
JTAlert 2.50 Won't start 3 messages
I have windows 10 with ALL Microsoft updates installed. I have Net 5 runtime installed but when I load 2.50 Frameworkcheck says "This app can't run on your PC" and a bunch of other random error messag
I have windows 10 with ALL Microsoft updates installed. I have Net 5 runtime installed but when I load 2.50 Frameworkcheck says "This app can't run on your PC" and a bunch of other random error messag
|
By Eric Alchowiak
·
|
|
Feature suggestion for variable filters for multiple instances 2 messages
#FT8
I use a Flex 6700 which allows using up to 8 receivers (slices in Flex terminology) for different band/mode configurations simultaneously. I usually monitor 6 bands at the same time with each receiver
I use a Flex 6700 which allows using up to 8 receivers (slices in Flex terminology) for different band/mode configurations simultaneously. I usually monitor 6 bands at the same time with each receiver
|
By Pat N6PAT
·
|
|
Feature suggestion - option to partition call window for DX vs Domestic 2 messages
#FT8
Another from my wish list: An option to allow splitting DX vs domestic call signs into separate partitions within the call sign window. Allow the user to turn the option on or off as they wish. What d
Another from my wish list: An option to allow splitting DX vs domestic call signs into separate partitions within the call sign window. Allow the user to turn the option on or off as they wish. What d
|
By Pat N6PAT
·
|
|
Line 10385 2 messages
Hi Laurie, Config - Windows 10 Home - 64-bit up-to-date and WSJT-X 2.3.0 JTAlert 2.50.0 is crashing at every launch after 10-60 s with Line 10385 Error: Variable used without being declared. Please ad
Hi Laurie, Config - Windows 10 Home - 64-bit up-to-date and WSJT-X 2.3.0 JTAlert 2.50.0 is crashing at every launch after 10-60 s with Line 10385 Error: Variable used without being declared. Please ad
|
By gabriel.dulcu@...
·
|
|
Alert Filtering enhancement ... 2 messages
Laurie, As you move more of the code into the NET framework, please consider making the alert filtering band specific. Specifically, I turn *OFF* "Show only Callsign generating alerts" on bands with l
Laurie, As you move more of the code into the NET framework, please consider making the alert filtering band specific. Specifically, I turn *OFF* "Show only Callsign generating alerts" on bands with l
|
By Joe Subich, W4TV
·
|
|
Wildcard in Wanted Callsign - not triggered? 2 messages
Greetings. I have added the following callsigns and callsign prefixes with wildcard into the Wanted Callsign Alert list. When a callsign is decoded in the CQ period, that matches a wildcard callsign p
Greetings. I have added the following callsigns and callsign prefixes with wildcard into the Wanted Callsign Alert list. When a callsign is decoded in the CQ period, that matches a wildcard callsign p
|
By Tomas, NW7US
·
|
|
Moving "QSO Logged" window? 7 messages
I'm using version 2.50.0 of JTAlert. For some reason the little "QSO Logged" window has moved to the bottom of the screen. Is there any way I can relocate it? 73, Bill AA4M
I'm using version 2.50.0 of JTAlert. For some reason the little "QSO Logged" window has moved to the bottom of the screen. Is there any way I can relocate it? 73, Bill AA4M
|
By Bill - AA4M
·
|
|
No calls are showing up in Callsign window
See my answer to the other thread you started. https://hamapps.groups.io/g/Support/message/34571 de Laurie VK3AMA
See my answer to the other thread you started. https://hamapps.groups.io/g/Support/message/34571 de Laurie VK3AMA
|
By HamApps Support (VK3AMA)
·
|
|
Not having luck with UDP settings 4 messages
I have had no luck (execpt once when it spontaneously started working for a while) getting the decodes and callsigns to show up from WSJT-X. Here are the settings from the "About window" JTAlert Insta
I have had no luck (execpt once when it spontaneously started working for a while) getting the decodes and callsigns to show up from WSJT-X. Here are the settings from the "About window" JTAlert Insta
|
By Charlie Rubenstein
·
|
|
Windows Defender false positive : Release 2.50.0 8 messages
Hi Laurie, The download is failing a Window Defender scan. This is on a Win10 Home, with all current updates including the latest Defender definition update. Most likely the old AutoIt security issue
Hi Laurie, The download is failing a Window Defender scan. This is on a Win10 Home, with all current updates including the latest Defender definition update. Most likely the old AutoIt security issue
|
By Ron / W4MMP
·
|
|
Possible Anomaly In Message Window 3 messages
Hello, I think I see an interesting behavior or anomaly in the Message Window in version 2.50.x. The scenario ............. Receive a text message from station "XXXXX" Start to reply to the message Se
Hello, I think I see an interesting behavior or anomaly in the Message Window in version 2.50.x. The scenario ............. Receive a text message from station "XXXXX" Start to reply to the message Se
|
By John Petrocelli
·
|
|
2.5.0 -- AutoIt Error 37 messages
Installed 2.50.0. Already had .NET 5.0.5 installed.
Installed 2.50.0. Already had .NET 5.0.5 installed.
|
By David - AK2L
·
|