Hi Bob, comments in line below. On 13/06/2016 19:16, Bob KD7YZ wrote: > 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. The above procedure works fine for me, I do not believe it caused the issue with the azel.dat file. Did you substitute the correct location for your WSJT CALL3.TXT file? > > 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
No folders where being linked, if you used a different mklink command option to link folders (/D or /J) then that could well mess things up. All that is needed is a single file hard link to share the CALL3.TXT file in the two locations used by WSJT and WSJT-X. This is not rocket science and it is exactly what hard links are designed for. 73 Bill G4WJS. ------------------------------------------------------------------------------ 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
