CHK Hash Tool

[encode]

Well, it's C++ Builder with its flat and inane beyond belief 32-bit compiler.
64-bit compiler is somewhat okay though.
Thus I do recommend to use 64-bit CHK only! Think it as I'm keeping 32-bit CHK just for compatibility...

[persicum]

Well, it's C++ Builder

I see... It is kinda Borland Pascal...
Nevermind, since the bottleneck is reading from HDD, both 64 and 32-bit is very useful. RAM-disk benchmarks are far apart from real life.

[encode]

HDDs are dying these days. As example I have only one 512 GB SSD in my system (Samsung 840 Pro). Some archived files are stored in external RAID1 HDDs though. Anyway, at true 540+ MB/sec reading it's not a bottleneck anymore...

[persicum]

HDDs are dying these days. As example I have only one 512 GB SSD in my system (Samsung 840 Pro). Some archived files are stored in external RAID1 HDDs though. Anyway, at true 540+ MB/sec reading it's not a bottleneck anymore...

In that case we do not need all these hashes except blake2sp as in WinRAR5 -))

[Matt Mahoney]

HDDs are not going away as long as they are 10 times cheaper per byte than flash/SSD. If current trends continue, it will be 10-20 years before that changes. http://www.jcmit.com/mem2013.htm

[Piotr Tarsa]

I think that in consumer space HDD will lose their popularity sooner than that. Now HDD capacities are in the range of single terabytes and I'm not really convinced that users will store ever increasing sets of files. Broadband connections are becoming more and more common so keeping eg movies on disk is becoming less and less relevant. Once 1 TB SSDs are as cheap as 100 GB SSDs are today I think HDDs popularity will quickly diminish.

However, when building a heavily replicated storage cloud or something like that, HDDs will still be a better option.

[Matt Mahoney]

Right. With a fast internet connection, you don't need a lot of storage. HDDs will be mainly for servers.

[encode]

What's new in upcoming versions:

• "Anime Checker" feature - if a filename contains a valid hash - the file icon will be set to OK sign
• Redesigned icons - as in older versions, but 32-bit ones. Back to classics.
• Most likely, CRC16 (as in older versions, same as in LHA archives)

Not sure about "Add Hash to Filename" feature - can't figure out how to make this thing 100% clear, simple and useful - how to fit it right in. Even SHA1 might be too long for filenames. It could be better to add simple "Rename" command or something...

[encode]

[encode]

Anime Checker example:

[surfersat]

Anime Checker example:

Anime checker is a nice feature!

Greetings.

[Fallon]

I still like this proggie of yours as much as ever. CHK is useful and simple and so the portable lives in the root of my system.

I think that in consumer space HDD will lose their popularity sooner than that. Now HDD capacities are in the range of single terabytes and I'm not really convinced that users will store ever increasing sets of files. Broadband connections are becoming more and more common so keeping eg movies on disk is becoming less and less relevant. Once 1 TB SSDs are as cheap as 100 GB SSDs are today I think HDDs popularity will quickly diminish.

Look at it broadly. People will keep whatever is in their interest, which is what they want to own. In the 19th century, stored data may have been a library, nowadays it is electronic data for business or for personal consumption (Music, movies, books, games, whatever).

'Broadband connections' refers to the cloud. The cloud is most useful for exchanging things like:
-1- unimportant business data.
-2- consumer data that costs extra to use.
Hyping the cloud for everything under the sun is in the interest of the companies providing the cloud (examples: Microsoft can charge 10 bucks a month for MS Office 365, Netflix can charge for movies), but it is only partly in the users interest.

1) If business is important - lets say your business has innovative ideas, then safety becomes an issue. Putting sensitive data in a cloud that is not yours, is risky.
2) If consumers have to pay to get data down from the cloud, then it will become all the more interesting to keep the data they do own, on a backup device at home, under control. Personal backup is not out of reach like a library was in the old days. But everything in the cloud can be out of reach.

So I see people store all the sets of files they want to own, including favorite movies.

[encode]

[nburns]

Right. With a fast internet connection, you don't need a lot of storage. HDDs will be mainly for servers.

Internet connections don't store data, though; they only move it around, so cloud storage doesn't directly affect the quantity of drives demanded -- just who buys them. Cloud storage offers the potential to save tremendous amounts of space through deduplication. But deduplication seems to have unavoidable privacy concerns.

[encode]

The Hash Explorer concept:

[encode]

Dear readers from the United States, I need your assistance!
How you'd call the "Uppercase Hashes" option? Is it look natural and self-explanatory to you? How about "Use Uppercase", "Display Hashes in Uppercase", ... ?

[Mangix]

Uppercase Hashes sounds fine. Display Hashes in Uppercase sounds verbose. Use Uppercase sounds slightly ambiguous

[nburns]

Uppercase Hashes sounds fine. Display Hashes in Uppercase sounds verbose. Use Uppercase sounds slightly ambiguous

Capitalize Hashes might be clearer. In any case, it will probably become obvious once the user clicks it.

[encode]

Capitalize Hashes might be clearer. In any case, it will probably become obvious once the user clicks it.

The thing is, "uppercase" (upper-case) and/or "lowercase" are sort of keywords in hash tools.

[encode]

Yes we can!

[encode]

The copied text example:

7581BBEAE184772BFE6474FE8ED083BCAB9C38BB *RealTemp.exe
74CA048B4118D12BC6C2550F2715858E5A47659F *RealTemp.ini
96A4D072ED81D5FC0B56B033B90B6FC3258CEB6A *RealTemp.zip
9A36BDBD3B59D8854ED5AA09751635B478550DB8 *RealTempGT.exe
1A185F28F642F197B668D6DFF60D094272EE5947 *RealTempGT.ini
CB5B1EF83E8854747B25B447F52927EDFA29E6E0 *RTCore.cfg
747285C5DE346B141F1C0624116B0C1ABC7077E1 *RTCore.dll
DDB94D9BC031ABF1AFE97DFEA32685A2369C7FE3 *RTCore.rth
824999C9C8CF2227DCEA304BBC67B09EF4F563E8 *RTFont.fon
8BE972FA6BD14E253618DF7966F50D5EF670B11A *RTShutDown.bat
37B18D278975591AF8F6A9AB6FF72D4A5FDFCDA3 *RTWarning.wav
F15AF33A43D6AF621159EC0D74A7A7B09CB28A73 *WinRing0.dll
8AC34EB21B9B38F67CD29684C45696C20AB2E75A *WinRing0.sys
E6DD89BD8E29C66BE84B00154998046FFF3FFA00 *WinRing0x64.dll
D25340AE8E92A6D29F599FEF426A2BC1B5217299 *WinRing0x64.sys

[encode]

And again, should I rename "Copy Hash" command? "Copy Hash(es)" / "Copy Hashes"? Or "Copy Info" / "Copy Hash Info"?

[encode]

Or simple "Copy" is enough?

[encode]

To avoid "Feaure Creep", CHK v1.60 will be released very soon!

[encode]

Okay, the CHK v1.60 is here:
http://compressme.net/

[Mangix]

interesting note:

I ran MinGW's strip utility against the 64-bit chk.exe and reduced the size.

Original: 8,671,602 bytes

Stripped: 6,760,960 bytes

Figured I'd post this since this is a forum about making files smaller .

[encode]

Thanks for your hint! I'll keep that trick for a next release!

[Bulat Ziganshin]

just add "-s" to the gcc compilation comnmand - it runs "strip" on the produced executable, f.e.:

gcc -static -O3 -s lzd.cpp -olzd.exe

[nemoW]

Could you please add TTH calculation?

[encode]

Honestly, this feature is in my TODO list for a couple of years now.
The next release will feature CFG-file (CHK will keep selected hash type and other options)