[Dx4win] R: Fw: dx4win crash importing adi file from wsjt

wo2n at att.net wo2n at att.net
Sun Aug 23 10:05:42 EDT 2020


Here’s The fix that work for me
I believe this started after a new update of WSJTX
Sometimes when WSJTX starts it tells you there’s an error ...but it doesn’t tell you what to do.

you will have to make a small edit to the wsjtx_log.adi file in the WSJT-X log files directory. Change the end of header marker from <eh> to <eoh>.
I found the fix on Google
This fixed work for me.

73 de  Bernie/WO2N

> On Aug 23, 2020, at 5:10 AM, Tibor M. Blum - IK2SAI - <tibor.blum at tiscali.it> wrote:
> 
> Dear Ian thank you.
> I have checked the file generated by wsjt and as you stated instead of EOH
> there is just EH.
> If i modify the file all is just running ok.
> I just ask by myself why wsjt doesn't write the adi file as should.
> This problem arised with this latest release.
> Any way dear Ian this problemi is solved!
> Vy 73 de Tibor, IK2SAI
> 
> 
> -----Messaggio originale-----
> Da: dx4win-bounces at mailman.qth.net <dx4win-bounces at mailman.qth.net> Per
> conto di Ian Fugler
> Inviato: domenica 23 agosto 2020 09:51
> A: DX4WIN at mailman.qth.net
> Oggetto: [Dx4win] Fw: dx4win crash importing adi file from wsjt
> 
> 
> 
> Tibor
> 
> Have you checked that the ADIF import file is correct?  I seem to recall
> that there was a bug and the ADIF file was showing 'ER' instead of 'EOR' at
> the end of the record, or 'EH' instead of 'EOH' after the header.  It was
> something like that.
> 
> 73,
> 
> Ian G4iiY
> 
> ________________________________
> From: dx4win-bounces at mailman.qth.net <dx4win-bounces at mailman.qth.net> on
> behalf of Tibor M. Blum - IK2SAI - <tibor.blum at tiscali.it>
> Sent: 23 August 2020 06:18
> To: DX4WIN at mailman.qth.net <DX4WIN at mailman.qth.net>
> Subject: [Dx4win] dx4win crash importing adi file from wsjt
> 
> Hello guys.
> 
> I do have a problem importing from WSJT the log file (adi).
> 
> All the time dx4win crash.
> 
> Up to few days ago (before a clean reistallation of all the system) it was
> working.
> 
> Any idea?
> 
> 
> 
> (Using dx4win 9.09.1259 and the lastest wsjt 2.02.02. Before i was using an
> older version of wsjt on WIN10pro @64 bit)
> 
> Thanks
> 
> Vy 73 de Tibor, IK2SAI
> 
> 
> 
> 
> 
> ______________________________________________________________
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:DX4WIN at 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 at 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 at mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html


More information about the DX4WIN mailing list