It's a known problem, scheduled to fixed in the next WJST release. Best Regardses, Eric (W1EL)
-----Original Message----- From: [email protected] <[email protected]> On Behalf Of Mark Endorf Sent: Tuesday, June 30, 2020 15:15 To: 'Lee Hallin' <[email protected]> Cc: [email protected] Subject: Re: [Dx4win] DX4WIN locks up on file import I have recently updated to WSJT-X release candidate 2.2.2. Upon launching WSJT-X, I now get a pop up window indicating “Error scanning ADIF log”. “Invalid ADIF header.” I took my existing file called wsjt_log.adi (the one I am trying to import), and renamed it to temp.adi. I then made a few new contacts in FT-8 mode. I was going to try to import the new contacts, but when I re-launch WSJT-X, I get the same error message. I was beginning to think, the problem is with the new version of WSJT-X. Both ADIF files initially looked proper to me, but I see that the header is labeled “WSJT ADIF Export <eh>”. I renamed <eh> to <eoh>, and now everything is working properly. Isn’t <eoh> the proper end-of-header for all ADIF versions? I am running the latest release with all updates installed on a Windows 7 platform. Perhaps if any of you are part of the WSJT user groups, this issue can be presented there. Mark WA0MHJ From: Lee Hallin [mailto:[email protected]] Sent: Tuesday, June 30, 2020 12:08 PM To: Mark Endorf; Hallin, Lee Cc: [email protected] Subject: Re: [Dx4win] DX4WIN locks up on file import 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 <[email protected]> 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:[email protected] 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:[email protected] 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:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
