I have also found that AK and HI calls do not create the lock-up, only those with a 291 DXCC code (Continental US).

Another ham is trying to help me and he thinks it is a corrupt record in the HRD log file. 

Thanks for the thought Morris

de Danny, W0JMP

Danny,

A corrupt HRD log may be the issue. There was an unrelated but similar problem recently where JTAlert would slow right down whenever it went off to examine the HRD log file, which happens when a station is first decoded and JTAlert goes off to check on its B4 status. Later decodes of the same station(s) were not affected since subsequent B4 checks used a cached status avoiding repeated log lookups.

Ultimately this problem was resolved by performing an ADIF export of the affected HRD log, creating a new empty log and performing an ADIF import and then switching JTAlert to use that new log. Worth a try, you have nothing to loose.

de Laurie VK3AMA

I tried that. I turned off all alerts except for my own call. No help.

I have also found that AK and HI calls do not create the lock-up, only those with a 291 DXCC code (Continental US).

Another ham is trying to help me and he thinks it is a corrupt record in the HRD log file. 

Thanks for the thought Morris

de Danny, W0JMP

I am having intermitente log posting to HRD Loging.
Is there a trace facility in JTAlert?

John
TI4JWC 

I have heard it too, but with my bad hearing could never make out just what it was saying.
Have tried to figure where it was coming from and have yet to find it.

John W3ML

How about turning off Alerts you have set for states such as WAS (new states) grids anything that would trigger a Alert maybe turn them off one at a time. 73 Morris WA4MIT

Hi Jim,

Mine works for states for sure and used to work for zones :)

I think it still does but have some Log4OM issues

It does not work here for zones or states, only for DX.  I manually do states and zones. Maybe I have it set wrong.
--
Jim Sherwood, N4UOZ

Running HRD 6.7.275, JT 2.1.0, JTALERT 2.16.4
Intermittently after entering OK to Log I do not receive the confirmation message and there is no log entry in the HRD Logbook.
I examine the WSJT-X log file and the QSO is there.  Ware  should I look for the source of my problem? 
John
TI4JWC

I am going to work with the guys at Log4OM at this point.

Appears that Log4OM has 99% of my contacts in the US listed as Zone 5. 

99% of the Zone 4 contacts are VEs.

After sorting in Excel I only ended up with 50 LOTW confirmed zone 4 contacts and none of them on 15 meters.

So not a JTAlert issue.

Carry on :)

73,

Rich
kd0zv

Why is that Jim?  Scan should work as it does for everything else

scan well not pick it up. You have to manually uncheck it.
--
Jim Sherwood, N4UOZ

As I said when I switch to ADIF logging its fine. But when I use LOG4OM logging it is missing zones.

And yes, its checked

As a test  I downloaded an ADIF file from QRZ.com and the CQ zones seem fine when I changed logging in JTAlert to ADIF logging instead of Log4OM.

I tried an ADIF from Log4OM and CQ zones are incomplete again.

I have hundreds of LOTW confirmed digital contacts on 15 meters.

Below is my LOTW digital WAS.

So for some reason my missing zones seem to be related to my Log4OM source.

Was hoping someone would know why this is doing this. I restarted the program and wsjt-x and it doesn't Ingore all Worked BT before the date I set which is today.

Very weird. I feel its going to effect my outcome of the contest so Im not going to be able to Search and Pounce as much as i would like cause I can't tell if I've worked the person before in this contest or in the past ya know.

Trying to figure out why I keeping getting alerted that I have a needed CQ zone.

It shows I need zone 4 on 15 meters when I do not. I have LOTW digital confirmation on 15 meters for all states so that should cover zone several times over.

What am I missing?

Running Log4OM so scanning that database. Just did a scan log and rebuild and no change.

Rich
kd0zv

I have net yet found a HI or AK station to test to see if they also lock up JT-Alert. But I did try simply putting a US call into the "DX Call" box in WSJT-X. I only typed the call in and did not activate anything else. That action by itself caused JT Alert to lock up.
I keep trying things but have still not found a solution.

 

Thanks again for your support Laurie.

de Danny, W0JMP

I also want to thank Laurie for providing this highly valuable software.
I would not want to operate without it.
The B4 information is invaluable as are the alerts for new DX.

Since I have WAS, my issue with USA stations is a nuisance but not a big problem.
I do want to help others achieve their WAS goals so I still try to work USA stations when DX is not active.