FileHasher.exe x86 for HDDB

[salazor]

I am looking FileHasher.exe x86 for HDDB, in the network find only x64 - if anyone has it I will be grateful.

Regards.

[horst.epp]

Use the setup of version 4.4.0
It will install the right version depending of the OS.
You can also use 7zip file manager and open the setup file as archive.
Its the 2nd entry of filehasher.exe

[salazor]

I did as you wrote, and it actually is but x64 - Setup file x86

[therube]

I'm not following?


http://www.softpedia.com/get/System/Fil ... Hddb.shtml
.exe installer, [32-bit only -- WRONG, SEE BELOW], includes FileHasher.exe (all files are 32-bit [WRONG])

http://www.softpedia.com/get/PORTABLE-S ... Hddb.shtml
"portable", separate 32 or 64-bit downloads, stand-alone .exe, does not include FileHasher.exe (or anything else)

[salazor]

I'm not following?


http://www.softpedia.com/get/System/Fil ... Hddb.shtml
.exe installer, 32-bit only, includes FileHasher.exe (all files are 32-bit)

http://www.softpedia.com/get/PORTABLE-S ... Hddb.shtml
"portable", separate 32 or 64-bit downloads, stand-alone .exe, does not include FileHasher.exe (or anything else)

Are you sure that all files in the Setup 32-bit are actually on x86.

Filehasher unpacked from setup, start HDDB and received - FileHasher.exe is not an application Win32.

Also I checked in PE Explorer and filehasher is AMD64, PE32+ (other files are 32-bit i386, PE32)

[therube]

Well I'll be.

On XP, x86, when I manually unpacked Hddb-Setup-4.4.0.exe (I believe I used uniextract & not 7-zip directly?), all I got were 32-bit programs.
On Win7, x64, sure enough I get both 32 & 64-bit hddb.exe & FileHasher.exe.

I would have expected XP to at least unpack the x64 .exe's, even if I couldn't do anything with them. (I'll have to try some more similar programs & see what they do. 7 Taskbar Tweaker is that way.)


So they're both there.
Take, Hddb-Setup-4.4.0.exe & extract with 7-zip.
(I don't use the GUI.)

> 7z.exe x Hddb-Setup-4.4.0.exe

It will "find" duplicate file names, & will prompt you as to what to do.
Tell it to 'A(u)to rename all', that way both the 32 & 64-bit files are retained.
If you do not, one will overwrite the other.
The "secondary" files are named "_1", so you'll get FileHasher.exe & also FileHasher_1.exe.
One will be 32-bit the other 64-bit.


(HDView.exe, Hddb_Srv.ex & Hddb_Gui.exe are only 32-bit.)

[salazor]

Many Thanks, works!!

[therube]

(I believe I used uniextract & not 7-zip directly?)

Yep.
Uniextract only left 32-bit.
7-zip gave me both 32 & 64-bit.

[salazor]

I run FileHasher and a great disappointment, I thought I'd find duplicate files, and this time each hash is different even for identical files.

It is a pity that in Everything there is no Hasher or similar.

[therube]

Eh, so tell me, just how does FileHasher work?
What do you do with it?

Oh, you have to run it from within hddb, cannot run directly.

Duplicate Cleaner, upcoming 4.0 version (that I imagine is still some time off yet) will have the ability to store hashes.


Are you able to limit what Hasher hashes?

And once it finishes (seems like it will take forever on my end & I don't have the patience), then what do you do with it, how do you interact with it?

I see you can add a Hash column to the file listing.


And even so, if it were to finish, & you have the hashes, then what?
Yes you can identify duplicates.
But?
As in how often will that come into play?


Without having a stored hash, Everything's dupe: / sizedupe: functions can go a long way to pointing out potential (byte-by-byte) duplicates.

And assuming you'll want to start with the largest files first, to remove the biggest pieces of cruft early on, its easy enough to highlight the particular files & send them to an actual file hash program to confirm that they are identical, prior to deletion.

I use dedicated duplicate file finders, hash programs, & of course Everything, depending on particular circumstances.

[salazor]

Yes, I do exactly as you wrote.

HashMyFiles says that the two files are identical, and HDDB displays hashes 00015421 and 00015422 and the in column "Duplicate Count" all zeros.

Also hashes of HDDB are useless.

[therube]

(seems like it will take forever on my end & I don't have the patience)

So I changed Options to only include 1 drive it its .db, so then hasher only deals with that one drive also.

Now ...

Well it certainly doesn't find duplicates.

I wonder just what the hash is?
Wonder if it is not actually a hash (of the file contents - which doesn't really make sense?) but rather a hash index

Possibly a CRC16, but it doesn't return results as my CRC16 program does.
Plus CRC16 would be worthless for determining "identical" in any case.

[therube]

Wonder if it is not actually a hash (of the file contents - which doesn't really make sense?) but rather a hash index

Yea, something like that.
FileHasher does not compute a files "checksum" value.

It is simply a numerical indicator (in hex) assigned to every (most, actually, as there are a few files with no hash) file, according to a files alphabetical "position" in the file list.

(@File shows 11754 items for me, the last has a "hash" of 00002DE9, which equates to 11753 [decimal].)

So what purpose that serves, I have no clue?

Likewise, what the 'Duplicate count' column denotes... ?