On 14/03/2019 3:33 am, Mark Johns via
Groups.Io wrote:
When launching JT-Alert 2.13, I get a box that says I must start wsjt-x first -- but wsjt-x is already running!
This happened with version 2.13.0. I just installed version 2.13.1 and get the same thing.
--
Mark D. Johns, KØJM
Mark,
There are typically two causes for this behaviour.
JTAlert is already running and your
trying to start a second instance of JTAlert and that is
waiting for a second copy of WSJT-X to be started. The popup
message will indicate an instance number. You will need to
locate the all ready running JTAlert process and kill it in
Windows TaskManager including any already running JTAlert
plugin processes. The easiest technique that ensures any
JTAlert zombie processes and file locks are removed is to
perform a Windows restart.
WSJT-X is running with elevated process
privileges and Windows is preventing JTAlert from interacting
with the WSJT-X process due to the mismatch in process
privileges. This is typically due to having set WSJT-X to run as
Administrator, either the wsjtx.exe file, the shortcut used to
start wsjtx.exe or both. There is never any need to run WSJT-X
elevated. Stop WSJT-X and remove the run as Administrator
setting.
Since your problem occurred with two
versions of JTAlert, my bet is on number 2 as the cause.
