Hi Mark, Assuming your .DXL log file is WA0MHJ.DXL, see if you have a WA0MHJ.~DXL file. If so, copy it to a unique name. This .~DXL file is a recent copy of WA0MHJ.DXL.
What version of DX4WIN is this happening with? If you create a "new" (different name) DX4WIN log file, can you import the WSJT-X file? Do you have another PC with the same version of DX4WIN on it? If so, move your logfile.DXL (save a copy of logfile.dxl first if it already exists on that PC) and WSJT-X file to that PC and try the import again. Do you have OTHER WSJT-X ADIF files you could import? If so: 1) Copy your logfile.DXL file to a new unique name (debug.dxl) 2) Go into DX4WIN 3) Open the debug.dxl file (or whatever you named it in step 1 above) 4) Try importing a different WSJT-X file (not the one that you used before) 5) Did the import work? If yes, try importing the WSJT-X file that didn't work earlier. Did it work? Let us know how it went and we can go from there :) 73, Lee N7NU On Tue, Jun 30, 2020 at 6:33 AM Mark Endorf <mend...@centurylink.net> wrote: > Last night a Windows update occurred. (DX4WIN was active) > Today I seem to be able to add QSO's and save them, but any attempt to > import my ADIF log from my WSJT-X contacts causes DX4WIN to lock up. > Spinning wheel with no import happening. > Any ideas? > 73 > Mark - WA0MHJ > > > ______________________________________________________________ > DX4WIN mailing list > Home: http://mailman.qth.net/mailman/listinfo/dx4win > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:DX4WIN@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > ______________________________________________________________ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html