I have recently been contacted by a JTAlert user who experienced a system wide failure of DDE after they enabled the UDP settings within WSJT-X.
After a PC reboot the problems persisted. They disabled the UDP settings with WSJT-X, rebooted, yet the broken DDE remained. They advised the only way to restore DDE functionality was to perform a System Restore. I suggested that a System Restore should not have been needed and that all they needed to do was turn off the WSJT-X UDP. They were adamant that turning off UDP didn't correct the problem (even after a PC restart) and that they had tried 3 different times and each time, the only way to restore DDE Functions was a System Restore. Is there anything in the UDP code that is changing Comms settings at the OS level when UDP is first enabled that are not getting reversed when UDP is turned off? Perhaps it is something within the QT library? Perhaps something within the current Dev branch, since the user is running 1.7.0 (unknown build, I am waiting on a response from the user) Thoughts? de Laurie VK3AMA ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
