LogFusion FAQ (Frequently Asked Questions)

Error: "The application failed to initialize properly (0xc0000135)"

Do you receive the error "The application failed to initialize properly (0xc0000135). Click on OK to terminate the application." when you try to start LogFusion? If so, make sure you have the Microsoft .NET Framework v2.0 framework installed. Please visit the LogFusion Download page to download the correct version of the framework for your computer.

How do I perform a Silent Installation?

Why don't the line numbers in LogFusion match up with the numbers in my text editor?

By default, LogFusion will only load the most recent part of the file, to avoid performance issues when opening extremely large log files. This behaviour can be disabled by turning off the "Limit the number of bytes to load from a log file when first opened" option on the Log Settings tab in the LogFusion Settings.

Also note that LogFusion does not show blank lines, so if your log contains blank lines, this will also cause discrepancies in the line numbers.

LogFusion Command Line Options

Using the command line, you can launch LogFusion without previously opened logs, or you can specify which logs to open. The command line options are as follows:

LogFusion.exe /noloadlogs
Launches LogFusion without opening the logs that were open the last time LogFusion was closed.

LogFusion.exe "path to log file"
Launches LogFusion and opens the specified log(s).

Examples:

LogFusion.exe "C:\Logs\System.log" "C:\Logs\Application.log"
Launches LogFusion and opens C:\Logs\System.log and C:\Logs\Application.log, as well as the logs that were open the last time LogFusion was closed.

LogFusion.exe /noloadlogs "C:\Logs\System.log" "C:\Logs\Application.log"
Launches LogFusion and opens only C:\Logs\System.log and C:\Logs\Application.log.