[cross-posted on the threads for both problems]
I’ve developed a work-around for the two problems I was having with ExpertSDR2.
To recap, my issues were:
- When I open an RX2 or BP window on a second monitor, ESDR2 hangs the next time I try to use it.
- My E-Coder interferes with Windows power management and prevents displays from sleeping.
To work around these problems, I created the following command file and now use it to start ESDR2. It disables the E-Coder Windows device when ESDR2 is not running and it always restores ESDR2 settings from a known good copy.
:: This command file starts the ExpertSDR2 program, after first:
:: - restoring the ExpertSDR2 settings to a known good state, and`
:: - enabling the E-coder device.
:: The command file disables the E-coder device before exiting to
:: prevent the E-coder from messing with Windows power management.
set EXE_DIR=C:\Program Files\ExpertElectronics\ExpertSDR2 SunSDR2DX
set USER_DIR=C:\Users\<your-user-name>\AppData\Local\Expert Electronics
:: Use Plug and Play Utility to enable the E-coder device.
pnputil /enable-device "%DEVICE_ID%"
:: Restore the ExpertSDR2 directory from the lifeboat copy.
robocopy "%USER_DIR%\ExpertSDR2 - lifeboat" "%USER_DIR%\ExpertSDR2" /MIR /XD voice /XD wave
if %ERRORLEVEL% GTR 1 GOTO END
:: Launch the ExpertSDR2 application.
"%EXE_DIR%\ExpertSDR2.exe" || GOTO END
:: Use Plug and Play Utility to disable the E-coder device again.
pnputil /disable-device "%DEVICE_ID%"
However, this does mean If I make changes to ESDR2 settings that I want to keep, I have to refresh the saved copy of the ExpertSDR2 directory.