Log4OM

When I have not entered a new call to the log for 10 or so minutes , when I do add a new call and click add, the program sits idle for about 10 seconds , then not responding appears in title bar and then about 5 seconds later the program responds and the call is entered. Is there a way to fix this ?

nc8x wrote:When I have not entered a new call to the log for 10 or so minutes , when I do add a new call and click add, the program sits idle for about 10 seconds , then not responding appears in title bar and then about 5 seconds later the program responds and the call is entered. Is there a way to fix this ?

We need to know the following information to be able to assist you

What version of Log4om
What computer operating system - Windows XP, 7, 8
What processor
How much RAM
What Radio
What interface cable between the rig and computer
How many QSO's in your logbook

Log4om - 1.18.1.0
win 7
Processor - Intel i5-3570k 3.4ghz
RAM - 8gigs
Radio - IC-7410
USB to serial with the FTDI Chipset
Number of QSO's = 4650

Hi Tim

OK first of all uninstall Log4OM - Download a fresh download and install it - See if the save is faster

If there is no change
Turn of any antivirus software, Malware protection and firewalls that you have running and see if the save is any faster.

If there is no change

1. Export an ADIF file of your log using ADIF 3.00 protocol for the export

2. Create a new logbook - File/New database

3. Import the ADIF exported earlier

Let me know the result to these three changes

nc8x wrote:When I have not entered a new call to the log for 10 or so minutes , when I do add a new call and click add, the program sits idle for about 10 seconds , then not responding appears in title bar and then about 5 seconds later the program responds and the call is entered. Is there a way to fix this ?

So you are typing the call and add the QSO to the log? There are some external services involved when doing that...
If you can reproduce the issue, can you send me your software log file? Please send it directly to iw3hmh (at) pisto.it so i can check what function is slowing down the software and hopefully find the issue.

Log can be obtained from HELP menu.

it seems that the issue was being cause by windows turning off the HDD after a preset time of 15 Minutes. So the lag was caused by the drive needing to get spun up and active again. I just extended the time so windows does not turn off the drive for a longer period of time.
Thanks to all who helped