Good morning Steve, I too have had this happen and quite frankly I am not sure how to reproduce it because I am not sure how it happened. Once it happens it appears to be locked in to this mode and even a program restart will not clear it. This has happened to several folks and as a consequence there was a wholesale move back to V1.9 among the meteor scatter folks this morning.
I can tell you what happened from my point of view understanding that it may not be that useful (I do a lot of programming) but suspect this issue is one that every little bit of information is going the help find. 1. I installed V2 yesterday morning and made several MSK144 contacts on 50.280 with it on 6m throughout the morning and early afternoon yesterday. 2. As is normal for me I left the program running overnight. 3. This morning I noted a CQ from another station and double clicked on it. WSJTx generated the messages for that station and went to TX1 as expected. 4. I self monitor (I run a Fricking Flex and this is mandatory practice in digital modes) and noticed the tones were higher pitched than normal. This caused me to pay more attention to what the program was doing and I noticed in the "Message" area of the right hand activity window instead of the expected text there was only an &. 5. I stopped and restarted the program. Upon TXing again the same situation occurred. That is the symptom. How to get it into this mode I do not know, it was something that happened overnight while I was not monitoring and unfortunately if it was something unusual it had either scrolled off the window and / or I erased it when I started operating for the day. Also unfortunately due to the locked nature of the issue once it happens as I mentioned earlier the meteor scatter community has moved back to V1.9. I do not know for a fact that it is the & message itself that causes stations to go into this condition although that is a working theory at this point. Also unfortunately I went all in when I loaded V2 RC1 and loaded it over V1.9. I have since reversed this process and likely lost the lock condition. As this is surviving program restarts perhaps it would be useful to ask some of the folks who did not make this mistake to send you there INI files as it may well contain the condition that is causing this. 73 de Bill ND0B -----Original Message----- From: Steven Franke via wsjt-devel <wsjt-devel@lists.sourceforge.net> Sent: Wednesday, September 19, 2018 7:08 AM To: WSJT software development <wsjt-devel@lists.sourceforge.net> Cc: Steven Franke <s.j.fra...@icloud.com>; WSJT Group <wsjtgr...@yahoogroups.com> Subject: Re: [wsjt-devel] Major Virus Like Bug in V2 Hasan, Unfortunately, your report isn’t very useful as it stands. To you and others who are testing the recent beta release of v2.0: when making a bug report, please carefully document and report a sequence of steps needed to reproduce the problem. When running a beta release, always run with “Save all” turned on and, as in this case, if the problem involves behavior that is triggered by receiving a certain type of signal or message, please submit a saved wav file that triggers the problem with your bug report. If you are not willing or able to do the careful documentation that is necessary to help us find and debug problems then, like Hasan, I recommend that you follow his lead: > > Going back to 1.9 on 260, V2 abandoned until fixed. > 73 Steve k9an > On Sep 19, 2018, at 10:52 AM, Hasan al-Basri <hbasri.schie...@gmail.com> > wrote: > > When running MSK144, the program will start tx'ing some weird sounding > tones...they will "infect" any V2 MSK144 station that hears them and they > will start sending the same strange tones. > > 5 of us have experienced this same bug...all simultaneously upon hearing > those "odd" tones. > > I'm betting it is connected to the CM auto-correct code. > > If you TX for a bit with v2 msk144, you WILL infect other listemers/ > > Going back to 1.9 on 260, V2 abandoned until fixed. > > 73, N0AN > Hasan > _______________________________________________ > 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 _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
