GM Joe Summation of Yesterdays info: 1 .Mike K1IU is experiencing crashes with the 2.6.0 rc files. He uses LOG4OM2 in conjunction with WSJT. 2. Tony ZL3HAM is experiencing crashes with the 2.6.0 rc files. He uses DXLab Suite and JTAlert with WSJT. 3. Dennis W1UE and Ty K3MM are both experiencing crashes with the 2.60 rc files. They use N1MM+.
I have yet to see any reports that 2.5.4 has caused crashes. When I used it, I did not experience crashes. When 2.6.0 RC4 came out, it took 20+ hours of operating before I had a crash. Once it crashed, the next crash didn't take anywhere near as long. Still, there is no time frame for crashes; it may crash 5 times in an hour, then not crash for 4 hours. I'm retired and have plenty of time to test out any revised files. Tracking down a fix for a crash that happens sporadically can be quite time consuming; if any member of the development team needs an extended period of operating time to test out changes, please don't hesitate to get in touch with me. Dennis W1UE On Mon, Oct 24, 2022 at 1:53 PM Joe Taylor via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi Dennis, > > Thanks for your helpful report. I guess it's not yet perfectly clear > whether using the hamlib4.dll from v2.5.4 helped, or whether you were > just lucky for the last 7 hours of the contest. > > In any event, it seems that there must be some kind of negotiation issue > between N1MM+ and WSJT-X. Somehow we need to isolate this problem and > see what can be done to make the negotiation more forgiving of delays, > or whatever, and not simply shut down the channel. > > -- Joe, K1JT > > On 10/24/2022 8:54 AM, Dennis W1UE via wsjt-devel wrote: > > I started the contest using 2.6.0RC4. I operate with WSJT in > > conjunction with N1MM+, using the DX Lab Suite Commander to a K30/Mini, > > through a Remote Rig > > unit to the remote transmitting site. I used SO1V mode for this > > contest- no SO2R. The combination worked perfectly for about 6 hours, > > then the WSJT-X for EW1 just "disappeared" with the TCP error from > > N1MM+. I opened Task Manager, killed the orphan JT process, and was > > back on the air- for maybe 15 minutes, when it happened again. This > > time I Restarted the computer, started up again, and within 30 minutes > > it happened again. > > > > Remembering a conversation i had with Joe K1jt a while ago, I then > > substituted the 2.5.4 hamlib4.dll for the 2.6.0 dll, restarted the > > computer, and started operating again. It lasted about 30 minutes, and > > the same error again. I deleted the orphan JT9 process and started up > > again. That was the end of the errors- it never happened again for the > > next 7 hours of operation. > > > > In his write-up on 3830, Ty, K3MM, also tried 2.6.0rc4 to start the > > contest. Within an hour of the start, he had his WSJT-X EW2 window just > > disappear. Rather than fight it, he went back to 2.5.4 and had no more > > "disappearances" the rest of the contest (about 27 hours). > > > > I typically use 100w or less in contests, but did use 800-1000w for this > > contest. I saw no difference in "disappearances" between the two power > > categories. > > > > Thanks to all for their work in supporting WSJT-X. Its truly a great > > program! > > > > Dennis w1UE > > > > > > > > > > > > _______________________________________________ > > 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
