I see the option to have DXKeeper upload each new qso to LoTW. I have that checked but it is not working. At the present time I do it from the ADIF file. It's not a big deal but it would be more conve

Thanks Laurie. I didn't, but I do now! Hi. Works fine. Just getting set up on a new computer and to much to remember at 80 yrs old. Hi John NA6Y

Win 10. FT4. When I use to double click on a call in the Decodes (2.16.14) window it would come up in the WSJT-x window and be sent. I no longer can do that. The only way I can double click a call and

Good morning, Just replaced my laptop and DXKeeper is giving me the message "Unable to confirm QSO logged" I looked at some other postings on this subject but they weren't of any help. Any thoughts on

No Larry, some of the countries have not been confirmed. I have a lot of countries though have not been confirmed but it only seems to be 3 or 4 that keep popping up so I don't think that's the proble

Running JTAlert ver 2.16.10 and WSJT-X 2.12 . I am continually getting the "Wanted Country" alert when I already worked the country, in some cases more than once. It doesn't alert on all countries, on

Tnx Mike. I went in and deleted what was there and opened JTAlert, no problem. Whether that helped or not remains to be seen since it didn't happen all the time. Anyway I really appreciate it. 73's an

Mike, I see 3 "decodes. sqlite" .bak, .shm and .wal, should I delete all 3? John NA6Y

Herb, How do I get to that address?

I am running JTAlert 2.16.10. When I bring up the JTAlert app at least half the time the decodes window does not populate. If I close the app and then immediately bring it up again the decodes window

FYI. My problem was solved by re-downloading the Virtual Comport Driver from Silicone Labs, cp210x_Universal Windows Driver. I read that another had had this problem after MS did an update. I have had

I downloaded the latest version of JTAlert (2.16.7) this morning and found that I know longer have my Audio CODEC. The only choice I have is the Realtex Audio. I tried going back to the previous verso

I am running WIn 10. This morning I tried DL'ding the latest version of JTAlert, 2.16.5. My virus software, McAfee gives me a "JTI suspect 262201" error and will not let me DL it. In the past I have a

Thanks Dave, that did it. Appreciate your help. I owe you a beer. HI 73"s John NA6Y

I have been using JTAlert and DXKeeper for quite time. I usually run FT4 using WSJT. There have been a number of times that during a session I get an answer to a CQ from stations that I may have worke

Dave, It appears that the problem is solved. I had an old revision, updated it, and there is was. Wanted to thank you and all the folks that responded to my posting, really appreciate it. I often wond

For manually logged it shows FT8 with no FT4 option. John NA6Y

Good morning, I am running JTAlert 2.16.1 with WSJT-X 2.1.2 and the mode is FT4. Here's my problem: If I auto-save to DXKeeper then the log shows the mode as FT4. If I manually save to DXKeeper, which

Thanks for the assistance Mike, I really appreciated it. In the process now of finding out from Yaesu what I need to do to return it. Great info on the grounding also. 73's, John NA6Y

The rig is a FT-991A with a SignaLink USB. The OS is Win10. Been running the digital modes for a few years now. When I open JTAlert and WSJT-x I now get the message "Rig failure Hamlib error: I.O. err