JTAlert Release Notes:
*** IMPORTANT : CRITICAL : Versions 2.8x.x require the NET 8 Desktop Runtime *** *** *** The Microsoft .NET 8 desktop runtime is required to be installed for JTAlert *** 2.8x.x versions. Later versions of the .NET desktop runtime will automatically *** be used if found installed like .NET 9. *** *** Windows 7/8 are not officially supported by .NET 8. Some Win7/8 users have had *** success running this release. If the .NET 8 desktop runtime does not install *** or JTAlert fails to run you will need to revert to JTAlert 2.63.2.2.81.5 (2026-Jan-13)
Changes: - Overrides Manager: US State selector is now hidden for non-US Countries. The US State selector is now auto-filled with the correct State for Hawaii and Alaska. - IOTA references: Invalid format reference numbers returned from XML lookups are now ignored and not logged. Previously the IOTA reference returned from XML lookups was logged without validation of the format. Note: There is no attempt to determine if the reference is valid. Fixes: - Overrides Manager: Closing without error notification when adding a new override or modifying an existing override. (2.81.4 defect) - ATNO audio alert: Incorrectly triggered when the alert was disabled. (2.81.2 defect) - Callsigns window DT display: Incorrect DT, typically -999, shown in statusbar for languages that do not use a period as decimal symbol.
2.81.4 (2025-Dec-31)
Changes: - Overrides Manager: Now supports US States. Important: The Overrides database needs to be extended to support the new State data. This is automatically accomplished by running the Overrides Manager at least once. If you don't run the manager at least once any existing overrides will fail when JTAlert does a lookup because the old database structure is not compatible with the new code.
2.81.3 (2025-Dec-19)
Changes: - Wanted Grid Alert: The need to perform a database rebuild after a change in grid type, field or square, is no longer required. - XML lookups: Option to disable QRZ and HamQTH xml lookups if a callsign override is found after a DXCall change occurs. See the main JTAlertV2 Settings window, "Web Services -> Online XML Callbooks", Default is off (lookups performed for overrides). Fixes: - Wanted Grid Alert: Logic error causing incorrect field and square alerting when the alert was set for fields only and the alert was set to auto-update after logging.
2.81.2 (2025-Nov-21)
New: - HRD 6.9 logbook: Full support of the new SQLite logs and changed MySQL (eg MariaDB) logs. Remote SQLite and MySQL logs are supported. HRDLogbook must be running on the same PC as JTAlert. See the main JTAlertV2 Settings window, "Logging -> HRD V6.9" section for setup instructions. - Callsigns window display panels: Option to show/hide the panel header. See Callsigns window options (click cog icon), "Display Panels" section -> "Show panel header" checkbox. - Wanted Callsigns Alert #1: Option to alert on any 1x1 callsign decoded. See the main JTAlertV2 Settings window, "Alerts -> Miscellaneous Alerts -> Wanted Callsigns #1" section, Default is off. Fixes: - Callsigns window SNR views: SNR sort value not remembered, resetting to disabled after restart. - ATNO audio alert: Incorrectly triggered for B4 stations. - Confirmed Bands display: QSO counts not being cleared when DXCall cleared.
2.81.1 (2025-OCT-28)
New: - Callsigns window display tiles: Option to adjust size of tiles. This size adjustment is independent of the window zoom level. See Callsigns window options (click cog icon), "Callsign Display" section -> "Display size" slider control. - Callsigns window display tiles: Option to display bearing (SP) instead of grid. Can be set for all bands, HF bands only or VHF/UHF bands only. Default is off. - Callsigns window display tiles: Display width options "Auto" and "Widest". Auto adjusts the tile width based on the needed space to display all info without text trimming, each tile has its own width. Widest adjusts all visible tiles to the width of the widest visible tile. - Callsigns window display tiles: Option to adjust space between tiles. See Callsigns window options (click cog icon), "Callsign Display" section -> "Display spacing" slider control. - Audio alerts: ATNO audio alert with user-set audio file and volume. Is triggered whenever a Dxcc, US State or VE Prov ATNO is detected and the corresponding Wanted Alert is enabled. Eg. If the Wanted Dxcc Alert is enabled and a Dxcc ATNO is detected the sound will play. See the main JTAlertV2 Settings window, "Alerts -> Miscellaneous Alerts -> ATNO Audio Alert" section, Default is off. Changes: - Callsigns window display tiles: Clublog membership icon changed from heart to 3-pointed star. - Errors: Error #2601 (JTAlertV2.Manager.exe failures) renamed #2802. Fixes: - Callsigns window display tiles: Setting "B4 replaces SNR dB" not working. - Callsigns window display tiles: Incorrect B4 date display for non-English multi-byte character languages. - Km to Miles conversion. Not working for callsign tiles and info tooltip, Km was always shown. Setting moved to Callsign window options (click cog icon), "Callsign Display" section, "Show distance in miles" setting. Default is off.
2.81.0 (2025-OCT-6)
New: - Callsigns window display tiles: See the help file "Callsigns Window - 2.81.x Changes". - False decodes: Are no longer displayed due to Dxcc/Grid validation and a uniqueness test. Decodes appearing only once with invalid/impossible grid values (typical of Wsjtx/Jtdx/Mshv false decodes) are ignored and not displayed. Thanks to Joe W4TV for providing the Dxcc/Grid data (a not insignificant effort to produce). - Wsjtx waterfall clearing: The waterfall can be cleared on band and mode changes. Jtdx and Mshv are not supported. See the main JTAlertV2 Settings window, "Applications -> Wsjtx/Jtdx" section, - Color selector: A new selector that allows for millions of colors unlike the fixed number of pre-defined colors of the old selector. For the Callsigns, Messaging and Activity windows only. - About window: Now includes a statusbar that displays the current band, mode, dx call and a count of received decodes in the current JTAlert session. Values are updated in real-time. - Logging: New default adif log will automatically be enabled if there is not an enabled log. "DEFAULT" will be displayed in the titlebar of the main JTAlert window. Changes: - Main config file: config file backup retention changed from 7 days to 14 days. - Callsigns window DX badge: The Directed CQ badge is now two badges. One for alerted directed CQ where the word is contained in the Directed CQ Alert word list and the other for all other directed CQs. The alerted badge only shows when a decode generates a Directed CQ alert. - UDP Server: Recommended UDP multicast IP address is 224.0.0.123 (changed from 224.0.0.1). Wsjtx/Jtdx/Mshv setup guides update to reflect this change. - Wsjtx DXCall coloring: The current DXCall set in Wsjtx is colored in the Wsjtx "Band Activity" panel. Color can now be customised (previously was fixed using the Wanted Call #1 colors). See the main JTAlertV2 Settings window, "Applications -> Wsjtx Coloring" section, - CQ alerts: Non-CQ decodes ending in "73" or "RR73" can now generate the CQ alert. By default this is not enabled. See the "Alerts -> CQ" section of the main Settings window to enable. - Activity window: The color of grid-lines can now be customised. Fixes: - JTAlertV2.Manager.exe memory leak. This leak was seen as a progressive increase in memory consumption when JTAlert has been running continuously for many hours. This fix improved display performance and needed a redesign of the Callsigns window display tiles. - Intermittent 2601 errors: Error would occur randomly at startup. - SpotCollector 10.x.x: Not displaying local spots. - Messaging window: Last contact callsign display overriding the new callsign display. It was a timing issue with the new contact command being lost while the window was updating (filtering) the messages display when the display was set to group messages by contact.
2.80.4 (2025-MAR-15)
New: - Callsigns window: Dual visual alerts. Display the alert colors of the 2nd highest priority triggered alert. If a decode generates more than one alert, the Country section of the callsign tile in the Callsigns window will be colored with that secondary alert colors. On by default. This can be toggled on and off in realtime via the Callsigns Options popup. Requires the country section of the callsign display tile to be enabled. - Session Ignored cache: Option to automatically add logged callsigns to the Session cache. See the "Alerts -> Add to Session Ignored Cache when QSO logged" menu. There is no dedicated setting in the Settings window. The default is off. - Adif import window: Option to hide the adif import window that is shown during JTAlert startup. Set via the Settings menu. Setting this menu will not hide an existing visible window but will prevent its display when JTAlert is next started. - Wsjtx DXCall coloring: The current DXCall set in Wsjtx is colored in the Wsjtx "Band Activity" panel. The colors will override any Wanted Alert colors that may have been set. The colors of the Wanted Callsigns #1 Alert are used. See the main JTAlertV2 Settings window, "Applications -> Wsjtx/Jtdx" section, "Color Band Activity DXCall with Wanted Call #1 colors (not Jtdx)" checkbox. Changes: - UDP status: The Wsjtx/Jtdx/Mshv UDP status values in the About window are now grouped together and have an additional value showing if the the connection is receiving UDP messages. - Chinese sound files: Thanks to BI1MHK Kina, for providing improved English to Chinese Mandarin translations used by the Google text to voice translation service that JTAlert uses. Download https://dnl.hamapps.com/Sounds/df622ae6c2213059a38a9743e5c1255f Fixes: - Callsign Overrides: Unable to delete existing overrides causing the window to close without displaying an error. - Callsigns window: Tooltip position selector in the options window would grow to full width of screen when selecting a display position. (2.80.0 defect) Unresolved Defects: - JTAlertV2.Manager.exe memory leak. This leak is seen as a progressive increase in memory consumption when JTAlert has been running continuously for many hours.
2.80.3 (2025-JAN-15)
Changes:
- CQ Marathon: Has been renamed DX Marathon.
2.80.2 (2025-JAN-6)
Fixes:
- Failure to start: On 32bit (x86) Win10 and Win11, JTAlert would show a fatal error
window about an inability to start the JTAlertV2.Manager.exe process.
2.80.1 (2025-JAN-1)
New: - NET 8 Desktop Runtime: This version will not work with the old, no longer supported by Microsoft, NET 6 Desktop Runtime. See the JTAlert download page on HamApps.com for official Microsoft download links for the Desktop Runtime. - Messaging window: Setting to send message with Enter key. See Messages section of the Options window (use F2 or click cog icon). - Messaging window: Setting to send your name in outgoing messages. Recipients using this version of JTAlert and higher only will see the name alongside your callsign on messages received. See Messages section of the Options window. - Messaging window: Grouping messages by contact callsign. See Messages section of the Options window. - Callsigns window: New option to allow display of the flashing ATNO label in the callsign tooltip display. The default is to allow display. See Callsigns section of the Options window. Changes: - NET Runtime check: Now checks for NET 8 Desktop Runtime and if successful will display all runtime versions found installed on the users PC. - Lotw & Eqsl filters: The last known upload date filtering for Wanted Alerts and membership flags now supports day intervals (30, 60, 90, 180 and 270 days). Previously only year intervals were available. See the "Alerts | Lotw / Eqsl" section of the main Settings window. Fixes: - QRZ log: Grid not included in the upload resulting in QRZ using their XML grid for the QSO record. - Messaging window: While running multiple JTAlert instances, random not displaying new messages while receiving the new message audio notification. - Error: Autoit undeclared error window when JTAlert startup is cancelled from "waiting for Wsjtx/Jtdx/Mshv to start" window or when JTAlert is automatically closed due to file creation errors encountered during startup. - Settings window: Wanted Call #3 missing from the quick enable/disable view. - Wanted Callsigns #3: Enable checkbox toggling Wanted Callsigns #2 setting.
2.80.0 (Unreleased Beta)
2.63.2 (2024-Nov-1)
New: - Logging: Option "Log Gridsquare". This is enabled by default. When unchecked this will prevent the grid from being logged. A user has to make a one-time deliberate choice to change the setting if they don't want grid logging. Note this affects all grid data sources, xml, previous log entry, on-air decoded grid, Wsjtx grid fields and JTAlert manually entered grid. - Callsign data: New "Alerts -> Clear callsign data cache" menu. Changes: - Logging: utf-8 multi-byte encoded characters converted to '?' character for loggers and online logs that take ascii only data (adif) via their logging interfaces. Applies to all loggers except Log4OMv2. Fixes: - Error: JTAlertV2.Manager.exe not closing when JTAlert is automatically closed due to file creation errors encountered during startup.
2.63.1 (2024-Oct-7)
New: - Callsign history window: Now shows the last upload date for Eqsl(AG) callsigns. Changes: - Hotkeys: The setting to enable/disable hotkeys has been removed. Hotkeys, restricted to JTAlert windows, are now permanently enabled. - JTAlert installer: Now using the latest version of the Inno compiler (6.3.3). Hopefully this will help reduce AV false-positives on the installer file. Fixes: - Windows keyboard input lag: Some users when running multiple JTAlert instances, typically 3 or more, experienced OS wide keyboard input lag. This was caused by a 3rd party hotkey library, now replaced. It did not affect all multiple instance users. - Callsign history window: Failed to show Lotw/Eqsl member info for callsigns that already existed in the JTAlert connected log. (2.63.0 defect)
2.63.0 (2024-Sep-3)
New: - Callsigns database: New database format which provides Eqsl(AG) last upload date and Clublog oqrs user last upload date. Database size reduction from typically 8.7 MB to 5.1 MB. For JTAlert 2.63.0 and later versions only. - Eqsl age filtering: Filtering of decodes based on last upload date similar to the the existing Lotw upload age filtering is now supported. - Windows tray icon: Windows taskbar notification area tray icon now brings the main JTAlert window forward of all other windows via a single left-click. The right- click brings up a context menu. - Messaging notifications: Text Messages receipt can be toggled on/off via the "Msgs ON/OFF" menu of JTAlert instance #1 window. - Multi-instance identification: For instances greater than #1 (#2 to #16) the main window titlebar icon, the taskbar entry icon and notification tray icon are overlayed with the instance number. Currently the Callsigns window does not have this, all its instance windows have the same icon. - Session ignored callsigns database: The single database cache is now shared across all running JTAlert instances. A callsign ignored under one JTAlert instance is now known by all other instances (previously each instance had an independent cache). - Session ignored callsigns database: Now takes into account the Band and Mode of the callsign ignored. If you ignore a callsign while on 20m they will not be ignored if you switch to say 10m. When you switch back to 20m they will continue to be ignored. Changes: - Session ignored callsigns database: The "clear on band change" setting has been removed as it is no longer needed now that the band is recorded with each callsign when it is added to the database cache. - Session ignored callsigns clearing: Restarting JTAlert no longer automatically clears the callsigns cache. Previous session callsigns by band/mode are retained unless their age is greater than 4 hours. If there is a need to consider less than 4 hours between JTAlert sessions the cache can be manually cleared via menus under the main window "Alerts" menu (near the top).