2012-11-02, 12:19 AM
First you would need to obtain the source code which shouldn't be a problem since it's open source.
Locate the code offending code. You will probably need to read through the documentation to find it.
Fix the problem.
Recompile.
To 'fix' the problem, you can probably just add a line that always returns a valid checksum instead of the actual checksum. It would be annoying if you need version updates, but it works just fine. Redirecting the scan would work as well, but may be more complicated if SAI uses dynamic path names.
It really depends on your level of comfort with the code, but I'd just rewrite the checksum
Locate the code offending code. You will probably need to read through the documentation to find it.
Fix the problem.
Recompile.
To 'fix' the problem, you can probably just add a line that always returns a valid checksum instead of the actual checksum. It would be annoying if you need version updates, but it works just fine. Redirecting the scan would work as well, but may be more complicated if SAI uses dynamic path names.
It really depends on your level of comfort with the code, but I'd just rewrite the checksum

