Keyboard Shortcuts
Likes
- DXLab
- Messages
Search
|
Re: QSL Labels or Cards
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Saturday, March 05, 2016 12:31 PM To: ' Dave AA6YQ' aa6yq@... [dxlab] Subject: [dxlab] QSL Labels or Cards I was trying to get a few cards and or labels done. When I preview a single label, it always shows the printing as horizontal. The label is shown as vertical. The printer is a Dymo LabelWriter 450. I don't see the Avery 4150 as an option (labels I have).In the "QSL labels and address labels" panel on the "QSL Configuration" window's Printer tab, change the setting in the "Single- Label Orientation" sub-panel. That's a function of your printer driver. With printing directly on the cards, it does not see the custom paper type I have added to the print engine. That's a function of your printer driver. If I select 3x5, all I get is different error messages depending on what I choose. I am using a Brother HL-5250dn. 73,Without knowing what the error messages say, one can only guess: try selecting a larger paper size. Dave, AA6YQ |
|
Which contest?
hello,
I have just logged a qso with AB1WR (just for ME still missing for WAS). Searching for a contest calendar on the ARRL web site it seems that this week-end contest is called "International DX-Phone". What is the contest to log in DXKeeper? The most likely candidate that I've found is "ARRL-DX-SSB". Is it correct? Thank you. -- 73 de Salvatore (I4FYV) |
|
QSL Labels or Cards
I was trying to get a few cards and or labels done.
When I preview a single label, it always shows the printing as horizontal. The label is shown as vertical. The printer is a Dymo LabelWriter 450. I don't see the Avery 4150 as an option (labels I have). With printing directly on the cards, it does not see the custom paper type I have added to the print engine. If I select 3x5, all I get is different error messages depending on what I choose. I am using a Brother HL-5250dn. PC is running Windows 10. TNX Will WC2L -- William Liporace WC2L or AR-Cluster Node telent dxc.wc22l.com or 144.93 MHz wc2l@... |
|
Re: UPDATE COMMANDER 12.1.5
开云体育>>>AA6YQ comments below ? From: dxlab@... [mailto:dxlab@...]
Sent: Saturday, March 05, 2016 11:32 AM To: dxlab@... Subject: [dxlab] Re: UPDATE COMMANDER 12.1.5 I am having a problem with Commander 12.1.5 too. ?When I try to start it I get the blue pinwheel and the computer locks up. ?I am using Win 10. ?It all worked fine before the update. ? >>>Be sure your firewall and anti-malware apps are configured to consider Commander 12.1.5 to be safe. ? ????? 73, ? ??????????? Dave, AA6YQ |
|
Re: Not logged in to QRZ
Yes, pathfinder has been working here for years with auto login. ?Think I found the problem. ?My anti-virus engine updated yesterday. ?I had to enter and exception for qrz.com for pathfinder auto login to work. ?Otherwise all other functions are nominal.
Thanks again Dave for your support. 73, Bob |
|
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 |
William WC2L