![jt65-hf-hb9hqx-edition jt65-hf-hb9hqx-edition](https://i.ytimg.com/vi/hEJcDInunvA/mqdefault.jpg)
So it seems I did not really understand what the adif import logic really was. I tried the VOX mode but I dont see any way to switch to data VOX, so Im going to try WSJT right now and see if it goes any better. It did not do anything to the other entries already there. Thanks, I am using the 'JT65-HF-HB9HQX-Edition' version 0.9.90.0. The only thing that happened was that the last new QSO was added, just as I wanted. I thought I made a big mistake because I was worried that it would overwrite all the logged JT65 QSOs I had imported into Log4OM before and all the additional info that I added to each JT65 QSO after importing into Log4OM would be lost (such as QSO sent status, LoTW status and so on). Important: Close and restart the program every 12 hours.
![jt65-hf-hb9hqx-edition jt65-hf-hb9hqx-edition](https://www.iv3pgq.it/wp-content/uploads/2014/05/eqsl-show.jpg)
Yesterday I made a mistake and imported the entire backup adif file from the JT65 program. Hello dear friends of JT65-HF HB9HQX-Edition This is a support group for this program, a fork of established JT65-HF from W6CQZ. I do both, except I only use the the last logged QSO adif file to import into Log4OM every few days.
#Jt65 hf hb9hqx edition software
Using the JT65 software I've been running (JT65-HF HB9HQX Edition), it can either export only the last logged QSOs or the entire log for a backup. HF-PACKET and UHF-PACKET (AX25) are supported in KISS-TNC emulation mode.