Log Checksum Verifier for other Operating Systems

[GoogleCodeExporter]

There is the Rip log checksum plugin 
(https://code.google.com/p/xld/issues/detail?id=29), which works great on a 
Mac. But it's necessary to run XLD with the plugin installed to validate logs 
generated by it.

So the idea is very simple: Provide stand-alone binaries for other operating 
systems to verify the checksums of XLD logs. A very simple command line tool 
would be sufficient, which checks one or more log files and gives a simple 
output: Good / Bad.

Something similar exists for logs generated by Exact Audio Copy, CheckLog.exe, 
which is only available for Windows, unfortunately. Personally, I'm mostly 
interested in a binary for Windows, but I assume there'd be an interest for all 
major operating systems.

Thanks for your consideration.

Original issue reported on code.google.com by xispy2 on 29 Aug 2014 at 10:31

[GoogleCodeExporter]

Here is a standalone log checker for Win32 (works under CLI). It should run on 
*nix systems using wine.
Note: SSE2 is required.

Original comment by tmkkmac on 10 Sep 2014 at 2:16

[GoogleCodeExporter]

Original comment by tmkkmac on 10 Sep 2014 at 2:16

• Changed state: Started

[GoogleCodeExporter]

Thank you!

Original comment by xispy2 on 12 Sep 2014 at 4:17

[GoogleCodeExporter]

Please report if it works properly.

Original comment by tmkkmac on 13 Sep 2014 at 8:26

[GoogleCodeExporter]

With initial testing I had some issues with character encodings: The log file 
must be in ANSI, everything else will result in a "Malformed". With special 
characters in the log's path name, the tool doesn't read the file at all.

But generally it seems to work as intended, which is great. Thank you so much 
for doing this, I'm sure there'll be other people appreciating this tool as 
well. I'll report back with more extensive results.

Since Wine is often a bit troublesome to use, is there any chance you could 
also provide a generic Linux binary?

Original comment by xispy2 on 14 Sep 2014 at 10:24

[GoogleCodeExporter]

>The log file must be in ANSI
That's strange. The log files from XLD are encoded with UTF-8, and changing 
encoding should result in "Malformed" result. The checker reads the file as 
binary, so the file encoding shouldn't be a problem.

>With special characters in the log's path name
This is a known issue. My compiler toolchain is mingw, and it doesn't support 
unicode entry point (wmain).

>Wine is often a bit troublesome to use
As far as I've tested the checker works with wine without problem.

Original comment by tmkkmac on 15 Sep 2014 at 2:54

[GoogleCodeExporter]

Here is a new version fixing path name issue.

Original comment by tmkkmac on 15 Sep 2014 at 5:05

Attachments:

• xldlogchecker_win32_20140915.zip

[GoogleCodeExporter]

Awesome, thanks for your quick response. I'll test and let you know, if I find 
any more issues.

Original comment by xispy2 on 15 Sep 2014 at 10:16