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
