Hi Richard,
Thanks for your report. See my message posted here earlier today (at
11:37, according to my email client):
#########################################################################
Many thanks to all the MSK144 gang who helped to identify a bug in
WSJT-X 2.0.
I believe the bug is now fixed in our development code. We will post a
-rc2 candidate release very soon, probably next week. In the meantime,
it's best to use v1.9.1 for MSK144 QSOs.
BTW: this was a rather ordinary bug, although it was manifested in a
rather unusual way. It has nothing to do with a "computer virus", in
the sense that term is generally used. No harm will come to your computer!
#########################################################################
-- 73, Joe, K1JT
On 9/19/2018 3:58 PM, richard bumgardner wrote:
To: WSJTx Development Group
From: Richard Bumgardner KV8S
Subj: WSJT V2.0 MSK144 Tx Field Issue
This morning several users of WSJT V2.0 MSK144 operating on 50.280
experienced critical failures within the Tx field which rapidly
propagated among all who decoded the corrupted frames. The frame which
was transmitted as "101745 Tx 1482 &" with no callsigns sent and
subsiquent transmissions continued with incremented timestamps.
This failure appears to have started during an attempted QSO between
myself (KV8S) and KC3OL. At some early point in the exchange the frames
became corrupted and the tone quality changed. I stopped my
transmissions and hoped to correct the issue by restarting the WSJT
program. I then noted that other users on the Ping Jockey board were
beginning to experience the same problem of corrupted frames. N5OSK
posted at 101800 the "101745 Tx 1482 &" quickly followed by KB7IJ
(who was also calling KC3OL) posting to KC3OL "stopping Ted... x just
went stupid" These posts were followed KB7IJ and N0AN. It appears that
any station which received the corrupted frames were then immediately
also corrupted and propagated their own corrupted frames. All affected
stations reverted back to V1.9 with no further problems noted. Also
appears that all these stations had installed V2.0 in separate
sub-directoies and had been successfully operating V2.0 for at least one
full day.
Sorry that i have little additional information as computer restart
and time lapse in going back to Ping Jockey precluded recovering further
details.
_______________________________________________
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
