Affecting ADIF and MIXW users only. The Log Scan for CQ Zones is broken and returns all zones needed on all bands. There will be a new JT-Alert release in a day or two with

>>>AA6YQ comments below

Dave - I looked on the DXLab's Databases tab of DXView's Configuration window,then I clicked on the "NEW ?" button and nothing changed on the screen- there were no highlighted DXCC Database Update

Brad - Please help the rest of us understand what is/was going on with yourlog, You say that someone emailed you earlier today and explained how itworks - Please do a copy/paste of their explanation

-----Original Message----- From: Ham-Apps@... [mailto:Ham-Apps@...]On Behalf Of Laurie, VK3AMA Sent: Thursday, November 08, 2012 3:46 PM To:

Hi Laurie, I understand now what was going on. Someone emailed me earlier today and explained how it works. Everything is ok. Thanks and sorry for the trouble. 73 de Brad KD5ZAT

Brad, Comments inline... de Laurie, VK3AMA That is correct, simply hlogging a QSo doesn't update your needed lists. Many operators consider a State, DXCC, etc as

Jess, If JT-Alert is logging to DXKeeper, then it is the DXKeeper Log that gets used for B4 checking. The inbuilt B4 log is only used if you have logging disabled, that is not

Costas, JT-Alert will handle all adif files from different loggers. Please use the "Settings -> Contact Support" menu to send me your config & session files for analysis.

Well, I don't usually use hot keys, but it just caught my attention as I was doing the initial set up of v 2.0. If that's the only thing you missed, we're in GREAT shape!!! 73, Phil/VE1BVD -- Phil &

Den, See my previous message in this group for an explanation as to the cause. A combination of JT-Alert not accurately reporting an invalid dxcc logging attempt and a DXKeeper

Laurie, I didn't realize this was topic was CC'd over on JT65-HF and replied over there, then it bounced trying to add it here. ( I've now updated my membership info ) This is what I wrote over

Hi Phil, I looked at the page when you first reported the issue, and I totally missed it ;) That 3rd hotkey (bottom one) should read "Halt JT65-HF TX On/Off"

Terry, I had a look at your Session Log. The actual error is due to an invalid DXCC code. The Log lookup of PJ2MI returned a DXCC code of 85, which is for the old

Laurie, for what it's worth, I had a similar experience a couple of days ago, before I changed to version 2. It only happened once, and everything has been fine since. 73, Phil/VE1BVD -- Phil & Anne

Hi Laurie... As requested in your last message, here's the screen shot showing two hot keys assigned to the same function: -- Phil & Anne Irons Sydney, Nova Scotia

DJ, Did you get my email (yesterday) in response to your support email? I believe this error is thrown as the result of your WiFi router returning an html page with a "Stale DNS

Does "HRD" appear in the title-bar of JT-Alert or "No Log"? If "No Log" then you need to enable HRD logging by checking the enable option, top-left of the HRD V5 section of the JT-Alert