locked Re: JT Alert 2.13 won't start
Thank you, Laurie. Neither of the programs, wsjt-x nor jt alert, is set to administrator level. Also, I don't see any mention of [2nd Instance] in the box (or 3rd or 4th, etc.). Restarting does allow the program to start normally sometimes. However, this morning I started clean and got the error box and had to re-boot a second time to get up and running. I'll let you know if I discern any pattern in the future.toggle quoted messageShow quoted text
Mark D. Johns, KØJM (ex-KØMDJ)
Minneapolis, MN EN35hd
"Heaven goes by favor; if it went by merit,
you would stay out and your dog would go in."
On Wednesday, March 13, 2019, 2:20:56 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
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!Mark,
There are typically two causes for this behaviour.
1. 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.
2. 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.
Let me know what you discover.
de Laurie VK3AMA