Well, Rich, I recall the good old days, when DDE was the President. 73 Steve WA2DFP Sent via the Samsung Galaxy Note® II, an AT&T 4G LTE smartphone

Unfortunately, it has to do with DDE which is an outdated technology that still works (if you use it right) but is no longer supported by the folks in Washington. 73, Rich - W3ZJ Stephen Rabinowitz

You were right on the money. My DXLab Launcher was running as administrator and WSJT-X was not. Once all programs were running at a humbler status the communications began to to flow. Seems like the

Parker, the errorlog.txt file you sent me does not show any instance where you 1. enabled Commander's "log debugging info" option 2. performed an action in JT65-HF that cause JT65-HF do direct

-----Original Message----- Sent: Monday, January 20, 2014 12:09 PM To: dxlab@... Subject: Re: R: [dxlab] Card Aging Report Question Hi Dave, So if I understand your response, the

-----Original Message----- Sent: Monday, January 20, 2014 2:55 PM To: dxlab@... Subject: Re: [dxlab] RE: Commander PTT Sluggish with JT65-HF The connection to other members of the DXLab

The connection to other members of the DXLab Suite is handled by JT-Alert. No application - either DXLab Suite or JT-Alert may be run with elevated privileges ("run as administrator"). DDE

OK. Please do the following: 1. on the General tab of DXKeeper's Configuration window, check the "log debugging info" box 2. the next time you log a QSO but the relevant Spot Database Entry is not

Not having its power supply enabled could also cause a CI-V interface to receive but not send signals. 73, Dave, AA6YQ

Hi Larry, Sorry, I misunderstood. I thought, erroneously,that the issue was referred to “Add NEEDED” Cards in the pane “QSL”. In “Card Aging”report of the pane “Check Progress”

Joe, I am using WSJT-X v1.1, r3496 with JTAlert-X 2.4.13 and the DXLab Suite. The TCP connection to Commander works well, but the connection to the other members of the suite, which I think is

Hi Dave, So if I understand your response, the information I provided in my email is just summery info for all the cards on the report. For example I have 16 cards for DXCC entities that have not been

DAVE: >>>If you have Commander running, then the "Xcvr Freq" panel in the upper-right corner of WinWarbler's Main window should match the frequency displayed in the VFO panel of DXKeeper's Main

Dave.....I think you’re right. I’ve been using a K1NU CI-Vinterface for years, but didn’t replace it after the lightning strike because Ithought it was still good because both DXLab Commander

Tnx Dave - its been thru several reboots in the past few weeks. 73 Art

Carlo, The "Need" column should be the last column to the right on your card aging report you don't need to add it. On mine before I added the QSL_sent_via column, the Expired and Need headings were

I do not see the “Need”column at the right-most of the screen. What I missed? Where tocommand to have such a column as well? Thanks Carlo IK2RPE Da: dxlab@...[mailto:dxlab@...] Per

...via the Databases tab of DXView's Configuration window. 73, Dave, AA6YQ

...via the Databases tab of DXView's Configuration window. Joe W4TV has included the following updates in this version: * update the prefixes and callsigns recognized as being in the Shetland