Hi Steve,
Thanks for the report. You do know that ""W6XX W7WM RR73 TNX" is not a
legal FT8 message, right?
Nevertheless, the program should not crash when it's given a bad
message. This defect will be fixed in the 2.0 GA release.
-- Joe, K1JT
On 11/27/2018 2:19 PM, Steve Boone W7WM wrote:
Sorry, I didn't report this during RC4 but I accidentally discovered
this unusual behavior with WSJT-X just before RC5 was released. This
also happens in RC5.
While in QSO at transmitting step TX1, TX2 or TX3
I manually change TX4 to "W6xx W7WM RR73 TNX" [1 or 2 extra characters
does not fail)
Click on TX4 (while TX1 is still transmitting)
WSJT-X 2.0 rc5 aborts:
WSJT-X screen disappears, wsjtx.exe task disappears (jt9.exe is still
active-see note below)
transceiver hangs in transmit mode (PTT)
On restart of WSJT-X
Popup:
Killing JT9.exe Process
KilByName return code: 602
OK continues WSJT-X as normal
On initial startup, wsjt.exe has 3 sub-tasks:
wsjtx.exe
jt9.exe
console window host
I have mode = FT8
Windows 10 Pro 1803
_______________________________________________
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
