Forgot to add: I have two profiles on this installation, both identical save for the callsigns. I seem to recall not having issues with this release until recently when the second op finally had time to get on, and we switched to the second profile then back to mine after she was done. We used two profiles like this with 1.7.0 without any negative effects.
> On Feb 8, 2018, at 8:12 PM, I&N Yanasak <yan.mis...@gmail.com> wrote: > > With the latest GA version of WSJT-X (1.8.0), running Windows 10, I am > running into the problem where the auto-logging and CW ID features are highly > unreliable, at least using standard messages. > > As far as I can tell, the only time that the 73 is detected is > 1) It must be at the end of the TX 5 line, and > 2) That line must not be modified from default (<call> <call> 73) > > All other times, auto-logging, CW ID (and the transmit disable) do not occur. > I can get around the auto-logging and transmit disable by manually selecting > the appropriate buttons, but the lack of CW ID makes sending custom messages > without my call not kosher. > > Any hints? These features used to work (fairly reliably with 1.7.0), and I > have checked that the appropriate settings are selected. > > Thanks es 73, > Ivan AI0IA ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
