开云体育

I do not know what is happening but I do not have either problem here. I have seen the lost control error but that is only if I turn off the rig before terminating DxKeeper and doing the retry get all

Good morning. I have been using the DXlabs suit for a? while now to control my Icom IC7300. I like it very much. Main use is doing data modes, FT8 PSK31 etc. It has been working well controlling JTDX

NOD32, no fear and you forget it. 73 de Salvatore (I4FYV)

As we can see, the FUD (Fear, Uncertainty and Doubt) regarding Anti Virus / Anti Malware solutions (MS Defender in this case) have reached a new rhetorical level in regards to DXLab applications /

/g/DXLab/message/192460 Worked for me.? Second section. Don WB6BEE

Just restore the file defender checks and save on the reinstall

Bob, you are missing the numerous posts here about recent Windows Defender actions on some DX Lab Suite applications. The minimum you should do is to open Defender, go to History, view quarantined

As of Friday it seems my window defender doesn’t like DXKeeper running on my machine. I have had to reinstall it three times and every time I do the defender pops up and says that the infected

No this isn't normal. Even with the shift in computing resources on the Club Log side, they are still processing the normal workload, it just takes longer. I've uploaded numerous times since the

I've been getting the "the connection with ClubLog terminated before the upload completed" message when trying to upload to Clublog. Is this normal until the Clublog servers get back to normal from

I fixed my problem with Propview accessing data by * Opening Windows Defender Firewall * Click Allow an app or feature through Windows Defender Firewall * Change Settings * Allow another App... *

+ AA6YQ comments below + Recovery instructions are here: https://www.dxlabsuite.com/dxlabwiki/RecoverMissingExecutable 73, Dave, AA6YQ

Jake - tried your excellent suggestion, & re-booted; but it made no improvement,. Thanks for the idea. 73, Gary W1EBM ________________________________ Sent: Friday, April 10, 2020 11:16 PM To:

Michael, Your virus protection software has quarantined Commander. Most likely you use MS Defender. A recent change has made this package identify Commander as containing a virus. Search the

I'm unable to launch Commander. I'm running Icom 756 PRO III, The message from DXLabLauncher is "unable to launch Commander - the file C:\DXLab\Commander\CI-V Commander.exe does not exist" What am I

+ AA6YQ comments below Thanks for your reply Iain. The reason I brought it up is that I think in past years if you had what was thought to be a high risk Q and it was later confirmed by LOTW the H

Thanks for your reply Iain. The reason I brought it up is that I think in past years if you had what was thought to be a high risk Q and it was later confirmed by LOTW the H was changed to an L and

<jperalta4@...> wrote: I don't think so. Why would you think that? A QSO may be high risk for some other reason (e.g. there's some question about the validity of the operatio

Today I worked a station I needed for CQ Marathon. I wasn't 100% sure it was a completed contact because of QRM. I logged the contact and placed an H in the Country Risk block in DXKeeper.

+ AA6YQ comments below + Yes, it is. 73, Dave, AA6YQ > > >