Keyboard Shortcuts
Likes
- DXLab
- Messages
Search
|
FW: [ARRL-LOTW] TQSL 2.2.1 Beta Test kit now available
开云体育Note that with TQSL 2.2.1 installed, you will no longer see a progress bar when you invoke DXKeeper’s “Upload to LoTW” function. ? ?????? 73, ? ????????????? Dave, AA6YQ ? From: ARRL-LOTW@... [mailto:ARRL-LOTW@...]
Sent: Saturday, March 05, 2016 8:42 AM To: yahoogroups Subject: [ARRL-LOTW] TQSL 2.2.1 Beta Test kit now available Please assist us with testing a release candidate for an updated TQSL release. This is TQSL v2.2.1-rc2 (Release candidate 2), which is available from the following links: ? Windows:? Mac:? Unix:? ? This release corrects defects and adds some minor updates since TQSL 2.2. ? Defects corrected: 1. When installing a .TQ6 file succeeded, TQSL would delete any other certificate files for that callsign, under the assumption that they were no longer needed. If an operator with a pending callsign certificate request would then install a TQ6 file for their former callsign certificate (one that was being renewed), the private key for the pending renewal could be deleted. This would cause the subsequent TQ6 file to fail to install.? TQSL no longer deletes anything unless it can verfify on-line with LoTW that the installed certificate is the current one. ? 2. When uploading logs, TQSL would always display the progress bar. This should not have been done when signing via the command line when batch mode (-x or -q) ?was enabled. ? 3. When using the language selection dialog, TQSL could cause the main window to appear on a different area of the screen.? The window location is now preserved. In addition, TQSL doesn't destroy and re-create the main window when the language is not changed. ? 4. Updating the LoTW configuration file could fail if the user's home directory contained non-ASCII characters (Windows only). ? 5. Ensure that the password prompt window appears on top of other windows when a password is requested while signing a log. ? 6. Correct defect that would cause Cabrillo "Light" mode QSOs (300 GHz) to be rejected. ? 7. Correct handling of unrecognized ADIF MODE/SUBMODE entries to allow user-defined modes to be used. ? 8. Fix a defect on OSX that would cause an incorrect error message to be displayed when an incorrect password was entered for a callsign certificate. ? 9. Restoring an incorrect .TQ6 file when there is a pending callsign certificate request could cause the pending request to be deleted. TQSL now rejects the invalid TQ6 file and takes no other action. ? New features: 1. TQSL attempts to cleanly close out the duplicates database when the window is closed while a signing operation is underway. ? 2. The certificate properties displays now include "Replaced" and "Expired" indicators. ? 3. Allow an alternate layout for the user interface that moves the status log to a separate tab. This is useful for users with long lists of station locations or callsign certificates. ? 4. Update the duplicates tracking to allow reporting of station location changes when the same QSO is signed from more than one station location. ? 5. Update the ADIF editor to automatically select the appropriate band when a frequency is entered. ? 6. Add "Replaced' and "Expired" tags ?to the callsign certificate properties display. ? As always, any testing you can perform to help verify this release is appreciated. 73, ? ? -Rick -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
|
Re: DDE Changes? CI V Commander V12.xx do not work - V11.9x works
Pierre Dupuis
开云体育Sorry Rich, my first E-Mail was for you.
Thanks for all info.
?
Pierre VE2MP
?
? From: mailto:dxlab@...
Sent: Saturday, March 05, 2016 8:23 AM
To: dxlab@...
Subject: Re: [dxlab] DDE Changes? CI V Commander V12.xx do not work
- V11.9x works ?
?
I agree. There is no reason to do that unless you have installed DXLab under
program files which is not recommended. Running applications as administrator
defeats many of the security features introduced after Windows
XP. On 3/5/2016 7:54 AM, 'Dave AA6YQ' aa6yq@... [dxlab]
wrote:
|
|
Re: DDE Changes? CI V Commander V12.xx do not work - V11.9x works
Pierre Dupuis
开云体育Thanks Dave for reply.
Yes I was running applications as administrator under program files.
I will erase and try again and follow all recommended files.
?
Merci...Pierre? VE2MP
?
? From: mailto:dxlab@...
Sent: Saturday, March 05, 2016 8:23 AM
To: dxlab@...
Subject: Re: [dxlab] DDE Changes? CI V Commander V12.xx do not work
- V11.9x works ?
?
I agree. There is no reason to do that unless you have installed DXLab under
program files which is not recommended. Running applications as administrator
defeats many of the security features introduced after Windows
XP. On 3/5/2016 7:54 AM, 'Dave AA6YQ' aa6yq@... [dxlab]
wrote:
|
|
Re: DDE Changes? CI V Commander V12.xx do not work - V11.9x works
开云体育I agree. There is no reason to do that unless you have installed DXLab under program files which is not recommended. Running applications as administrator defeats many of the security features introduced after Windows XP.? 73, Rich - W3ZJ On 3/5/2016 7:54 AM, 'Dave AA6YQ'
aa6yq@... [dxlab] wrote:
|
|
Re: Not logged in to QRZ
开云体育Auto-login is working here, so it’s unlikely that there’s been a change in QRZ.com’s login procedure. ? Has Pathfinder never been able to automatically log in to QRZ.com, or is this new behavior? If the latter, when did it first start, and what changes did you make to your hardware or software around that time? ? ?????????? 73, ? ?????????????????? Dave, AA6YQ ? From: dxlab@... [mailto:dxlab@...]
Sent: Saturday, March 05, 2016 7:01 AM To: dxlab@... Subject: [dxlab] Not logged in to QRZ ? Getting up pop up indicating not logged into QRZ. ?I'm setup for auto login via pathfinder. ?If I open pathfinder and login manually it all works. ?I've checked my login and password in pathfinder config and its all good. Only upgrade I did was to DXView recently. ?All modules are up to date. ?Any ideas. ? Bob, N2NF |
|
Re: Not logged in to QRZ
I had that happen to me the other day and I just closed pathfinder and reopened it and it logged me. No clue why I had been using it for some time and now I am not logged in. I figured it was something at their end since it logged me back in when I restarted the app.
I also got a popup on Thursday that said Pathfinder has stopped working and windows closed it. I reopened it and kept going. 73, Bob KB4CL From: dxlab@... [mailto:dxlab@...] Sent: Saturday, March 05, 2016 7:01 AM To: dxlab@... Subject: [dxlab] Not logged in to QRZ Getting up pop up indicating not logged into QRZ. I'm setup for auto login via pathfinder. If I open pathfinder and login manually it all works. I've checked my login and password in pathfinder config and its all good. Only upgrade I did was to DXView recently. All modules are up to date. Any ideas. Bob, N2NF |
|
Re: DDE Changes? CI V Commander V12.xx do not work - V11.9x works
开云体育From a security perspective, it would be better to not run any of your DXLab applications with Administrator privileges. ? ???? 73, ? ????????????? Dave, AA6YQ ? From: dxlab@... [mailto:dxlab@...]
Sent: Saturday, March 05, 2016 4:37 AM To: dxlab@... Subject: RE: [dxlab] DDE Changes? CI V Commander V12.xx do not work - V11.9x works ?
|
|
Not logged in to QRZ
Getting up pop up indicating not logged into QRZ. ?I'm setup for auto login via pathfinder. ?If I open pathfinder and login manually it all works. ?I've checked my login and password in pathfinder config and its all good. Only upgrade I did was to DXView recently. ?All modules are up to date. ?Any ideas. Bob, N2NF |
|
Re: DDE Changes? CI V Commander V12.xx do not work - V11.9x works
Thanks Dave,
that makes my day and I learned a little bit more. Running everything as administrator show, it is working as expected. Haven?t thought about this before - now the problem is solved and I can start again using DDE for my Frontend for DXkeeper. Greetings and have a nice weekend - ARRL SSB is calling Peter DF1LX |
|
Re: DDE Changes? CI V Commander V12.xx do not work - V11.9x works
Funny - there seems to be the fault in DXlablauncher somehow - cannotIs Launcher set to start Commander in "Run as Administrator" mode - or are you using "run as administrator" to launch the stand alone version of Commander? You *can not* mix administrator and user modes - run *all* DXLab components with normal (non-elevated user) permissions. Any program that needs to exchange DDE with Commander *must also* run with normal user permissions - not as administrator. 73, ... Joe, W4TV On 3/4/2016 6:10 PM, pkfalkensee@... [dxlab] wrote: Well - I use Windows7 (Windows10 - no thanks) - no software update since several month. |
|
Re: DDE Changes? CI V Commander V12.xx do not work - V11.9x works
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Friday, March 04, 2016 6:10 PM To: dxlab@... Subject: RE: [dxlab] DDE Changes? CI V Commander V12.xx do not work - V11.9x works Well - I use Windows7 (Windows10 - no thanks) - no software update since several month. - I do not use any antimalware Software - sorry - I do not use any Internetsecurity Suite - sorry too Windows Security Essentials is switched off. Firewall is activated. Brain is working :) I just switched back to 12.15 and DDE is working. But I started 12.15 Commander without DXlabLauncer. Now I made a test: Started DXlabLauncher (2.06) and started CMD -> 12.15 starts up. I fired DXlabTest1.3,5 and NO DDE is possible. I killed Commander and Launcher -> started Commander "standalone" -> DDE is working with DXlabTest again. Funny - there seems to be the fault in DXlablauncher somehow - cannot imagine why - but it is reproducable. 73,Windows will not allow two applications to communicate via DDE unless they have the same privilege level. If one application is started with "Run as Administrator" and the other application is not started with "Run as Administrator", they will be unable to communicate via DDE. Dave, AA6YQ |
|
Re: DDE Changes? CI V Commander V12.xx do not work - V11.9x works
Well - I use Windows7 (Windows10 - no thanks) - no software update since several month.
- I do not use any antimalware Software - sorry - I do not use any Internetsecurity Suite - sorry too Windows? Security Essentials is switched off. Firewall is activated. Brain is working :) I just switched back to 12.15 and DDE is working. But I started 12.15 Commander without DXlabLauncer. Now I made a test: Started DXlabLauncher (2.06) and started CMD -> 12.15 starts up. I fired DXlabTest1.3,5 and NO DDE is possible. I killed Commander and Launcher -> started Commander "standalone" -> DDE is working with DXlabTest again. Funny - there seems to be the fault in DXlablauncher somehow - cannot imagine why - but it is reproducable. Greetings Peter DF1LX |
|
Re: Can't log FR1GV
开云体育Hi Dave -I think that's a great idea. The nice thing about this reflector is that all questions are welcome, and the majority of people follow your lead and no one gets flamed. Thanks for setting such a good example for all of us. 73, Bob WB2NVR -- Bob Schaps WB2NVR 914-347-7331 Office 914-262-3535 Cell 914-472-0690 Home |
|
Re: Can't log FR1GV
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Friday, March 04, 2016 3:33 PM To: dxlab@... Subject: Re: [dxlab] Can't log FR1GV I had decided I was going to keep my mouth shut on this issue, but . . . why start now? ;-) One of the reasons I have stuck with this group over the years, and recommended DXLab Suite to friends is because of the excellent support provided. I subscribe to several support groups, and have subscribed to several more in the past. This is the only group I have ever belonged to where a person doesn't get flogged for asking a question. I have never quite understood why someone would subscribe to a support group, and then condemn a person for asking for support. 73,One could speculate as why people do this, but this isn't the "Psychology of Online Interaction" group. Suffice it to say that a group where questions are actively welcomed and nasty responses are not tolerated produces an environment that's enjoyable for both new and experienced users -- just what's needed to keep driving the product forward. Dave, AA6YQ |
|
Re: Can't log FR1GV
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Friday, March 04, 2016 3:24 PM To: dxlab@... Subject: Re: [dxlab] Can't log FR1GV On Mar 4, 2016, at 13:29, aa6yq@... [dxlab] <dxlab@...> wrote: To correct this defect, I am considering the following changes: [large clip of the changes] These changes will immediately inform a user if the log they open is not consistent with the DXCC Database, enabling the user to take corrective action when convenient. How much is this going to add to the time to load the log when I startup DXKeeper? It already goes longer than I like to sit and wait (about 147K entries in the log). it will never again be necessary to invoke the consistency checker.I don't know yet, John, but it will be a one-time cost. Once a log's "last DXCC database version" setting has been initialized, Can you make the implementation of this procedure an option that I can leave turned off (since I have no history of not following the recompute instructions that come with a DXCC database update)? 73,Since it's a one-time cost, I don't think that's necessary. Dave, AA6YQ |
|
Re: Can't log FR1GV
On Fri, Mar 4, 2016 at 2:09 PM, 'Joe Subich, W4TV' lists@...
[dxlab] <dxlab@...> wrote: It's not the same. In my proposal, the need for recompute would be determined by the database maintainer (you), rather than by DXKeeper at runtime. I think it would be simpler to implement, faster to execute, and gives you the flexibility to decide when recompute is appropriate or not. 73, ~iain / N6ML |
|
Re: Can't log FR1GV
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Friday, March 04, 2016 2:57 PM To: dxlab@... Subject: Re: [dxlab] Can't log FR1GV I would suggest that you would create a script to automatically do the recompute when there is a change to the underlying database. This would stop people from having to do it manually after the updates and would insure that the information is correct. 73,Though adding a DXCC entity, removing a DXCC entity, or changing a DXCC entity's "entity prefix" are all relatively rare events, I am very reluctant to have them automatically trigger a recomputation that would stop a user from employing DXKeeper for multiple minutes, depending upon the number of QSOs present in the log and the number of awards being pursued. The user should be informed each time the log is opened that recomputation is required, but initiating recomputation should remain something the user does at his or her convenience. Dave, AA6YQ |
|
Re: Can't log FR1GV
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Friday, March 04, 2016 2:49 PM To: dxlab@... Subject: Re: [dxlab] Can't log FR1GV I think this will stop some questions about the recompute after an database upgrade, from what I remember only it's need if some prefix change. Can/Would the DXCC database version be show above the Recompute button in DXKeeper, Check Progress tab, in bold like DXCC 2.5.2 ? This would be easier to the user determine what DXCC database version he's running, instead of going to the DXView Config window, database tab. 73,Clicking the "Database Info" button at the bottom of the General tab of DXKeeper's configuration window displays the versions of all databases in use, including the DXCC database version. Dave, AA6YQ |
|
Re: DDE Changes? CI V Commander V12.xx do not work - V11.9x works
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Friday, March 04, 2016 2:00 PM To: dxlab@... Subject: [dxlab] DDE Changes? CI V Commander V12.xx do not work - V11.9x works I try to connect via a small Python3 Script to the CI-V Commander via DDE and I am getting "grey" hairs. I use WinSPY and see that there is traffic inside the DXlab Suite. I started DXlabTest1.3.5 and TCPIP works DDE nothing - no value shown. I tried 2 other test programs - which works - shit - what do I incorrect with my small Python script? Well - I fall back from CI-V Commander V12.xx (newes) to V11.95 I belive - and voila - DDE is working again in DXLabTest1.3.5 and I may check now what is going wrong with my Python Script AND NOW it works fine: I did a lot of investigations - and well - something is wrong in DDE in the newest Commander :) 73,Since every DXLab application interoperates with Commander via DDE and there have been no reports here of interoperation failures, Peter, that's unlikely. What's more likely is that one of your anti-malware apps is preventing your application from interoperating with the current version of DDE, or perhaps that you're running on a version of Windows 10 that doesn't correctly support DDE. Dave, AA6YQ |
iain macdonnell