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 color. On by default. This can be toggled on and off in real time 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.$$$$$$WSJT-X DXCall coloring: The current DXCall set in WSJT-X is colored in the WSJT-X 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 -> WSJT-X/JTDX section; Color DXCall with Wanted Call #1 colors (not JTDX) checkbox.$$$Changes:$$$UDP status: The WSJT-X/JTDX/MSHV UDP status values in the About window are now grouped together and have an additional value showing if 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 the screen when selecting a display position. (2.80.0 defect)$$$Unresolved Defects:$$$JTAlertV2.Manager memory leak. This leak is seen as a progressive increase in memory consumption when JTAlert has been running continuously for many hours.

$$$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 process.$$$

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

JTAlert Release Notes:$$$$$$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 dont 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 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 instace 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 that 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).$$$$$$$$$

2.62.2 (2024-Jul-2)$$$$$$$$$ $$$New:$$$$$$$$$ - Windows tray icon: A Windows taskbar notification area icon is now shown for$$$ each JTAlert instance. The menu for this icon allows for closing JTAlert;$$$ displaying the About JTAlert diagnostic window and for recovering a misplaced$$$ off-screen main JTAlert window.$$$$$$ - Window status bars: Callsigns; Activity & Messaging windows can be individually$$$ turned off. The default is for the status bar to be visible. If the status bar$$$ is turned off access to the cog icon to adjust settings is lost so the standard$$$ (across all windows) F2 hotkey will bring up the settings from which the status$$$ bar setting can be accessed under the Window section of the Options popup window.$$$$$$ - Error reporting: Additional popup error windows and error logging added for$$$ configuration (user settings) file related functions.$$$$$$$$$ $$$Changes:$$$$$$$$$ - Log fields display: The callsign right-click context menu DXLab lookup entries$$$ have been removed. DXLab users will get the lookups via enabling the existing$$$ lookup on new DX Call options under Applications - DXLab Suite of the main$$$ Settings window.$$$$$$$$$ $$$Fixes:$$$$$$$$$ - Callsigns window: Settings and previously saved layouts resetting to the default$$$ at JTAlert startup.$$$

2.62.1 (2024-Mar-24)$$$$$$New:$$$$$$ - DXLab SpotCollector: New dB & DF local spot message.$$$$$$ - Worked B4 Alert: New ignore log age options; 1 day; 2 days; 1 week and 2 weeks.$$$ $$$Changes:$$$$$$ - Rebuild Database window: Now remembers last display position on the desktop.$$$$$$ - Worked B4 Alert: The ignore log age date is now calculated continuously during$$$ a JTAlert session. Previously it was determined once only when JTAlert is$$$ first started and would not adjust to the utc date (day) rollover.$$$$$$$$$ $$$Fixes:$$$$$$$$$ - Messaging window: Not being displayed when using the context menu of the QSO$$$ partner callsign of the log fields display for instances other than #1.$$$$$$ - Marathon alert: WAE entity qsos incorrectly crediting the Dxcc entity during$$$ logging and alert database rebuild.$$$$$$ - Marathon alert: Entities still flagged as needed after a database rebuild against$$$ DXKeeper log with the Use DXKeeper Marathon risk data option enabled and there$$$ existed multiple same day QSOs in the log with the first QSO set as high risk.$$$

2.61.0 (2023-Nov-07)$$$New:$$$ - Dark color theme: Set via the View -> Dark themed windows menu.$$$ Note : Not all windows support the dark theme. Only the yellowed-starred$$$ windows listed under the View menu support the dark theme. The Callsigns;$$$ Activity; Messaging; Decodes; BandHeat and About windows.$$$ - Callsigns window: The callsign tile right-click context menu now includes a$$$ row of icons (at the top of the menu) for quick access to the most common$$$ menu actions; send Text message; copy callsign to clipboard; open browser$$$ to qrz.com; add callsign to ignored list and remove the callsign from display.$$$ Hover the mouse over an icon to get a brief explanatory tooltip.$$$ - Options popup windows: The default colors applied to JTAlert specific colors$$$ when using the Reset to defaults button under the Colors section of the$$$ Options popup will apply either a light or dark set of colors depending$$$ on the color theme is set for JTAlert. Note: These default colors are not$$$ the window and standard ui controls; buttons; menus; drop-down selectors;$$$ etc.; but the explicit JTAlert specific colors as seen under the Colors$$$ section of each windows Options popup (click the gear icon).$$$Changes:$$$ - Options popup windows: Shown via left-click of the gear/cog icon now dock$$$ with the parent window and change screen position when the parent is moved.$$$ - Options popup windows: Under Windows 11 only are now styled with rounded$$$ corners matching the default Windows styling.$$$ - Log fields: Field sizes adjusted to better accommodate 6 character grids$$$ without clipping.$$$ - Callsigns window: Callsign information tooltip display at mouse pointer option$$$ has been removed.$$$Fixes:$$$ - WSJTX config ini file not being read when its path is hard-linked to a WSL path

2.60.10 (2023-Sep-01)$$$$$$$$$ $$$New:$$$$$$$$$ - Logging: New Contact Type log fields selector; labelled Type. If a$$$ selected value is visible in the selector during logging its value is$$$ appended to the Comments logged. If there is no Comment set; the selected$$$ value only is logged as the Comment.$$$ The selections available are POTA; SOTA; VOTA; IOTA; COTA; WWFF; TEST.$$$$$$ $$$Fixes:$$$$$$$$$ - Logging: Incorrect QSL_VIA and NameAddress values logged when late logging.$$$ Late logging occurs when a QSO is not logged before starting a QSO with$$$ a new station (Wsjtx/Jtdx DX Call is set).$$$$$$ - User Alert: %JTAlert_IsFFMAGrid% environment variable incorrectly set to$$$ Yes when the %JTAlert_Grid% variable had no value.$$$

2.60.9 (2023-Jul-16)$$$$$$New:$$$$$$ - Logging: Option to log name and address returned from an XML lookup to the$$$ comments field of the enabled logger. See the Logging section of the main$$$ JTAlert Settings window; Log XML name and address to Comments field$$$ checkbox. The default is off.$$$$$$ - Logging: Option to log QSLMGR (QRZ xml) and QSL_VIA (HamQTH xml) returned$$$ from an XML lookup to the QSL_VIA field of the enabled logger. N3FJP loggers$$$ are not supported. See the Logging section of the main JTAlert Settings$$$ window; Log XML QSLMGR to QSL_VIA field checkbox. The default is off.$$$$$$ - Wanted Grid Alert: The internal grid lists are automatically exported to text$$$ files (one grid per line) each time JTAlert is shutdown. All possible band$$$ and mode tracking combinations are expoted to individual files with the$$$ file name reflecting the band and mode. FFMA 6m file exports are also$$$ included. Files are saved to this directory.$$$ %localappdata%\HamApps\\session\JTAlertX\GridData\$$$$$$Changes:$$$$$$ - XML lookups: For QSO records of maritime mobile stations; callsign with /MM$$$ suffix; any dxcc; continent; iota or state/province values contained in the$$$ record are ignored and not logged.$$$$$$Fixes:$$$$$$ - Wanted Callsigns #3 Alert: When triggered the callsign would not display in$$$ the Alerts Only view of the Callsigns window.$$$$$$ - Callsigns window Age sorting: The Age sorting description reversed compared$$$ to the actual sorting being performmed.

2.60.8 (2023-Jun-17)$$$$$$$$$ $$$New:$$$$$$$$$ - Wanted Callsign Alerts: Name alias (max 8 characters) which are shown in the$$$ callsign tooltip (if a Wanted Callsign Alert is triggered) and right-click$$$ context menu (if Wanted Callsign menus are enabled). See the Callsigns window;$$$ Miscellaneous section of the Options popup (left-click cog icon).$$$$$$ $$$Fixes:$$$$$$$$$ - B4 and last QSO lookups: Possible wrong most recent QSO date returned for$$$ Logs that did not have the QSOs stored in date order or a mixture of date$$$ order for QSOs imported from external files. This affected ACLog; ADIF;$$$ HRD5; HRD6 and DXKeeper.$$$$$$ - Confirmed Bands display: Delay time of several seconds for large qso count$$$ logs when responding to WSJTX DXCall changes.

2.60.6 (2023-Apr-09)$$$$$$$$$ $$$New:$$$$$$$$$ - DXLab SpotCollector: Option to post local spots to SpotCollector for decodes$$$ generating Alerts only. This is ON by default; see the main JTAlert Settings$$$ window; Applications -> DXLab Suite section.$$$$$$ - Audio Alerts: Option to not play audio alerts generated for the current QSO$$$ partner (DX Call in WSJTX/JTDX). This is off by default and is set via the$$$ Alerts -> No audio alerts for WSJTX/JTDX DX Call menu of the main JTAlert$$$ window. Note: The Own Callsign sound will always be played if triggered$$$ ignoring this setting.$$$$$$$$$ $$$Changes:$$$$$$$$$ - Czech sound files: Thanks to OK1FSB; Adam; for providing improved$$$ English to Czech translations used by the Google text to voice translation$$$ service that JTAlert uses.$$$ Download https://dnl.hamapps.com/Sounds/b0fd5f2be6c4f4287bacb55730581505$$$$$$ - Ukrainian sound files: Thanks to WW4ZZ; Georgii Iesaulov; for providing$$$ improved English to Ukrainian translations used by the Google text to$$$ voice translation service that JTAlert uses.$$$ Download https://dnl.hamapps.com/Sounds/e21828c439b60af50f49d66c8a64b68e$$$$$$ - Russian sound files: Thanks to WW4ZZ; Georgii Iesaulov; for providing$$$ improved English to Russian translations used by the Google text to$$$ voice translation service that JTAlert uses.$$$ Download https://dnl.hamapps.com/Sounds/115530b11d72e110f2e33943c641a32b$$$$$$$$$ $$$Fixes:$$$$$$$$$ - Main window position: When the main window was positioned near the bottom of$$$ the Windows deskktop and overlapping the taksbar; the position when JTAlert$$$ was next started would be incorrect.

2.60.4 (2023-Jan-2)$$$$$$$$$ $$$New:$$$$$$$$$ Wanted Grid Alert: The Alert can now be configured to alert on 2 character (MH2)$$$ OR 4 character (MH4) grids. When changing grid format in the Settings window$$$ be sure to perform the Alert Database Rebuild operation and restart JTAlert.$$$$$$$$$ $$$Changes:$$$$$$$$$ Alerting: No longer alerting on two word CALLSIGN GRID decodes. To enable$$$ alerting on these type of decodes see the main JTAlert Settings window;$$$ Alerts - Miscellaneous Alerts section.$$$$$$$$$ Fix:$$$$$$ Callsigns Window: Callers; SNR and Distance views missing the Disabled$$$ callsign sort option. Note: This fix will affect your current sorting$$$ selection for these view types.$$$$$$ Wanted Callsign Alert: CSV file export missing callsigns with widcard character.$$$$$$ QRZ Log Upload: Name data not being uploaded. This was due to JTAlert using$$$ old out-of-date api documents from QRZ.com which specified a limited number$$$ of adif fields supported with Name field not listed.$$$$$$ ClubLog Log Upload: Log uploads quietly failing (no error report from$$$ ClubLog server) due to changed upload url that was introduced 1-Jan-2023.

Provides several audio and visual alert types based on decoded Callsigns within WSJT-X.$$$$$$Audio and visual alerts for several alert conditions$$$Your Callsign decoded (someone calling you)$$$CQ$$$Wanted Callsign$$$Wanted Prefix (by Band/Mode)$$$Wanted Grid (by Band/Mode)$$$Wanted US State (by Band/Mode)$$$Wanted VE Province (by Band/Mode)$$$Wanted DXCC (by Band/Mode)$$$Wanted CQ Zone (by Band/Mode)$$$Wanted Continent (by Band/Mode)$$$Wanted CQ Marathon (by Band/Mode)$$$$$$Automatic logging to these log types when QSO is logged in JWSJT-X$$$DXLab DXKeeper$$$ACLog$$$Log4OM V1$$$Log4OM V2$$$HRD Log V5/V6$$$Standard ADIF file$$$$$$Various Web Services Supported$$$Online XML Callsign Database lookup. QRZ.com (paid) and HamQTH (free)$$$Upload logged QSO to Online Logbooks. QRZ.com; eQSL.cc; ClubLog.org and HRDLog.net$$$Upload all decoded Callsigns with frequency and Signal report to HamSpots.net$$$$$$Works with DXLab applications$$$Automatic log to DXKeeper when WSJT-X QSO is logged$$$Automatic post decoded Callsigns to SpotCollector (local spots)$$$DXKeeper lookup of previous QSOs with decoded Callsign$$$Send Callsign to Pathfinder for lookup$$$$$$Supports user-selectable Sound Card$$$Each audio alert type has independent volume setting & wave file$$$LoTW and eQSL membership flagging of decoded callsigns$$$Band Tracking or alerts. 160m to 2m; including 60m$$$Disable audio alert for Worked B4 stations on current Band$$$Automatic Worked B4 flagging of previous QSOs$$$Scan your log to update needs lists for alerting (US State; DXCC; CQZones; etc)$$$Dockable to bottom or top of WSJT-X window$$$Bring WSJT-X window to front of other windows on alert activation$$$Auto start & close of WSJT-X and other applications on JTAlert start & close$$$Send TX Power and current QSO partner data Name; Callsign & No. Bands worked to JTMacros for dynamic macros$$$2.60.3 Install instructions for first JTAlert install.$$$Install the NET 6 Desktop Runtime (see links at top of this page)$$$Download JTAlert.2.60.3.Install$$$Run JTAlert.2.60.3.Install to install$$$Install the Sound and Database files (see below)$$$Start JTAlert$$$2.60.3 Upgrade instructions.$$$Stop JTAlert if running.$$$If uprading from an old JTAlert version earlier than 2.60.0;$$$install the NET 6 Desktop Runtime (see links at top of this page)$$$Download JTAlert.2.60.3.Install$$$Run JTAlert.2.60.3.Install to upgrade.$$$(All previous settings are saved and will not be lost)$$$JTAlert is now ready to run$$$

New:$$$$$$$$$ WSJTX 2.6.0: Now recognises the new ARRL DIGI special operating mode.$$$$$$ $$$Changes:$$$$$$$$$ NET 6 Desktop Runtime: When JTAlert experiences internal errors attributed$$$ to the NET 6 Desktop Runtime not being installed or a corrupted (unlikely)$$$ install; an error popup window is shown as well as the Help file section for$$$ that error (# 2601). JTAlert will shutdown on detection of this error condition.$$$$$$ Log Fields Display: The Time field has been removed.$$$$$$ $$$Fixes:$$$$$$$$$ Callsigns Window: Alphabetic sorting of callsigns backwards. Descending$$$ was ascending and ascending was descending.$$$$$$ Callsigns Window: Callsign tooltip showing utc time in 12 hour format without$$$ the am/pm indicator. Now changed to 24 hour format.$$$$$$

For more details refer : https://hamapps.com/php/notes.php?file=jtalert