Lockup of screen

[w9nwrwi]

New user and am considering Log4OM as my main log, looks very nice.
I have had some success with integrating to other programs but am still testing all functions.

One major problem I am having is that for no reason Log4OM will totally lock up. It starts with all my logged qso's disappearing,
the hard drive starts churning, bottom of screen to the right of "Detach Grid" in red it says "Busy." Hard drive eventually stops (30 minutes or so of run ) but program is still locked.

The only thing I can do is end program via Windows 7 task manager. Upon closing Log4OM via task manager and then attempting to reopen I get the "program is already running" notification.

Any assistance appreciated.
73
Chuck w9nwr

[VA3AG]

New user and am considering Log4OM as my main log, looks very nice.
I have had some success with integrating to other programs but am still testing all functions.

One major problem I am having is that for no reason Log4OM will totally lock up. It starts with all my logged qso's disappearing,
the hard drive starts churning, bottom of screen to the right of "Detach Grid" in red it says "Busy." Hard drive eventually stops (30 minutes or so of run ) but program is still locked.

The only thing I can do is end program via Windows 7 task manager. Upon closing Log4OM via task manager and then attempting to reopen I get the "program is already running" notification.

Any assistance appreciated.
73
Chuck w9nwr

Are you running the program as a administrator? If not try that please.
73

[w9nwrwi]

Thanks for the response,

Will try that.
73
Chuck

[IW3HMH]

Running as admin could help for other functions, but this is not related with privileges.
Can you try downloading the portable version and try it from an usb key? Just unpack and start, please create the new database in the same usb key.
I suspect something on your system like defrag needs or some kind of incoming trouble with the hard disk (but this should apply to some other strange behaviors with other applications)
Please let me know

[w9nwrwi]

The program has been reasonably stable for the last few hours, only had one lockup but that one did not do anything with qso's and hard drive, it just stopped after a delete function (of a qso) from Fldigi.
I will lets things settle in a bit as I am just learning your very nice program. Will run a defrag and optimize and will see how that does as the days go on.

One interesting thing; On setting up with FLdigi (recommendations from the manual- pg 176) and a Flex 6500 I had to NOT use the recommended rpc-xml, but had to go to TS480 for rig control. Then the 6500, Fldigi and Log4OM all played nice, PTT, CAT, Logging, etc. at this point working well.

EDIT: As of today Log4OM has been very stable with no lock ups, but it looks like I was mistaken regarding using TS480 for rig control. Yes RIG control works great but, it will not accept FLdigi logs , I guess it needs rpc-xml then. Log4OM communicator is set and minimized.

Will take a look at the portable version.

Thanks for your response.

73
Chuck

[IW3HMH]

Keep me informed pls.

[w9nwrwi]

Daniele,
Well not quite sure what is happening. I opened up programs in the following order; SmartSDR CAT Flex 6500/SmartSDR/Fldigi/and then Log4OM with communicator operating and minimized. Log4OM was not opened as Administrator. After about 5 minutes
Log4OM froze up. I task manager shut it and Communicator down. Kept everything else open and restarted Log4OM as Administrator.

It has been running for about 4 hours now without trouble. Configuration in FLdigi is using Hamlib (TS-480) and with this setup (contrary to Log4OM manual pg 176) all CAT control, logging from FLDigi to Log4OM is working just fine.
Cluster working great, all databases (maps, awards, qsl's, etc.) working.

Band switching, freq change, by Flex6500 being followed nicely by FLdigi.

Its working great at this point so will not change anything. The only thing I did to the computer since first days trouble/config and today was remove Microsoft Update # KB3022345 which was giving me integrity violation when I checked system with a Scan File Command.
Today Microsoft delivered a number of updates which included KB3068708 (updated KB3022345) which I told it to not install.

So far so good at this point.

73
Chuck