From: Bill S. <g4...@cl...> - 2020-07-13 21:09:54
|
Hi Tripp, if there is a wsjtx process running after a reboot then something must be starting it, WSJT-X will not start spontaneously. 73 Bill G4WJS. On 13/07/2020 22:04, Tripp Sanders wrote: > I have an icom 718 being controlled directly through wsjt x. it’s been > running for at least 3+ hours after closing the wsjt x And survived 2 > reboots. > > On Mon, Jul 13, 2020 at 3:51 PM Bill Somerville <g4...@cl... > <mailto:g4...@cl...>> wrote: > > On 13/07/2020 21:42, Tripp Sanders wrote: >> I have been having problems with wsjt x having a stale lock file >> error after closing the program normally restarting my pc fixes >> it but it happened and restarting didn’t work. I looked on some >> stuff online and i tried deleting the lock file but even with >> admin privileges it did not work I then checked using process >> explorer if wsjt x was running and it was I tried to kill it but >> I couldn’t. I then uninstalled and reinstalled wsjt x but it >> still happened. Wsjt x version is 2.2.2 windows version 2004. >> -- >> 73, >> K5TRP >> Tripp Sanders > > Hi Tripp, > > how do you close WSJT-X? Do you have a CAT controlled rig, if yes > how is it connected for CAT control? > > When you find the wsjtx process remains running after you close > WSJT-X, how long have you tried waiting for it to terminate normally? > > 73 > Bill > G4WJS. > |