Log4OM

Evaluating Log4OM, fresh download and install on Win7. Looks promising, hope this works out.

A few problems:
1. Every launch generates dialog: Could not find file ...\Roaming\Log4OM\resourcestrings.xml
2. File >> New Database generates dialog: Could not find file ...\Roaming\Log4OM\LogOM.SQLite
...so it's impossible to create a new log.

-Gary NA6O

Gary,

Welcome aboard to V1 of Log4OM. We're deep into Beta testing of V2 and that is around the corner.

Regardless ... in case you have not done so yet, download the Log4OM Quick Start guide and read through that. There may be something you overlooked during your installation and might be noted in the guide.

Here is the URL to get you to the page to download the guide as well as the main Users Guide.

http://www.log4om.com/dl/

na6o wrote: ↑12 Nov 2019, 00:52 1. Every launch generates dialog: Could not find file ...\Roaming\Log4OM\resourcestrings.xml
2. File >> New Database generates dialog: Could not find file ...\Roaming\Log4OM\LogOM.SQLite

Sounds like you could have a bad install or download, try a fresh download and install as per page 1 of the quick stat guide to 'Run as an administrator'

I went through the entire download and install process 3 times. Same result. It simply doesn’t install the missing files.

Gary NA6O

na6o wrote: ↑12 Nov 2019, 15:56 I went through the entire download and install process 3 times. Same result. It simply doesn’t install the missing files.

Gary NA6O

Turn off all of your anti virus software, firewalls, malware protection and windows defender, CCleaner, I think the file is being blocked during install

I made sure NOTHING like that is active. Same result. Guess the installer doesn't like me. I have another machine I'll try installing on, just to see if there is a difference there.

-Gary NA6O

I figured it out. My security model is that my operating account is User level only. Installs require permission from an Admin account. So the required files were only installed in the appdata/roaming/Log4OM directory of the admin account. Moving the files over fixed it. All's well now.

-Gary NA6O

Thanks for letting us know