Trusted QSL Software Beta Release
Reports, comments and any other feedback on this release may be sent to firstname.lastname@example.org
Beta version: TQSL v2.0 Release Candidate 7 [v2.0-rc7-7-gf5be82b]
tqsl-2.0.msi -- Microsoft Installer (3.8 MB)
Mac OS X
tqsl-2.0.dmg -- Apple Disk Image (8.4 MB)
tqsl-2.0.tgz -- Source tar archive, gzipped (2.1MB)
New & Corrected in Current Release
There are major changes in TQSL v2.0. Please read the Release Notes
Updated in RC7:
This release corrects the following defects reported since TQSL 2.0-RC6 (as well as severl enhancements).
- Correct defect that would cause TQSL to crash on startup if the certificate store could not be read
- Display an error to the user if the station location data file or certificate store cannot be opened
- When adding a Station Location, properly initialize the callsign to correspond to the selected callsign certificate/location (not the first call found)
- Fix the Station Location editor to not show duplicated DXCC entities
- Check for an existing valid Callsign Certificate before starting to sign a log - if not, display an error and abort
- Updates to documentation including certificate acceptance, station location modifications, and multi-computer scenarios
- Fix defect that caused double-clicking a .TQ6 file to fail
- Update the message in the callsign certificate request window to better explain when a request should be signed
- Correct the error messages on TQSL update check failures to properly explain what was going on.
- Increase the TQSL update timer to allow for slow connections
- Update to the current (v2.5) LoTW configuration file
- Strip leading and trailing spaces from IOTA, WPX, etc. Leaving these causes signature verification to fail
- Bring up the GUI before performing the automatic update check so it doesn't appear that TQSL has hung on startup.
Updated in RC6:
This release corrects the following defects reported since TQSL 2.0-RC5 (as well as severl enhancements).
- Strip leading spaces and trailing spaces from station locations passed on the command line to help correct for common user errors.
- Display LoTW errors returned when a callsign certificate request failsfor some reason.
- Record multiple outstanding certificate requests and delete the pending status if the user deletes the corresponding callsign certificate.
- Remove an errant "M" on the certificate request signing page. Properly wrap the text on that page for MacOS.
- The TQSL version number is always displayed for command line usage unless "-n" (check for new TQSL, configuration and program updates) is used.
- Added a new icon for TQSL contributed by K1GQ. The default shortcut icon has not changed, but the new icon is available for selection.
- Display an error when the TQSL configuration files (station locations, callsign certificates, etc.) can't be opened. All earlier versions of TQSL ignored these errors and started up with no callsign certificates or station locations defined.
- When a user selects a callsign in the Station Location window then clicked on "Create new Station Location", the DXCC entity in the station location wizard used the entity of the first callsign, not the selected callsign.
- The station location editor no longer shows multiple entries with the same DXCC entity in the entity selection pulldown list when there are multiple callsign certificates for a given callsign.
Updated in RC5:
- Corrects defect introduced in RC4 that caused certifcate requests to be truncated and therefore not recognized by LoTW.
- Corrects crash that would occur when exiting TQSL if unreadable files were present in the TQSL working directory.
Updated in RC4:
- Band limits relaxed for the 30m, 17m, and 12m bands to allow QSOs with "18.0 MHz" for example to be signed without generating an error.
- The "Station Location" properties for some entities (Canada was reported) had a corrupted display including the string "RU_OBLAST" that was chopped off. These entities now display correctly.
- The messages displayed and online help now explain to users that "you have no certificates" means that you have no certificates installed on the computer being used.
- Command line signing has had several fixes to keep unexpected dialog boxes from appearing when prompting for passwords, error handling, etc.
- The "Ignore errors?" dialog box that appears when invalid QSOs are found in a log being signed now explains what the options do (ignore them or cancel signing).
Updated in RC3:
This release fixes two serious problems reported for 2.0-rc2:
- If you minimized the TQSL window then closed it, upon restart the TQSL window was sized far too small to be usable. This release does not store the position/size when minimized, and will not allow the main window to be too small on startup.
- If you received an error message while signing a log (out of date range, bad call, bad mode, etc.) and chose to NOT ignore errors, TQSL would sign and upload the log as of the point where the error was found rather than discarding it. This release discards the log and cancels the operation when the user chooses "No" when asked to ignore errors.
- Minor changes made in the handling of unknown Cabrillo log formats. TQSL now automatically detects the "call-worked" field from a Cabrillo log without additional user configuration for Cabrillo logs for many (most) contests.
Updated in RC2:
This update has the following changes:
- Add "TQSL" to the title of the 'update available' window so it's clear that it refers to a TQSL update.
- Fix defect that caused "Sign and Save" operations to discard the log without signing it.
- Provide the callsign involved when callsign certificate loads fail.
- Track multiple pending certificate requests and warn the user when they try to create a duplicate request.
- Improve the error reporting when attempts to update the TQSL configuration file fail.
- Update file hadnling to use backslashes for Windows to avoid mixed forward and backward slashes.
- Update the signing process display to include processed/duplicate/error count.
- Recover from invalid ADIF files by ignoring up to the next end of record mark.
- Update the documentation to describe how menus work on Mac OS X.
- Remove dead output file when signing fails or is cancelled.
- Fix a crash when a station location references an invalid DXCC entity.
- Display DXCC entity name, not entity number, in messages displayed to users.
- Moved Diagnostic Mode menu entry to the File menu so it works properly on OS X.
- Correct reporting of RX_FREQ errors to display the invalid input.
- Fix range for subsquare values (Allow 'a' through 'x').
- Display the expected DXCC entity when reporting "No callsign certificate" when trying to use a station location.
- Try to automatically determine the callsign field in an unknown Cabrillo log file, allowing the file to be processed without defining a custom log format.