Log4OM

w9nz

While using ver 2.11.0.0 in contest mode, I would occasionally get a dire looking message "Unhandled Exception". This always occurred in conjunction with a double click on a cluster call sign. I then had the choice of exiting the program or ignoring the error. I always picked ignore the er...

w9nz

It has been reported numerous times that the contest mode is sluggish. In particular, a double click on a cluster response often does nothing or it takes a rather long time for the call to propagate to the contest window. I've noticed that often, the call will propagate to the contest call box quick...

w9nz

I'm using ver 2.11.0.0 in the contest mode. I noticed that during a recent contest, when I doubled clicked a call sign, my rig changed frequency as expected however, sometimes, the mode also changed. This doesn't happen all the time, maybe 20%. For example I'm working 160m SSB in LSB. Double click a...

w9nz

I'm using Log4om v2.11.0.0 I'm an occasional contester and want to use Log4om for contests and don't want to move to a specialized contest logging program. In a contest, one wants to avoid wasted time and the mental effort to perform task. The bottom line is that you want to be able to "move&qu...

w9nz

I very much agree that there is an issue and in my case I would say it goes beyond sluggish and I would characterize it as "hanging up" if there is a heavy cluster load. See my post in the ERROR section of the forum "Log4OMv2 Hangs with increased cluster load". Although Log4om is...

w9nz

I was using Log4om v2 for the recent ARRL Sweepstakes SSB contest. I noticed that with a relatively heavy cluster load the the program would "hang up" if you would double click on a spot. Instead of quickly changing the transceiver frequency to the spot frequency and entering the call sign...

w9nz

During contests, when spots are arriving very quickl,y it would be nice to be able to stop the appearance of new spots and then resume fresh spots when desired. I tried the "STOP CLUSTER" icon that is on the top line along with frequencies and immediately to the right of the Elevation. Whe...

w9nz

Please, please bring back the Cluster Scanner that was in version 1. It would be nice if the calls would be color coded for not worked, worked before etc. The band map, although it seems like a good idea is was too cluttered and not very useable.

Thanks,
Ray Mikula
W9NZ

w9nz

Within JTAlert, my file path to the Log4om SQLite file pointed to a file location off in the Cloud (OneDrive). I would like to have it point to an SQLite file residing on my own computer. No matter what I do the file path won't change. I've turned OneDrive off and uninstalled and reinstalled JTAlert...

w9nz

I have Log40m set for cluster to follow band changes. This works fine until I'm using split mode on my Icom 7300. When using split, Log4om cluster does not follow band changes. Seems like the band (for the cluster) is being derived from the 7300 Tx frequency, which isn't changing when the band is ch...

Search found 28 matches

Unhandled exceptions (error)

Contest mode sluggishness

Mode change LSB to USB with cluster Call selection

Declutter and Streamline Contest Log

Re: Ver 2.10.0 sluggish?

Log4om v2 Hangs with increased cluster load

Stop Cluster Question/Issue

Re: Cluster Scanner

Can't change JTAlert file path to Log4om SQLite File

Cluster not following rig band change in split mode