I also delete the wsjt_log.adi file each time after I import it.
Otherwise it will keep appending QSOs, and you will be making D4W
process the same QSOs over and over again each time you import. Not a
problem I guess if you select 'imported QSO is ignored' but it doesn't
seem very efficient. :) (And it'll always be in the recycle bin if I
need it)
73 Len K1NU
On 2018-07-24 17:38, Carol Richards wrote:
Hello all,
Thanks for all of the responses. For some reason, DX4WIN didn't like
my WSJT_X adi file because it kept hanging with the message, " Reading
WSJT_log.adi (not responding)". I worked around the problem by
importing the file to N1MM and then to DX4WIN. Not the most ideal way,
but I will have to look into the problem a bit more closely. I have
never had this problem before...strange.
Carol
______________________________________________________________
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
Message delivered to [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]
Message delivered to [email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
