locked #Announcement #NewRelease : JTAlert 2.12.2 is available for download #Announcement #NewRelease

HamApps Support (VK3AMA)

Note: JTAlert 2.12.2 doesn't support WinXP or Vista (there will be NO future JTAlert releases supporting XP or Vista).

Visit https://HamApps.com for the download link and upgrade/install instructions and a link to the official Microsoft .NET Framework 4.7.2 download.

Release Notes...
2.12.2 (18-JUL-2018)

    - Settings will now show a "JTAlert requires a restart" popup message when
      the file for ADIF or MIXW logging is changed.
    - Miscellaneous internal code changes to improve responsiveness.
    - Additional debugging data to help diagnose some of the random errors
       encountered by some users, especially those using underpowered PCs.

    - Non-US States/Provinces, when available from an XML lookup or previous
       QSO in the log, not being logged. This affected all supported loggers.
    - US Counties, when available from an XML lookup or previous QSO in the
       log, not being logged to MIXW log.
    - Random non-clearing and appending of current period Callsigns to the end
       of the last (non-cleared) period callsigns. On some slower PCs combined
       with a busy Band, this could happen for a number of consecutive periods.
    - A random defect where the number of display lines in the Decodes History
       window was increasing over time, rather than being automatically trimmed
       as new decodes were added.

de Laurie VK3AMA

Join Support@HamApps.groups.io to automatically receive all group messages.