Hi Bill,
just to be certain, are you also using the "Flex Radio 6xxx" Hamlib
driver for the "Settings->Radio->Rig" option? I don't know offhand what
the TCP/IP time out is for Hamlib but it is quite normal for it to be 30
seconds or even more, so it may be that WSJT-X is waiting for a
connection to fully close before exiting. Is it possible that this
problem only occurs when trying to restart WSJT-X within a minute or so
of closing it down?
The TS-2000 emulation on a VCP will not suffer this extended delay and
has been much better tested.
73
Bill
G4WJS.
On 16/09/2017 19:00, Bill Barrett wrote:
Hello Ria-
I have seen the orphaned WSJT-X and JT9 processes as well. Not so much
lately since using FT8.
I thought it might have been due to closing with the "X" rather than
File Exit.
Same software/HW set up as you.
Bill W2PKY
On Sat, Sep 16, 2017 at 10:12 AM, Ria Jairam <[email protected]
<mailto:[email protected]>> wrote:
Sometimes I may be using WSJT-X and after I quit and try to reopen
later it would tell me that it's still open. Looking in task
manager it says that WSJT-X is still there as a background
process. This only happens after using WSJT-X for a while.
Is this a bug or am I doing something wrong?
Also sometimes it would lose all CAT just at random. I'm using a
Flex-6700 with the CAT port using TCP instead of a virtual serial
port.
I mention the two together because they seem to happen together
sometimes. Just very odd.
System info:
Windows 10 creator
Flex-6700 running 2.x software (currently 2.0.19)
73
Ria, N2RJ
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
