Think this rings a bell from the past! Look at the first few records of the .ADI file and see if you see "<EOH>" (End Of Header) anywhere. Seems like having no <EOH> caused a problem in the past.
If you DON'T see one, add "<EOH>" (minus the quotes) at the very beginning of the file and try the import again. Please let us know what you find. 73, Lee N7NU >>> Bill Turner via DX4WIN <dx4win@mailman.qth.net> 9/1/2017 10:39 AM >>> I'm using v8.0.5 and have routinely imported .adi files from WSJTX (after adjusting the modes to fit what DX4WIN will accept). Running WIN10 on a Dell D630 Latitude laptop. I had run the most recent update to DX4WIN. In this case, I changed FT8 to FAX so the data length is the same. Bring up my DX4WIN log, import the .adi file and get a new little box on the screen that says Reading wsjtx_9-1-17.adi which is the name of the file I'm trying to import. DX4WIN hangs and when I click on this new little box I get a Not Responding message added to the reading message. Any idea what is going on here? Bill Turner, W4WNT ______________________________________________________________ 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
