Messages

1

Support and Feedback / Re: File Verifier start of calculation

« on: September 01, 2026, 08:08:16 »

When I double click a checksum file, the "File Verifier" opens and the entry is ready for running the check.
When I double click a second checksum file, the second entry is added, but the firs entry gets calculated and shows green the success of verification.

I have to start only the verify of the newest entry by hand.

2

Support and Feedback / Re: File Verifier start of calculation

« on: August 31, 2026, 15:41:50 »

Your comment contradicts the current implementation: adding a check starts automatically the check of the previous added check...
Version (x64) v16.2 (build 3211)

3

Support and Feedback / Re: File Verifier does NOT check sha files

« on: August 31, 2026, 12:03:01 »

To ignore the format marker for SHA checksum is a HACK, that will work in most cases, but not in all.

SHA1 file can be generated in text or binary mode, and on Linux the default is text!

Command in Linux for text mode: sha1sum -t filename.sha1, the resulting checksum file has "  " as format marker in front of the file name
Command in Linux for binary mode: sha1sum -b filename.ext, the resulting checksum file has " *" as format marker in front of the file name
Without an option, text mode is used

So only reading the marker and calling the calculation in the correct mode is the 100% solution.

4

Support and Feedback / Re: File Verifier does NOT check sha files

« on: August 31, 2026, 11:42:31 »

Please read all my comments carefully. I am not a random support forum poster. I report real problems.

When generating a SHA1 file, reading the input byte by byte, the correct .SHA1 file has a * in front of the file name: E836D9DCBE84E119124034499EBC62DE183C35B6 *LoreIpsum.txt

Your "File Verifier" for .SHA1 tries to open the file "*LoreIpsum.txt" (with the * in the file name) and the verification fails because the file is not found.

5

Support and Feedback / Re: File Verifier does NOT check sha files

« on: August 31, 2026, 11:16:54 »

When calculating the check sum, the input file normally is read "byte by byte", what is called "binary" mode of calculation. This is why in the checksum file, the * in front of the file name marks the calculation as binary.
Alternatively, the input is read as text, transforming line breaks to the system settings, what is called "text" mode of calculation. This is why in the checksum file, the second " " in front of the file name marks the calculation as text.

6

Support and Feedback / Re: File Verifier does NOT check sha files

« on: August 31, 2026, 11:05:54 »

The specification for a checksum file are
[checksum][space][format][filename]

The format is a space for text or a * for binary, resulting in a 2 spaces separator "  " or a space and * separator " *"

Following the specifications, a file that is calculated as text has 2 spaces between checksum and file name, a file that is calculated as binary input has a space and a * between checksum and filename

Your "File Verifier" only accepts the " *" separator for .MD5 files
Your "File Verifier" only accepts the " " or "  " separator for .SHA1, .SHA256 or .SHA512 files

https://share.google/aimode/iNfBL2kQlHTPmklSb

7

Support and Feedback / File Verifier start of calculation

« on: August 31, 2026, 10:30:48 »

When I double click a file checksum, the file verifier opens and is ready for calculation.
I would expect that the calculation is done automatically.

When I double click an other file check sum, the already present file check sum is verified, but the newly added is only ready for calculation.
I would expect that the calculation is done automatically.

When i drop an other file to a verification entry, and start the verification, the message "50% done" is shown.

8

Support and Feedback / File Verifier tab column header

« on: August 31, 2026, 10:23:03 »

The "File Verifier" tab column header has unexpected behaviour.

When I move a column during width adjustment to the right margin, all column to the right of adjustment disappear. The visibility can still be toggled in the context menu, but the columns are gone.
There is no option in the context menu to add the column again.

Work around: get a fresh "File Verifier"

9

Support and Feedback / Re: File Verifier does NOT check sha files

« on: August 31, 2026, 10:16:43 »

The "File Verifier" works for

• .MD5 file with binary mark (after check sum a "space" and a "*") and file name
  
• .SHA1 file with text mark (after check sum 1 or 2 "space" ) and file name.
  

The specification allows for all checksum files .MD5, .SHA1, .SHA256 and SHA512 the binary make " *" or the text mark "  ".

The extension .SHA is recognized as checksum file, but no calculations are done

If the file name is missing in the checksum file, I can drop a file in the "File Verifier". I expect that the calculation is then done with this fiel. No calculation is done.

Examples of accepted and not accepted check sum files are attached

Powershell 7 command to  generate a accepted .MD5 checksum
$hashObj = Get-FileHash -Path .\LoreIpsum.txt -Algorithm MD5
"{0} *{1}" -f $hashObj.Hash, (Split-Path $hashObj.Path -Leaf) | Out-File -FilePath ".\LoreIpsum.md5"

Powershell 7 command to  generate a accepted .SHA1 checksum (no * in output, but it is calculated as binary)
$hashObj = Get-FileHash -Path .\LoreIpsum.txt -Algorithm SHA1
"{0}  {1}" -f $hashObj.Hash, (Split-Path $hashObj.Path -Leaf) | Out-File -FilePath ".\LoreIpsum.SHA1"

10

Support and Feedback / File Verifier does NOT check sha files

« on: August 20, 2026, 09:04:04 »

Observation: when clicking on SHA checksum file, the "File Verifier" opens. I can add the corresponding file for check. Pressing the start button for the SHA check , 0 (zero) files are checked.
Using the dialog with only a MD5 checksum, the dialog adds the corresponding fiel automatically and check works fine.

Expectation: the SHA check works the same way as the MD5 check.

Version: (x64) v16.2 (build 3205)