New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MD5 files with comments come up as "Damaged" #62
Comments
Here is an example:
|
It didn't see # as comment. When there are unknown lines, the status becomes "Damaged". Normally md5sum format seems to use ";" as comment. I updated my MD5 checker to recognize "#" as comment, too. From your sample, I added IsoBuster in creator. It will show the status correctly. I put the sample file (md5_sample_2022-02-25.zip) in "MultiPar_sample" folder on OneDrive. Please test it. If you have other format MD5 files, I can add its style by reading samples. |
Here is another MD5 format where MultiPar doesn't recognize the tool that created it:
|
Another one:
Another one:
I think that's all the MD5 file types I have handy. Thanks for the quick help! |
Thank you for samples of vrious format. I added those comment style for Creator. I put the sample file (md5_sample_2022-02-25b.zip) in "MultiPar_sample" folder on OneDrive. |
I have a lot of MD5 files with comments at the top using a leading # as the comment indicator. This doesn't cause MultiPar to fail, but it does say the MD5 file is "Damaged". If this intentional?
The text was updated successfully, but these errors were encountered: