Log4OM

Norton removed LogOMUI.exe, now Log4OM does not run?

I reinstalled Log4OM. Still didn't work.

So then I went to Norton and took LogOMUI.exe out of quarantine.

Now Log4OM thinks that it is a fresh installation, and does not find the previous log and configuration files. Where are my old configuration files, and how do I point Log4OM to find them?

Terry will likely provide the best and correct solution for getting your hiccups resolved.

I will only add that I used Norton "once" and that was about 6-7 years ago and it about wiped out my system and semblance of letting other applications run. That being said I am NOT a fan of Norton. I found it to be a serious resource hog and just seemed to take over my computer(s). I got rid of it (not an easy task either) and have used other protection APPs since.

The back up files that you have been keeping (You did keep backups didn't you?) contains a backup of the configuration files and an ADIF of your logbook. Restoring the backup has been covered a few times on this forum.

However I doubt that your main database was screwed by this Norton update so search for WHATEVER YOU CALLED YOUR LOGBOOK.sqlite or *.SQLite to locate it and then in Log4om use File/open database to open it in the software.

G4POP wrote:The back up files that you have been keeping (You did keep backups didn't you?) contains a backup of the configuration files and an ADIF of your logbook. Restoring the backup has been covered a few times on this forum.

However I doubt that your main database was screwed by this Norton update so search for WHATEVER YOU CALLED YOUR LOGBOOK.sqlite or *.SQLite to locate it and then in Log4om use File/open database to open it in the software.

Yes, I have the program set to backup after EVERY use.

And therein seems to lie a problem.

In my fiddling to try and sort this out, I have started and exited the program a number of times. Apparently Log4OM is set to keep only a number of "backups", and then discards the oldest, so all of my extant backups in "\appdata\roaming\Log4OM\Backups" have been generated in my efforts to recover.

Oh well, not to worry. I have a good complete ADIF file (which I also separately generate as a backup) so I will restart and reconfigure the program and then separately save a "golden" configuration file which Log4OM will be ignorant of and not discard.

Does that sound like a sound plan?

Yes but set the number of backups to a higher value like 12 or 15 and set the secondary backup to NOT delete

Norton Security quarantined Log4OMUI and I reported it to Norton. I just received the following reply:

Upon further analysis and investigation we have verified your submission and, as such, the detection(s) for the following file(s) will be removed from our products:

File name: Log4OM_1_26_0_0.exe
MD5: e9b135170868e795ed32d918b7e60797
SHA256: 31eec66299ea2ba82e08907cc9e1af4a7e6035b72f42199686265371c542d8ae
Note: Whitelisting may take up to 24 hours to take effect via Live Update

File name: LogOMUI.exe
MD5: c692e74e763692179f6ced6fed14ea40
SHA256: 99e8c9b296419d2f8c1ca298c2e3faa57b8a05b12f563c902ac0efcbab6f0291
Note: Whitelisting is available by downloading a RAPID RELEASE indicated in the Further Information section below or via the next Live Update

Further Information:
Required RAPID RELEASE sequence >= 182413

The latest Rapid Release definition available here: ftp://ftp.symantec.com/AVDEFS/norton_an ... pidrelease
To check the current sequence number of the Rapid Release definition: http://www.symantec.com/security_respon ... pidrelease
More information on Rapid Release definitions can be found: https://support.symantec.com/en_US/arti ... 03326.html

If detection persists, please contact support:
* Norton: https://support.norton.com/sp/en/us/home/current/info
* SEP: https://support.symantec.com/en_US/endp ... 54619.html

Decisions made by Symantec are subject to change if alterations to the Software are made over time or as classification criteria and/or the policy employed by Symantec changes over time to address the evolving landscape.

If you are a software vendor and would like to upload your software for proactive whitelisting, please complete one of the following forms:
* If you are BCS customer: https://submit.symantec.com/whitelist/bcs
* Otherwise: https://submit.symantec.com/whitelist

For more information on best practices to reduce false positives:
http://www.symantec.com/content/en/us/e ... .en-us.pdf


Sincerely,
Symantec Security Response
http://securityresponse.symantec.com