OK, version 0.1 is available for Beta testing......
Remember: This is an "all care, no responsibility" production....
I've tested it on both E38 and LS1 log files and it works OK. It should be fine for the other controllers as long as...
- The 1KB header is std.
- The metadata section starts and ends the same way.
- There are no additional data sections in the log file ( apart from the actual log data).
Basics:
This utility ONLY works from the command line. If you are not comfortable using the command prompt / DOS window / ETC. then this is not for you. While the utility is only meant to work on EFILive log files, it will happily write to any file named. It is possible to overwrite files that you didn't actually want over written. PEBCAK is the responsibility of the user....
Set up:
simply unzip the file and save it to where ever you want. You can save it to C:\Windows or C:\Windows\system32 and it will be in your default path for the command prompt. If you put it somewhere else, you may need to add that directory to the path variable or use the full path when running the tool. I'd stick it in C:\Windows, unless there is already a file there called "join.exe"
Usage:
Start a command prompt window.
Code:
click on [start] - [run]
type in "cmd" ( no quotes )
then click on [OK]
Then change directory to where you have stored your log files. The STD. directory is under your "My Documents" folder.
Code:
cd "My Documents"\EFILive\V7.5\"Logged Data"
Next identify the 3 required parameters for the tool...
- Source File: This file is used for the PID description and it's data will appear first in the final log.
- Additional Files: the names of each file that you want to add to the source file. They are added in series so you can set the order you want.
- Output File: This is what the final joined log file will be called.
WARNING: This tool will overwrite any file named as the output file if it exists. It will not ask for confirmation.
You can run the tool in it's basic form....
Code:
join -s [source file] -a [add file-1] ... -a [add file-n] -o [output file]
It will take a couple of seconds to set up the environment, and then output some details on the screen as to what is going on. A sample screen will look like this...
Code:
> join -s BBL00119.efi -a BBL00120.efi -a BBL00121.efi -o test.efi
Source file: BBL00119.efi
Source size: 51637
Source Meta size: 613
Next File: BBL00120.efi
Next size: 51637
Next meta: 613
Next File: BBL00121.efi
Next size: 52137
Next meta: 613
Completed join to output file test.efi
There are 3 other command line switches.....
- -h : The "help" option, which gives some tips on the tool and how to use it.
- -v : Verbose mode, which just prints the metadata data as found in the source file.
- -d : Debug mode, which does everything EXCEPT write to the output file. This mode is useful when combined with "-v" to list the metadata if you want to check things like the PID selections.
So, if you feel up to it, try it out and see if it is of any use.
Simon.