Hi Laurie, I am using DXKeeper for logging. My delay before checking is set to 8 seconds which is perfectly adequate 99% or more of the time, but occasionally when my machine is

Hi Laurie, Thank you for your answer. Yes, I understand your point of view. However, allow me to suggest another solution that could meet both aspects: At the "B" versions of my wsjt-x clones I placed

Not had an issue with this version or any others with any of the AV software I have used in the past. Charlie G4EST www.g4est.me.uk

The problem was solved by increasing the priority of marathon. It is apparent that verbal alerts enjoy different priority then visual alerts. Amos 4X4MF ============ I am using the CQ Marathon

QRZ.com has you in OR, that is where the info came from probably, change it at QRZ.com. John VE3KKQ

The JTAlert Call database shows that I operate from MN but the thing is I have never had an address in that state. I don´t know why I have been associated with that state in the call database. There

I did have a problem "downloading" it. I am using Windows Defender. I went into Windows settings under Update and Security. Windows Security, Virus & Threat Protection then Protection History where it

Yep .. I've never had a problem with AVG Internet Security. Neil, KN3ILZ

Thanks Laurie. I did not know about the priorities. I assumed a Wanted Callsign would always be the highest priority. I don't know why anyone would not want it this way. Presumably, you added

...and Log4OM also has the correct zones in its Main UI window, however something goes wrong upon the logging of the QSO. It happens over and over again. Guess we need more chatter on the Log4OM

Dave, That isn't true. Log4OM does receive the correct zones from JTAlert, unless JTAlert doesn't have a zone to send (very rare). The problem is what Log4OM does with the info. As I

That's what I was trying to say. Log4om is not receiving any correct info on itu and cq zones from j talert. sent by my LG phone

Jim, This is not a defect, but expected behavior when a Wanted Callsign is generating other Alerts. A Wanted Callsign alert is, by default, lower in priority than all

Hi Bill, Your correct, the internal B4 cache (held in memory) does not get updated if JTAlert is unable to confirm a QSO was logged. What Logger are you using that is

Sorry, separate configurations per JTAlert instance is not possible with the V2 series of JTAlert, it would require a significant code rewrite which will not happen. The V2 code is near

No, that wont be possible. It was the menus in the titlebar and the mouse position/click detection management that were the problem. The code for placing the menus (and the Band

Richard, Tnx for the report. I can confirm this is a defect. It has been corrected for the next release. Sorry for the inconvenience. de Laurie VK3AMA

It is not a JTAlert problem. If JTAlert shows zones in the log fields area, that is what gets sent in the ADIF packet to Log4OM. If a zone is unknown than there will be no zone data in the adif

Thanks Herb. I was not officially back. I was in transit from my non-Internet QTH, spending some time at a family members house and wanted to check the unread messages and couldn't resist reply to

Yes. Using Norton 360. I did get the message from Norton saying this is new, and not may users (or words to that effect), but all I had to do was click "Trust" and no problem. This is a