Ria

I think Tim said that WSJT-X has the problem much more frequently than other 
programs, but I think he suggested that other programs have it too.  Given the 
popularity of JT, it could be observation bias.

DF


________________________________
From: Ria Jairam <[email protected]>
Sent: Wednesday, October 11, 2017 7:01:44 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Stale Lock

WSJT-X hanging on exit definitely isn’t a SmartSDR problem. Any software should 
timeout a TCP connection it can’t close instead of staying hung.

However this may be peculiar to Hamlib rather than WSJT-X. We are not the only 
flex users having this issue and literally nothing else connected to the radio 
has this problem.

Anyway either myself, Phil and others would be more than happy to help debug 
any issues with flex radios connecting to WSJT-X or any software for that 
matter.

73
Ria, N2RJ

On Wed, Oct 11, 2017 at 5:06 PM Dave 
<[email protected]<mailto:[email protected]>> wrote:
Sounds more like a problem with SmartSDR than WSJT-X.  Maybe we should raise 
the issue with Flex.

BTW.  I said I killed the jte.exe entries.  I should have said wsjtx.exe as I 
just scroll down to the bottom of the lists and find up to four instances 
listed depending how many slices I'm running when it freezes.

73 Dave W3DLQ


------------------------------------------------------------------------------
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]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
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

Reply via email to