Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
|
Re: "Inbound OQRS" greyed out
Rex Turvin
When you have inbound OQRS "bureau request" or " direst request" you are notified once a day via e-mail from Clublog. My notification comes around 830PM local every night. ?73 NR6M ex: KF7NMD Sincerely, Rex Turvin Vice President CADXA ?www.nr6m.com From: "' Dave AA6YQ' aa6yq@... [dxlab]" To: dxlab@... Sent: Monday, February 29, 2016 5:34 PM Subject: RE: [dxlab] Re: "Inbound OQRS" greyed out
?
>>>AA6YQ comments below
-----Original Message----- From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 6:29 PM To: dxlab@... Subject: [dxlab] Re: "Inbound OQRS" greyed out Sounds straightforward enough, I guess I just need to see it in action. How am I alerted by DX Keeper? >>>Alerted about what? Does it download the requests automatically or do I have to go in every day and check to see if there are new requests? >>>You must click the "Inbound OQRS" button whenever you wish to see if new requests are present. Does Clublog also email me to let me know a request was made? >>>I have received such email messages from Club Log, but I don't know how often they are sent. I guess that's the part I'm unsure about. I have about 15 outgoing bureau card requests in my "add requested" queue (from my last incoming bureau shipment). >>>There is no "add requested" queue. Will these added requests display anywhere else other than when I enqueue requested labels to print? If (fictitious call) XX9XXX requests a bureau card from me, will it display anywhere other than when I go to run bureau labels? >>>If you respond to an incoming bureau card by locating the logged QSO and setting its "QSL Sent" item to 'R', and if the "QSL Via" panel on the Main window's QSL tab is set to anything other than LoTW or eQSL, ithen nvoking the "Add Requested" function will add that logged QSO to the QSL Queue. You could define a script that filters the Log Page Display to contain only QSOs whose "QSL Sent Via" items are set to 'B' and whose "QSL; Sent" items are set to 'R'; invoking that script would then show all QSOs for which a request for confirmation via the bureau has been received. The practical reason for this is that if I get a direct OQRS request (unlikely for a garden-variety stateside station like me) I'd like to send off a card same-day. >>>Then click the "Inbound OQRS" button every day. 73, Dave, AA6YQ |
|
Re: "Inbound OQRS" greyed out
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 6:29 PM To: dxlab@... Subject: [dxlab] Re: "Inbound OQRS" greyed out Sounds straightforward enough, I guess I just need to see it in action. How am I alerted by DX Keeper? Does it download the requests automatically or do I have to go in every day and check to see if there are new requests?Alerted about what? Does Clublog also email me to let me know a request was made?You must click the "Inbound OQRS" button whenever you wish to see if new requests are present. I guess that's the part I'm unsure about.I have received such email messages from Club Log, but I don't know how often they are sent. I have about 15 outgoing bureau card requests in my "add requested" queue (from my last incoming bureau shipment). Will these added requests display anywhere else other than when I enqueue requested labels to print? If (fictitious call) XX9XXX requests a bureau card from me, will it display anywhere other than when I go to run bureau labels?There is no "add requested" queue. The practical reason for this is that if I get a direct OQRS request (unlikely for a garden-variety stateside station like me) I'd like to send off a card same-day.If you respond to an incoming bureau card by locating the logged QSO and setting its "QSL Sent" item to 'R', and if the "QSL Via" panel on the Main window's QSL tab is set to anything other than LoTW or eQSL, ithen nvoking the "Add Requested" function will add that logged QSO to the QSL Queue. You could define a script that filters the Log Page Display to contain only QSOs whose "QSL Sent Via" items are set to 'B' and whose "QSL; Sent" items are set to 'R'; invoking that script would then show all QSOs for which a request for confirmation via the bureau has been received. 73,Then click the "Inbound OQRS" button every day. Dave, AA6YQ |
|
Background colors DXKeeper Log Page Display
Hi, I am trying to change de background colors in DXkeeper log page display. They are 4 settings : Normal, LoTW, eQSL and Both. When I try to change the Normal and eQSL to the same background colors, and then the LoTW and and Both to the same colors, it works until I restart DXkeeper. Default values are always?coming back no matter what I tried to do. My reason of doing this is I don't care about eQSL, so I would like to display all eQSL user the same as Normal user. And LoTW and Both to the same colors, because I only handle LoTW. I do not want to display colors that I have no meaning for me. Anyway, the reason is not so important..... DXkeep do not keep my settings....... Any clues ???? Regards, Jeff VA2SS |
|
Re: "Inbound OQRS" greyed out
Sounds straightforward enough, I guess I just need to see it in action. How am I alerted by DX Keeper? Does it download the requests automatically or do I have to go in every day and check to see if there are new requests? Does Clublog also email me to let me know a request was made? I guess that's the part I'm unsure about.
I have about 15 outgoing bureau card requests in my "add requested" queue (from my last incoming bureau shipment). Will these added requests display anywhere else other than when I enqueue requested labels to print? If (fictitious call) XX9XXX requests a bureau card from me, will it display anywhere other than when I go to run bureau labels? The practical reason for this is that if I get a direct OQRS request (unlikely for a garden-variety stateside station like me) I'd like to send off a card same-day. I usually send bureau cards out at club meetings once a month (I'm a bureau letter manager and get free outbound cards as a perq of the job). |
|
Re: Reload DXLab after IS Reinstall
Dave - Took your first recommendation - Uninstalled DXLab apps tks to the Dell Techs who used Revo Reg Cleaner Pro They cleaned it all out, and then I did a New Download from the DXLab web site. Installed Launcher and used it to install all Apps. Uploaded my DXKeeper Log file and updated all other missing data (I must not have done the Workspace saving correctly since had to re enter most data). Keeper Uploads to LoTW, and other apps seem to work all OK. So, my DX Lab Suite on the problem computer appears to be back up to full operations. . . . and the world is now safe!! ? Thanks for your continuing assistance. ? Best regards, Alan K9MBQ? -----Original Message----- |
|
Re: "Inbound OQRS" greyed out
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 4:52 PM To: dxlab@... Subject: RE: [dxlab] "Inbound OQRS" greyed out OK, I enabled the first option (set QSL to R), since this will probably only ever be used for bureau card requests (I'm betting I'll get maybe a couple per year, tops). I automatically upload everything to eQSL and LoTW so setting those options is irrelevant. (and every QSO is uploaded to Clublog in real time as well). The Incoming OQRS button is no longer greyed out. I pressed it, it flashed a couple of times and put the current date/time as the last time I checked, but those generated requests either didn't come through yet or else I'm not sure where to find them. Assuming they didn't download, what should happen once they do arrive? 73,DXKeeper will inform you of the number of new requests, and set their "QSL Sent" items to 'R'. Invoking the "Add Requested" function on the Main window's QSL tab will add them to the QSL Queue, just as if you'd manually processed incoming QSL cards. Dave, AA6YQ |
|
Re: "Inbound OQRS" greyed out
OK, I enabled the first option (set QSL to R), since this will probably only ever be used for bureau card requests (I'm betting I'll get maybe a couple per year, tops). I automatically upload everything to eQSL and LoTW so setting those options is irrelevant. (and every QSO is uploaded to Clublog in real time as well).
The Incoming OQRS button is no longer greyed out. I pressed it, it flashed a couple of times and put the current date/time as the last time I checked, but those generated requests either didn't come through yet or else I'm not sure where to find them. Assuming they didn't download, what should happen once they do arrive? |
|
Re: Can't Edit Commander User-defined Controls
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 1:06 PM To: dxlab@... Subject: [dxlab] Re: Can't Edit Commander User-defined Controls Commander Version 12.1.1 on Win10. Yes, there was an entry for the Edit window behind the Commander entry in the Task Bar. I clicked on the Edit entry and the Edit panel came up. Sorry for the bother. I know this is a Windows question, but how did manage to do this? <>Windows supports multiple monitors. If the "Use multiple monitors" box on Commander's Configuration window is checked, then Windows can be displayed on any monitor. If your physical monitor configuration changes, or if Windows gets confused, a window can effectively be "lost", meaning displayed by a non-existent monitor. In the past, this happened with some frequency, and this procedure was provided to recover such lost windows: However, every DXLab application has been extended to detect the physical monitor configuration on startup, and automatically relocate a "lost" windows to the primary monitor. Two users subsequently reported lost "spot source" windows in SpotCollector, but that was the result of a failure to employ the "auto relocate" capability when restoring those specific windows, a defect that has been corrected. Your report of a missing window in Commander is the first such report; Commander should have automatically relocated your "lost" Edit window to your primary monitor. 1. on the Configuration window's General tab, check the "log debugging info" boxIf this should happen again, please do the following: 2. terminate Commander 3. start Commander 4. on the Configuration window's General tab, ucheck the "log debugging info" box 5. attach the errorlog.txt file from your Commander folder to an email message describing what happened (e.g. identifying the "lost" window) and send it to me via aa6yq (at) ambersoft.com 73,Thanks! Dave, AA6YQ |
|
Re: DXKeeper QSL Printer config problem
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 1:06 PM To: dxlab@... Subject: [dxlab] DXKeeper QSL Printer config problem I'm in DXkeeper/QSL tab/Config/Printers. Win10 home, production release, all updates. Although my printer visible and selected as desired the Size pulldown doesn't show what is actually available when I go into Windows print server properties for that printer. And specifically it doesn't show the two forms I've defined for that printer: QSL Card and DXK Envelopes. Both of those were defined after installing the printer, all done as admin. While using my "normal" Windows login I can see the printer and the forms in Print server properties and print test pages so it appears that all is properly installed. Yet DXK isn't seeing the forms with those names. Clean boot gives same result. Suggestions? 73,DXKeeper populates each "Paper Size" selector with ~40 standard paper sizes. It then queries Windows to determine if any additional paper sizes are supported by the selected printer, and if so adds those to the "Printer Size" selector. Presumably Windows responds by querying the appropriate printer device driver. Thus if an expected paper size is not appearing the "Paper Size" selector, all I can suggest is that you contact whoever provided your printer driver. Dave, AA6YQ |
|
Re: "Inbound OQRS" greyed out
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 2:35 PM To: dxlab@... Subject: [dxlab] "Inbound OQRS" greyed out I'm interested in using the inbound OQRS functionality. I went into Clublog and generated a bureau QSL request to my own call from a friend's Canadian callsign; in theory this should somehow notify me that I have an inbound OQRS bureau request. How do I activate that feature in DX Keeper, and is Clublog itself supposed to notify me by email when I have such a request?In Club Log, you must activate "Inbound OQRS" for you callsign. Club Log sends email informing you of waiting requests, but I do not know at what frequency such messages are sent. <>The instructions for DXKeeper are here: 73,As described in these instructions, the "Inbound OQRS" button will remain greyed out until at least one of the options in the "Inbound OQRS" panel ("QSL Configuration" window, "Club Log" tab) is enabled. Dave, AA6YQ |
|
Re: Reload DXLab after IS Reinstall
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 1:16 PM To: DXLab Group Subject: RE: [dxlab] Reload DXLab after IS Reinstall OK, Dave. Will uninstall and do a new install. Any suggestions re a Windows Registry Cleaner? Also, I can open Commander and DXKeeper and use all OK, incl uploading recent QSOs to LoTW. However, once I open WW, it will not shut down.I have no experience with Registry Cleaners. A Registry Cleaner - I forget which one - was at one time recommended in "Getting Started with DXLab", but a user reported that it caused damage, so I removed the recommendation. 73,You could try leaving Commander and DXKeeper installed, an only uninstall/clean/re-install the applications that aren't working correctly. However, there is always the possibility of hidden damage. Dave, AA6YQ |
|
"Inbound OQRS" greyed out
Hi Dave,
I'm interested in using the inbound OQRS functionality. I went into Clublog and generated a bureau QSL request to my own call from a friend's Canadian callsign; in theory this should somehow notify me that I have an inbound OQRS bureau request. How do I activate that feature in DX Keeper, and is Clublog itself supposed to notify me by email when I have such a request? |
|
Re: Reload DXLab after IS Reinstall
OK, Dave. Will uninstall and do a new install. Any suggestions re a Windows Registry Cleaner? Also, I can open Commander and DXKeeper and use all OK, incl uploading recent QSOs to LoTW. However, once I open WW, it will not shut down. Alan K9MBQ -----Original Message----- |
|
Re: Can't Edit Commander User-defined Controls
Commander Version 12.1.1 on Win10. Yes, there was an entry for the Edit window behind the Commander entry in the Task Bar. I clicked on the Edit entry and the Edit panel came up. Sorry for the bother. I know this is a Windows question, but how did manage to do this?
|
|
DXKeeper QSL Printer config problem
Jim Miller
I'm in DXkeeper/QSL tab/Config/Printers. Win10 home, production release, all updates. Although my printer visible and selected as desired the Size pulldown doesn't show what is actually available when I go into Windows print server properties for that printer. And specifically it doesn't show the two forms I've defined for that printer: QSL Card and DXK Envelopes. Both of those were defined after installing the printer, all done as admin. While using my "normal" Windows login I can see the printer and the forms in Print server properties and print test pages so it appears that all is properly installed. Yet DXK isn't seeing the forms with those names. Clean boot gives same result. Suggestions? jim ab3cv |
|
Re: Reload DXLab after IS Reinstall
Evidently "when lost WIN 7 OS and Dell reinstalled lost programs and Apps which have mostly reinstalled" left your system in inconsistent state. The only reliable course of action (short of wiping the C: drive) that I can recommend is to
toggle quoted message
Show quoted text
1. save backup copies your log, Workspaces, and any other critical data files some place safe, if you haven't already 2. direct Windows to uninstall whatever DXLab applications it can 3. use a competent Windows Registry Cleaner application to eliminate all vestiges of each DXLab applications from your system 4. proceed as if you were relocating DXLab to this system for the first time Hopefully, that will be effective. If not, you'll have to save all of your other application data, wipe the C: drive, re-install Windows, and then re-install your applications. 73, Dave, AA6YQ -----Original Message-----
From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 11:31 AM To: dxlab@... Subject: RE: [dxlab] Reload DXLab after IS Reinstall Dave - I tried what you suggested but its not working. Here is what has happened: - Backed up Log all OK. - Think I backed up the Workspace - Directed Launcher to Install all the apps, but although Commander and Keeper say they are installed, when clicking on them to "Terminate", get a msg that says not installed. Tried to Install direct from the C drive program list, but no change. - Terminate does not work on the other programs . . . get a message in read that says it keeps trying but then stops. - When looking at Launcher Config, all programs except Commander and Keeper show correct path names and correct Installed/Available versions - Workspace does not seem to function . .. saved the workspace on this computer, and also did the same from a second machine where DX Lab Suite is fully operational, but cannot seem to save it with the Workspace on the Launcher. Help! - Alan K9MBQ |
|
Re: Can't Edit Commander User-defined Controls
What version of Commander are you running?
toggle quoted message
Show quoted text
When you CTRL-click a user-defined control button, does an entry for the editing window appear in the Windows task bar? 73, Dave, AA6YQ -----Original Message-----
From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 11:57 AM To: dxlab@... Subject: [dxlab] Can't Edit Commander User-defined Controls Neither a CTRL-click nor a right-click on any User-defined Controls button brings up the edit panel/window. Error log shows nothing but the following 29-Feb-2016 16:41:33 > CIVMain.ConfigCmd_Click 29-Feb-2016 16:41:33 > CIVConfig.Form_Paint Other CTRL-click functionality okay, e.g. CTRL-Help or CTRL-n to display or edit memory notes. Have rebooted PC and restarted Commander; have restored Commander from Launcher "Restore" with no success. |
|
Can't Edit Commander User-defined Controls
Neither a CTRL-click nor a right-click on any User-defined Controls button brings up the edit panel/window. Error log shows nothing but the following
29-Feb-2016 16:41:33 > CIVMain.ConfigCmd_Click 29-Feb-2016 16:41:33 > CIVConfig.Form_Paint Other CTRL-click functionality okay, e.g. CTRL-Help or CTRL-n to display or edit memory notes. Have rebooted PC and restarted Commander; have restored Commander from Launcher "Restore" with no success. |
|
Re: Resetting SpotCollector Database Display?
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 9:52 AM To: dxlab@... Subject: [dxlab] Resetting SpotCollector Database Display? I made a bit of a mess installing SpotCollector on my new PC. I removed all the fields from the display that I wasn't interested in an now SC has a blinking scroll bar at the bottom that is quite annoying every time it updates the display. I suspect it is caused by resizing the display in light of the eliminated fields. I think I should have just left them all in place and rearranged them so that the ones I wanted were left most and therefore always in the window. Is there a way of resetting this or should I just remove and reinstall SC? Removing and re-installing SpotCollector would likely have no impact, as it would not alter SpotCollector's settings stored in the Windows Registry. 1. terminate SpotCollectorIf you copied a Workspace from your current PC to your new PC and used that as a source of initial DXLab application settings on your new PC -- but didn't direct the Launcher to save your modified settings to this Workspace, you can 2. open the Launcher's Workspaces window 2a. click on the Workspace's name in the "Workspaces" panel on the left 2b. in the "Selected DXLab Application" panel, set the "Applications Settings to Load" selector to SpotCollector and then click the panel's "Load Settings from Workspace" button 1. terminate SpotCollectorIf you didn't copy a Workspace from your current PC to your new PC, you can clear SpotCollector's settings in the Windows Registry; then when you next start SpotCollector, all settings will be at their initial default values: 2. open the Configuration windows' "DXLab Apps" tab, and depress the CTRL key while clicking SpotCollector's "Ld" button in the Registry panel 73, Dave, AA6YQ |
|
Re: Reload DXLab after IS Reinstall
Dave -? I tried what you suggested but its not working. Here is what has happened: - Backed up Log all OK. - Think I backed up the Workspace - Directed Launcher to Install all the apps, but although Commander and Keeper say they are installed, when clicking on them to "Terminate", get a msg that says not installed. Tried to Install direct from the C drive program list, but no change. - Terminate does not work on the other programs . . . get a message in read that says it keeps trying but then stops. - When looking at Launcher Config, all programs except Commander and Keeper show correct path names and correct Installed/Available versions - Workspace does not seem to function . .. saved the workspace on this computer, and also did the same from a second machine where DX Lab Suite is fully operational, but cannot seem to save it with the Workspace on the Launcher. Help! - Alan K9MBQ |
to navigate to use esc to dismiss