locked JT-Alert 1.5.0 now available for download.
Laurie, VK3AMA <groups03@...>
JT-Alert 1.5.0 is now available for download at http://Ham-Apps.com/
Note: There is no help file at present and the new style Configuration/Settings Form still requires some updates to its instructional text, but the functionality is 100% working.
Note: JT-Alert 1.5.0 comes bundled Sounds and Callsign databases (US States, LoTW & eQSL) for WAS alerts and Callsign flagging of LoTW/eQSL membership. In a future release, these databases will be moved to a separate installer with an integrated updater. Sounds will also be moved, in a future release, to a separate installer.
All Configuration and Settings data is saved to a file store in the user's "Local App Data" area (typically C:\Users\\AppData\Local\Ham-Apps\JT-Alert\ under Win7 and C:\Documents and Settings\\Local Settings\Application Data\Ham-Apps\JT-Alert under WinXP). These locations cannot be changed and are the folders recommended by Microsoft. Settings file, session files, B4 Log and ADIF Log are stored here and don't cause security issues or the need to run JT-Alert as administrator if they were stored in the JT-Alert program directory under Vista or Win7.
Important Notes on Sound Wave Files:
Sounds are no longer stored in a Sounds folder under the JT-Alert folder (which was needed for WAS announcements). They are now stored in the Windows "Common App Data" area (typically "C:\ProgramData\Ham-Apps\JT-Alert" under Win7 and "C:\Documents and Settings\All Users\Application Data\Ham-Apps\JT-Alert" under WinXP). This allows for different JT-Alert versions to be installed simultaneously (starting with 1.5.0) to share a common single install of Sound files.
Important Notes on Supported Logs:
If you select one of the supported Logger format logs (including standard ADIF), that log is used for B4 testing and the use of the inbuilt JT-Alert B4 log file is NO longer used. When selecting a supported Log, be sure to check the Log specific settings page to setup the log path or ODBC DSN name.
If your preferred logger is not supported, it is best to select the ADIF log as that will record additional QSO data (Name, QTH, Grid, DXCC, State, ITU zone, CQ zone and QSL request) that can be imported by you logger at a future time.
Important Notes on Worked B4 Log:
If you don't want to record the additional log detail provided by the ADIF log and not, at a later time, import into your
logger, there is an inbuilt MSAccess .mdb file log that will record QSOs and will identify worked B4 Callsigns. Go to the "JT-Alert Worked B4" page of the Setup and check that the File exists (it should have been moved from your old JT-Alert.mdb file it it existed). If the path is empty, create a new file (don't create in the JT-Alert program folder, but use the preferred default location) and import an ADIF QSOs file from your logger to initially populate the file.
Notes on new LoTW/eQSL Callsign flagging:
Decoded Callsign flagging of LoTW and/or eQSL(AG) membership uses databases automatically installed by JT-Alert. If you have DXLabs installed it is possible to configure JT-Alert to use the DXLab databases. The Callsign flagging involves a small triangle being painted (user configurable colors) to the top left corner of the JT-Alert decoded callsign.
I think that covers the important changes.
If you experience problems or have questions post a message to this Yahoo Group. Please don't reply to this message with your questions, but instead start a new message with a subject line that reflects the question or problem.
de Laurie, VK3AMA