On 13-Jun-16 1247, Bill Somerville wrote: > On 13/06/2016 17:42, Greg Beam wrote: >> I'm still confused on how the the CALL3 link is causing azel.dat >> failure. > > Hi Greg, > > it's not. The azel.dat issue is unrelated.
not to worry. the problem started when I did the suggested ;rename %localappdata%\WSJT-X\CALL3.TXT CALL3.TXT.SAVED ;mklink /H %localappdata%\WSJT-X\CALL3.TXT C:\WSJT\WSJT10\CALL3.TXT ; from then on, whenever I ran WSJT10, I got the fatal-error about azel. Now all I did was completely uninstall wsjt10, get a download and re-install. WSJT10 works again. The original issue of too many CALL3 locales however remains. I won't be linking any folders for the time being, hi -- 73, Bob KD7YZ www.qrz.com/db/kd7yz AmSat LM#901 ------------------------------------------------------------------------------ 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
