Re: [ARRL-LOTW] "Trusted QSL" version 1.14 is available for beta testing
- Ok, I see the warning screen only if the QSO has been upload with V. 1.14. So I guess the only way to bring my logs up to date with 1.14 is to upload my entire log one time. Should everyone do this? One other quick question. Why is the warning screen only blaming my choice of logger? When it was the users(me) fault that the dupe was uploaded and not the logger?KeithFrom: Dave AA6YQ <aa6yq@...>
Sent: Wednesday, April 3, 2013 9:04 AM
Subject: RE: [ARRL-LOTW] "Trusted QSL" version 1.14 is available for beta testing
From: mailto:ARRL-LOTW%40yahoogroups.com [mailto:mailto:ARRL-LOTW%40yahoogroups.com] On Behalf Of Pete Ennis>>>AA6YQ comments below
Sent: Wednesday, April 03, 2013 10:53 AM
Subject: Re: [ARRL-LOTW] "Trusted QSL" version 1.14 is available for beta testing
How is this taking place? If I upload a single duplicate QSO with AClog 3.3 I see no notice.’
>>>TQSL 1.14 only considers a QSO a duplicate if1. That QSO was previously digitally signed by TQSL version 1.14 (or later)
2. Since that QSO was last digitally signed,
- neither its callsign, band, mode, satellite, or station callsign have changed
- no component of the “Station Location” with which the QSO was digitally signed has changed
>>>In your test, did you attempt to upload the QSO from TQSL 1.14 a second time?73,
From: Dave AA6YQ <mailto:aa6yq%40ambersoft.com>
Sent: Tuesday, April 2, 2013 6:17 PM
Subject: [ARRL-LOTW] "Trusted QSL" version 1.14 is available for beta testing
Over the past 4 months, Rick K1MU, Robert KC2YWE, and I have rebooted the Trusted QSL project from which the TQSL and TQSLCert
applications and the TrustedQSL library are built. After considering input from ARRL Management, from the ARRL’s LotW Support Group,
and from this ARRL-LotW Yahoo Group, we established a set of priorities that would be addressed by a sequence of incremental
releases. The first release in this sequence is version 1.14, in which
1. Log files can be signed and uploaded over the internet to LotW in one operation.
2. Errors in Station Locations are reported (e.g. incorrect CQ and ITU zones).
3. QSOs that need not be re-submitted (“duplicates”) are brought to the user’s attention.
4. Error reporting has been improved.
5. Installation on Windows has been improved.
6. Users are notified when a new version becomes available.
7. Documentation has been improved.
A small group of testers began exercising version 1.14 on March 10th; this testing exposed several defects, all of which have been
corrected. We are now ready to begin the next stage of testing: every member of this Yahoo Group is invited to download version
1.14, install it, and give it a try. Questions, defect reports, and suggestions should be posted here.
The current release candidate v1.14-rc5 is available via
You can review the documentation for v1.14-rc5 before you download and install it:
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1430 / Virus Database: 2641/5722 - Release Date: 04/03/13
- Thanks Robert. TQSL V1.14 now reinstalled and a new tq8 file just uploaded. Will check the status in the morning.73,
Gary AL9A----- Original Message -----From: Robert KC2YWECc: Gary AL9ASent: April 07, 2013 8:18 PMSubject: Re: [ARRL-LOTW] "Trusted QSL" version 1.14 is available for beta testingOn 4/8/2013 12:07 AM, Gary AL9A wrote:
Oh boy, this is getting to be even more fun. Went to Unistall and got this error message. "C:\Program Files\TrustedQSL\unins000.dat does not exist. Cannot uninstall."
So really briefly, the problem is that when you did a "last known good" setting, it restored a registry backup. But that doesn't touch the files, so I think the files and the registry information pointing to them is just out of agreement.
As a simple fix, go into C:\Program Files\TrustedQSL and delete everything in there. It's OK - your certificates and locations are stored somewhere else (we won't touch that). Then the 1.14 installer should run fine. The problem is that it's trying to run the uninstaller for 1.13, but it's failing (as you see when you do it manually) and so the installer gives up. If you delete all the files, it won't think it's installed and it should install normally. Afterwards, you should be able to uninstall and install it normally.