Funny - there seems to be the fault in DXlablauncher somehow - cannot
imagine why - but it is reproducable.
Is 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.
- 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
