When you imported the contest log, did you *check* the Station Callsign
box in the "Replacement Options" filed and enter "N0S"? Did you *ALSO*
*UNCHECK* the "substitute N0FY for missing station callsigns" box in
the "Substitution Options" field if it is checked?

When you export the contest QSOs for LotW, do their "Station Callsign"
say "N0S"?

When you export the contest QSOs for LotW, does the "Station Callsign"
in the "LotW Operations" field on the QSL tab say "N0S"?

73,

... Joe, W4TV

I should clarify that I don't have any issue with the Import function and have done so before.? It is the fact these QSOs were done under the call N0S which was assigned to me for the contest and not my call N0LF.? I can't seem to get it to work.
I've imported the QSO's
I've setup a station location for NOS, but it pulls call N0FY ( I'm guessing because N0S is a temporary and a sub certificate to N0FY)
I then have filtered the log for this set of QSOs and using the? Add All option it is ready to generate 733 entries.? But it then fails because the call sign is not N0FY.?
I know there should be a way to make this work, I'm just not getting there.
Any help is appreciated.

You have too exclude the c:\DXLABS from being scanned. Windows Security | Virus & Threat Protection | Manage Settings |? Add a Exclusion, then do the upgrade again. It took a while for me to find this, hope it helps.

Dave,

Sorry to come back to this issue.
I *STILL* have the same problem and daily I have to download the eQSL images one by one.
Not having seen in the past 6 weeks any other user raising the same problem I *DO* suspect that there is a mis-setting in my DxK (actually v. 15.4.9) prg.
Could this be the case?
What do I have to recheck?

Thanks and best regards


Carlo IK2RPE



-----Messaggio originale-----
Da: [email protected] <[email protected]> Per conto di Dave AA6YQ
Inviato: giovedì 27 febbraio 2020 15:47
A: [email protected]
Cc: Dave Morris N5UP <N5UP@...>
Oggetto: Re: [DXLab] Problem in downloading eQSL images

+ AA6YQ comments below

I (just) recently experienced problem in dowloading (just few, 5/6) eQSL images.
The following warning appears: "from eQSL.cc: PROCESSOR OVERLOAD - THROTTLING INVOKED -->"
I have the latest DxK (v. 15.4.3)
Something changed in the 15 second interval? Can i intervene (where ??) to extend the 15 seconds to lets say to 20?

+ The rate at eQSL images are downloaded from eQSL is as specified by eQSL. If this eQSL announces that this rate should be changed, I will change it.

73,

Dave, AA6YQ







--
Questa email è stata esaminata alla ricerca di virus da AVG.

I found this morning when I booted everything up that Windows 10 Windows Defender has also quarantined commander.? I've never had that happen in the past but a quick restore got it back.

I also experienced a problem this morning when I cut on my computer and started up the suite.? Commander was gone and would not start. After looking I found Windows Defender on Windows 10 had moved commander to quarantine.? I restored it and all is well again.

开云体育

How can I save the settings tp appear from session to session?

t u 73 Dwight NS9I

Last night I downloaded the new TQSL version and upload three QSOs I made yesterday. I then ran sync and it worked, with the correct dates and only 13 QSOs reported. So whatever it was appears to be fixed.

+ AA6YQ comments below

I've found that MS virus shield identify CI_V Commander executable as a trojan.

And put C:\DXLab\Commander\CI-V Commander1453.exe in quarantine.
This is the problem: !cl&threatid=2147723317

+ See <>

+ After you satisfy yourself that Commander1453.exe is not infected, direct your anti-malware to "unquarantine" it.

73,

Dave, AA6YQ

I've found that MS virus shield identify CI_V Commander executable as a trojan.
And put C:\DXLab\Commander\CI-V Commander1453.exe in quarantine.
This is the problem:

--
--
73 de Leo IZ5FSA

+ AA6YQ comments below

Thanks for replying, but as can be seen from the screen print link I sent, i already have 3 column and "Include QSL Mgr && Pse/Tnx QSL" box selected.
As can be seen from the screen dump the "bottom line font" window is greyed out.
Sorry to be pedantic, this is most frustrating...

+ On the Main window's QSL tab, is the "QSL Via" panel set to "3-column labels" ?

73,

Dave, AA6YQ

Thanks for replying, but as can be seen from the screen print link I sent, i already have 3 column and "Include QSL Mgr && Pse/Tnx QSL" box selected.
As can be seen from the screen dump the "bottom line font" window is greyed out.
Sorry to be pedantic, this is most frustrating...
Pete T
Oh2euu

+ AA6YQ comments belo-w

I am set up for qsl labels 3 columns x 8 labels, I want to change the bottom line font size (bigger) but the bottom line font is greyed out - I can't select it.

+ On the Main window's QSL tab, set the "QSL Via" panel to "3-column labels"; then on the "QSL Configuration" window's "QSL Labels" tab, check the "3-column QSL Labels" panel's "Include QSL Mgr && Pse/Tnx QSL" box.

Also, is there a setting to bring the bottom line text higher up the label?

+ The position of the "bottom line" text is fixed.

73,

Dave, AA6YQ

I am set up for qsl labels 3 columns x 8 labels, I want to change the bottom line font size (bigger) but the bottom line font is greyed out - I can't select it.
Also, is there a setting to bring the bottom line text higher up the label?

73' Pete T
Oh2euu

+ AA6YQ comments below

A new version of TQSL showed up today as well., I assume this may be in response to some of the upload issues for the last few
weeks???

+ No. The upload issues to which you refer were entirely attributable regressions in the LoTW Server.

+ Here's the content of TQSL 2.5.2:

Major feature Additions:

When a log is signed by TQSL, the station details (Callsign, DXCC entity, Gridsquare and other QTH details provided by the selected
Station Location (and Callsign Certificate) are compared to the details provided by the log. When the log states that the US State
is one value but the Station Location gives another, TQSL rejects that QSO. This will allow detection of errors where a station
location is incorrectly chosen. This feature requires that the log provide station details, which previously were not used by TQSL.
Once a logging program supplies these (MY_STATE, MY_DXCC, MY_CQ_ZONE, etc.) then TQSL will validate them against the log. Cabrillo
logs now use the "My Callsign" field to verify that the QSOs are for the correct callsign.

Optionally, a station performing roaming operations (multiple gridsquares) can choose to have TQSL assume that the log is correct.
When callsign or QTH are provided with the log, TQSL will update the details on the upload to Logbook automatically. This behavior
is enabled by selecting "Override Station Location with QTH details from your log" on the "Log Handling" preference page.

When submitting requests for US 1x1 callsigns, which must always be a signed request, ensure that the flow properly marks the
callsign as 1x1, and that the requester has a valid callsign certificate that can be used to sign that request.

Minor Updates:

- Add diagnostic log lines suggested by David, W1HKJ.

- Fix centering of date fields in the date range prompt dialog box.

- When a user is changing the language, the current language is now selected in the language selection dialog.

- TQSL now handles Unicode/UTF-8 format "Cabrillo" files by ignoring the extra bytes before the "START-OF-LOG" signal.

- If a BAND is provided for a QSO along with a FREQ, where that frequency (or receive frequency) is outside the related ham band,
ignore the FREQ setting.

- Ensure that messages from TQSL are properly translatable - some long messages were not entirely translated.

Defects Corrected:

- TQSL now issues an error message when an unrecognized file is loaded as a callsign certificate file. Previously, TQSL simply
ignored the invalid file.

- When TQSL is verifying a US callsign, it could fail and reject a callsign certificate request if the data from the FCC had become
corrupted. TQSL now ignores the data in many of these cases by doing additional lookups of known good callsigns to verify that the
ULS data is valid. TQSL now provides the last update date for the ULS database to the message displayed saying that the ULS data is
missing. When fetching the ULS data fails, TQSL no longer rejects callsign certificate requests, which are allowed to work without
address data.

- TQSL now reports when it is unable to open the files needed to connect to Logbook. There were cases where critical files were
missing from the installation, but the error displayed did not provide useful guidance for correcting the error.

- When https (Secure) connections to Logbook fail, tqsl now falls back to trying insecure (http) requests. This allows systems with
anti-virus software that interferes with network connections to recover. A system running such software is inherently insecure, so
bypassing https is a reasonable workaround.

- ULS checks are no longer performed for US 1x1 callsigns.

- Ensure that expired or otherwise invalid certificates in the chain verifying a user Callsign Certificate are properly reported.
This fixes an issue where in some cases (TQSL on Mac) trying to install an expired callsign certificate (an out-of-date TQ6 file),
would cause an unexpected error "unable to get local issuer certificate". Trying to load an expired TQ6 file now causes an
appropriate error message.

- Correct the behavior when backing up in the Callsign Certificate request wizard so that spurious pages are not displayed.

+ From

<>

73,

Dave, AA6YQ

+ AA6YQ comments below

Yes. It still shows the same date, and still updates the same 900 QSOs.
That was as of this morning.

+ Please attach the file

LOTW_QSOS_ADI.txt

+ from DXKeeper's Databases folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

Yes. It still shows the same date, and still updates the same 900 QSOs.

A new version of TQSL showed up today as well., I assume this may be in response to some of the upload issues for the last few weeks???


Dave
NR1DX

--
This email has been checked for viruses by Avast antivirus software.

This release

- informs the user when a "Sync LoTW QSOs", "Sync LoTW QSLs", or "Update from LoTW" operation produces a "Username/password
incorrect" response from LoTW; in previous versions, the user had to inspect the file received from LoTW to see this error message

- enables the "Sync LoTW QSOs", "Sync LoTW QSLs" functions to work correctly when the CTRL key is depressed after the breaking
changes made by the ARRL to LoTW's lotwreport programmatic interface (tnx to Vince VA3VF)


Notes:

1. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"


2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<>


3. After upgrading, to revert to the previous version of DXKeeper, see
<>


DXKeeper 15.4.9 is available via the DXLab Launcher and via



73,

Dave, AA6YQ