The latest JTAlert version 2.60.0 is now
available at https://hamapps.com/JTAlert/
toggle quoted message
Show quoted text
Full release notes are available at the end of this message.
*** IMPORTANT : CRITICAL ***
This version requires the Microsoft NET 6 Desktop
Runtime to be installed. The old out-of-support NET 5 Desktop
Runtime will not work with this JTAlert release.
The official direct download links for the NET 6 Desktop Runtime
*** WARNING ***
Due to significant internal code changes the
Callsigns window configuration will be reset to its default.
You will need to set your personal Callsigns window options (via
the gear icon, bottom-right of the window in the statusbar)
This release includes...
Please review the release notes at the end of
- MSHV support (limited)
- Callsign override management
- Additional DXKeeper automation
- 2 additional Wanted Callsign Alerts.
- New callsigns display customization.
de Laurie VK3AMA
*** IMPORTANT : CRITICAL : This version requires the NET 6
Desktop Runtime ***
- NET 6 Desktop Runtime: This version will not work with the
old no longer
supported by Microsoft NET 5 Desktop Runtime. See the
JTAlert download page
on HamApps.com for official Microsoft download links for
the Desktop Runtime.
- MSHV support: Support for MSHV has special restrictions.
Only a single instance
of the 64bit MSHV is supported, 32bit MSHV is not
supported. MSHV must be set
to use multicast UDP on 220.127.116.11 port 2237, other
addresses and ports will not
work. See the "MSHV UDP Setup" help file topic.
- Callsign override management: Useful for special event
stations using obscure
callsigns that don't accurately convey their operating
location or those pesky
US based stations using KH6, KG4 or KL7 callsigns that
have not made it into the
callsigns database. There is no limit on the number of
overrides that can be set.
Open via the "Settings -> Manage callsign overrides
..." menu. Changes made via
this window will be seen by JTAlert in real-time, but if
you are setting an
override for a callsign that has already been decoded in
your current JTAlert
session you will need to restart JTAlert so that old
cached location data is cleared.
- DXKeeper Automation: New setting to instruct DXKeeper to
deduce missing QSO data
like ARRL sections. This is off by default, see the main
JTAlert Settings window,
"Logging -> DXLab DXKeeper" section.
- Callsigns Window: New option to clear callsigns when a
mode change has occurred.
See the "Automation" section of the Callsigns window
Options popup (click gear icon)
- Callsigns Window: New option to replace Country name
display with the callsigns 4
character grid when operating on 8m and lower (vhf
bands). See the "Callsigns"
section of the Callsigns window Options popup (click the
- Wanted Callsigns Alert: Two additional, independent,
Wanted Callsigns Alerts.
New options to restrict a Wanted Callsign alert to either
HF, VHF or all bands.
See the "Alerts -> Miscellaneous Alerts" section of
the main JTAlert window
Settings window. Open via the "Settings" menu or use the