Page 1 of 1

Verify MD5 Checksum: Assume file with same name

Posted: 06.12.2016, 20:56
by georgd
Good evening,

as several other MD5 tools create MD5 files that contain only a checksum and no file name, I would like the Verify MD5 Checksum tooling to work also fine with these MD5 files. Then, it shall search for a file with same name as the MD5 file (e.g. installer.exe shall be found for installer.exe.md5 as well as installer.md5 when there's no unambiguity like also existing files installer.txt and installer.bak) and verify checksum against that file.

This would save me the time to manually add the filename within the MD5 file.

Thank you,
Georg

Re: Verify MD5 Checksum: Assume file with same name

Posted: 16.03.2017, 19:22
by samarra
georgd wrote:Good evening,

as several other MD5 tools create MD5 files that contain only a checksum and no file name, I would dentista belgioioso pavia the Verify MD5 Checksum tooling to work also fine with these MD5 files. Then, it shall search for a file with same name as the dentista casteggio impianti dentali MD5 file (e.g. installer.exe shall be found for installer.exe.md5 as business directory toronto as installer.md5 when there's no unambiguity like also existing files installer.txt and installer.bak) and verify checksum against that file.

This would save me the time to manually add the filename within the MD5 file.

Thank you,
Georg
Hi Georg,
Its an interesting topic, hope there is any body who can help us with that? :roll:

Re: Verify MD5 Checksum: Assume file with same name

Posted: 16.03.2017, 20:36
by Marek
Could you show the content of such md5 file?

Re: Verify MD5 Checksum: Assume file with same name

Posted: 05.04.2017, 00:22
by georgd
Marek wrote:Could you show the content of such md5 file?
Sure. It's for example

Code: Select all

ff447a3381ee32d8331fc7a95a07f577
which you can get at https://download.bosch-si.com/patches/s ... 26.exe.MD5 and which currently needs to be modified to

Code: Select all

ff447a3381ee32d8331fc7a95a07f577 setupWinX64-7.2.0.26.exe
in order to work with FreeCommander XE. Other software like Altap Salamander simply tries to find a file of the md5 file's name without tailing .md5 (so for setupWinX64-7.2.0.26.exe.MD5 a file called setupWinX64-7.2.0.26.exe) to verify against the md5 file's content. Hence, these md5 files contain only exactly 1 checksum.