Re: [wsjt-devel] Decode lite up - no decode
Hi Joe- I run multiple instances all the time. A problem I have observed is when cancelling all instances, using the windows tray and right clicking on the WSJT-X ICON in the tray and cancelling all instances there is usually several zombie instances of WSJT-X left in the Task Manager. Not a big issues, but thought I would mention it. Thanks & 73; Bill W2PKY On Tue, Jan 29, 2019 at 4:40 PM Joe Taylor wrote: > Hi Tom, > > > Pretty daft to kill processes that may be needed on an assumption. > > It's not daft, at all. Probably 99% of WSJT-X users run only one > instance. In the rare but not unheard-of case where something caused a > program crash, jt9.exe may be left running. When WSJT-X is re-started, > that zombie jt9.exe must be killed. > > Surely it's easy enough for you to start your instances in the proper > order? The ~1% of users running multiple instances have been doing that > for years, with no issues. > > -- Joe, K1JT > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Decode lite up - no decode
Hi All Yes work around is to have all instances use the —rig-name=xxx option Joe - there are times I don’t want to run wsjtx on 6m (the instance with no —rig-name option) - I could be using jt6, FSK411 for MS (a lot of UK contests still don’t support FT8/MSK) which wsjtx does not support - so I just start HF to check conditions —rig-name=HF instance - work away. Finish with MSHV and switch back to wsjtx to use MSK/FT8 - that would kill the HF screen. I have been running all night here with —rig-name=HF and —rig-name=VHF and all is 100% no mater what order I use. I’m pretty sure the software could check for running wsjtx processes (jtalert does it well) and if there are none, other that the one just started, then kill the jt9 exe - if there are existing wsjtx processes don’t kill - that would deal with the rogue process and handle the —rig-name option. 73’s Tom GM8MJV (IO85) On 29 Jan 2019, at 21:40, Joe Taylor wrote: > Hi Tom, > >> Pretty daft to kill processes that may be needed on an assumption. > > It's not daft, at all. Probably 99% of WSJT-X users run only one instance. > In the rare but not unheard-of case where something caused a program crash, > jt9.exe may be left running. When WSJT-X is re-started, that zombie jt9.exe > must be killed. > > Surely it's easy enough for you to start your instances in the proper order? > The ~1% of users running multiple instances have been doing that for years, > with no issues. > > -- Joe, K1JT > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Decode lite up - no decode
Hi Tom, Pretty daft to kill processes that may be needed on an assumption. It's not daft, at all. Probably 99% of WSJT-X users run only one instance. In the rare but not unheard-of case where something caused a program crash, jt9.exe may be left running. When WSJT-X is re-started, that zombie jt9.exe must be killed. Surely it's easy enough for you to start your instances in the proper order? The ~1% of users running multiple instances have been doing that for years, with no issues. -- Joe, K1JT ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Decode lite up - no decode
Thanks Mike So that means you MUST start the single instance first no matter what. That does agree with what I am seeing - nothing in the docs to say there is a ‘start up’ order. As a work around I will try to set all my wsjtx instances to use a —rig-name option and see if that will help keep things running. Pretty daft to kill processes that may be needed on an assumption. -- 73’s Tom GM8MJV (IO85) On 29 Jan 2019, at 17:54, Black Michael via wsjt-devel wrote: > It is coded that way. When you start with --rig-name it knows to expect > multiple instances. Without --rig-name it assumes you're running only one > and kills the jt9 process...but doesn't kill the wsjtx process...which seems > wrong. > > I suppose it's possible to make that check a bit better to allow either > sequence > > de Mike W9MDB > > > > > On Monday, January 28, 2019, 4:36:51 PM CST, Tom Melvin > wrote: > > > > Good day all > > Posted over in general wsjtx list not much joy - Been playing and need some > advice > > One PC, multiple Audio connections to two separate transceivers - wsjtx v2.0.0 > > Start one wsjtx —rig-name=test wsjt starts up and runs fine > > Start another instance but no —rig-name - wsjtx starts up and runs fine but > the original instance has stopped decoding, icon on all the time. > > This only happens if you start the —rig-name=xx instance BEFORE the plain > one. If you start the main instance first, then the —rig-name=xx and don’t > restart or change config both will work 100% ok. As soon as you restart or > change config on the ‘main’ instance the —rig-name instance will lock up. > > Looking at task manager the jt9 process no longer exists on the 1st one. > > Have tried this with main ham setup on windows 7, as a test loaded wsjtx on a > stand alone Windows 10 laptop and same problem. > > Compiled from source, on windows 10 laptop and same problem. > > I can reproduce this 100% on two different PC’s with different versions of > windows. > > Is the a way I can see in a little more details what was happening that would > cause the jt9 process to die? > > > 73’s > > Tom > GM8MJV (IO85) > > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Decode lite up - no decode
It is coded that way. When you start with --rig-name it knows to expect multiple instances. Without --rig-name it assumes you're running only one and kills the jt9 process...but doesn't kill the wsjtx process...which seems wrong. I suppose it's possible to make that check a bit better to allow either sequence de Mike W9MDB On Monday, January 28, 2019, 4:36:51 PM CST, Tom Melvin wrote: Good day all Posted over in general wsjtx list not much joy - Been playing and need some advice One PC, multiple Audio connections to two separate transceivers - wsjtx v2.0.0 Start one wsjtx —rig-name=test wsjt starts up and runs fine Start another instance but no —rig-name - wsjtx starts up and runs fine but the original instance has stopped decoding, icon on all the time. This only happens if you start the —rig-name=xx instance BEFORE the plain one. If you start the main instance first, then the —rig-name=xx and don’t restart or change config both will work 100% ok. As soon as you restart or change config on the ‘main’ instance the —rig-name instance will lock up. Looking at task manager the jt9 process no longer exists on the 1st one. Have tried this with main ham setup on windows 7, as a test loaded wsjtx on a stand alone Windows 10 laptop and same problem. Compiled from source, on windows 10 laptop and same problem. I can reproduce this 100% on two different PC’s with different versions of windows. Is the a way I can see in a little more details what was happening that would cause the jt9 process to die? 73’s TomGM8MJV (IO85) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Decode lite up - no decode
Good day allPosted over in general wsjtx list not much joy - Been playing and need some adviceOne PC, multiple Audio connections to two separate transceivers - wsjtx v2.0.0Start one wsjtx —rig-name=test wsjt starts up and runs fineStart another instance but no —rig-name - wsjtx starts up and runs fine but the original instance has stopped decoding, icon on all the time.This only happens if you start the —rig-name=xx instance BEFORE the plain one. If you start the main instance first, then the —rig-name=xx and don’t restart or change config both will work 100% ok. As soon as you restart or change config on the ‘main’ instance the —rig-name instance will lock up.Looking at task manager the jt9 process no longer exists on the 1st one.Have tried this with main ham setup on windows 7, as a test loaded wsjtx on a stand alone Windows 10 laptop and same problem.Compiled from source, on windows 10 laptop and same problem.I can reproduce this 100% on two different PC’s with different versions of windows.Is the a way I can see in a little more details what was happening that would cause the jt9 process to die?73’sTomGM8MJV (IO85) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
