Recent Posts

Pages: 1 ... 5 6 7 8 [9] 10
81
Support and Feedback / Re: File Verifier start of calculation
« Last post by Mathias (Author) on August 31, 2026, 11:40:53 »
I don't like autostart because it does not work for the way I use it. I like adding files to check (large ones),  and then I add some more, and then some more.. and then I start the work and can leave the machine to work and go to something else.

Checksum module currently don't do any settings/customizations. Not sure I want to add a whole settings things for just one settings . Hmm I see if I can add add settings for it someway or something.


82
Support and Feedback / Re: File Verifier tab column header
« Last post by Mathias (Author) on August 31, 2026, 11:34:33 »
column should not be able to be reordered.  I will fix that
83
Support and Feedback / Re: File Verifier does NOT check sha files
« Last post by Mathias (Author) on August 31, 2026, 11:30:45 »
When getting checksum of a file, the data from the file is always read as binary. they are never converted into text.   to much can go wrong with that.
84
Support and Feedback / Re: File Verifier does NOT check sha files
« Last post by SwissKnife64 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.
85
Support and Feedback / Re: File Verifier does NOT check sha files
« Last post by Mathias (Author) on August 31, 2026, 11:08:17 »
Not sure what you mean with binary.  all checksum files are text files.

86
Support and Feedback / Re: File Verifier does NOT check sha files
« Last post by SwissKnife64 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
87
Support and Feedback / Re: File Verifier does NOT check sha files
« Last post by Mathias (Author) on August 31, 2026, 10:36:33 »
I'm not sure I understand everything you trying to say?

So if the checksum file has 2 or more space between checksum and filename it does not work ?
if file does not contain filename it does not work..
and .SHA does work ?



88
Support and Feedback / File Verifier start of calculation
« Last post by SwissKnife64 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.
89
Support and Feedback / File Verifier tab column header
« Last post by SwissKnife64 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"
90
Support and Feedback / Re: File Verifier does NOT check sha files
« Last post by SwissKnife64 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"
Pages: 1 ... 5 6 7 8 [9] 10