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 <t...@tkrh.co.uk>
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
