HashCheck
HashCheck copied to clipboard
idrassi
HashCheck Shell Extension for Windows with added SHA2, SHA3, and multithreading; originally from code.kliu.org
Verifier bug: 260 character path limit. Affects Verifier, but does not affect Create Checksum File.
If you are running a version of Windows that exhibits the 260 character MAXPATH limit, eg, Windows 7, 8 or 10, you can use HashCheck's shell extension to Create Checksum...
Actually, with current version 2.5, we can only search about Hash to compare with another one. Please make like Hashtab, an easy feature to compare Hash with another one file...
Currently it uses Windows EoL (CR+LF), for obvious reasons, but many Windows text editors (including Notepad and Wordpad) as well as Checksum tools handle the Unix EoL (LF) without issue....
I do not know the speed difference between that and blake3 but I wanted to ask if the support for that algorithm will be added? Thanks.
Not sure if this is something HashCheck can prevent, but trying to open a `*.blake3` file after upgrading to Windows 11 23H3 showed an error saying something to the effect...
HashCheck does not currently support long path names (> 260 characters).
Basically what I put in [The Checksum doesn't respect my "View Settings"](https://github.com/gurnec/HashCheck/issues/51), but in short this is what happens: - If you have your folder sorted by Type and you...
When creating a check sum, the files aren't in order... This has been discussed before, but hasn't been fixed yet.
