Page 1 of 1

Fatdog64 & GTKHash/GHasher

Posted: Tue 08 Feb 2011, 17:45
by dolphinsupernova
Hi everyone,

I've just started using Fatdog64 which turns out to be most excellent. However, I would like to use either GTKHash or GHasher to verify MD5 Checksums.

Does anyone know if there is a package available to download as I have scoured the forums and not been able to find one. I freely admit that I do not have the knowledge to put together a 64 bit version PET package so, if anyone else could point me in the right direction (or know of an existing package), I would be most grateful.

Thanks,
Ade

Posted: Wed 09 Feb 2011, 13:00
by jamesbond
There you go. How to use (after installing the pet) - click a file, use "Open With" menu, and select "phash". Less flashy that GTKHash/GHasher, but gets the job done.

EDIT: Also works in other 32-bit puppies.

cheers!

Fatdog64 & GTKHash/GHasher

Posted: Wed 09 Feb 2011, 18:38
by dolphinsupernova
Hi Jamesbond,

Nice one! i've installed your Pet and tried it out but something seems to be wrong with the output i receive. I seem to get an xdialog screen with a large amount of text but nothing that resembles a MD5Checksum. Hmmm, don't know where to go with this.

Can you cast any light on my problem? Am i doing something wrong?

Thanks for your help,
Ade

Posted: Wed 09 Feb 2011, 22:55
by jamesbond
Updated. Uninstall the old one first. If you still get to see nothing, open terminal and type this in it:

Code: Select all

which md5sum
which sha1sum
and let me know what you see.

Fatdog64 & phash

Posted: Thu 10 Feb 2011, 21:14
by dolphinsupernova
Quality! Yes, this time it works so many thanks indeed.

I don't suppose you happen to know if this is going to be included in the next release of Fatdog?

Regards

Posted: Thu 10 Feb 2011, 22:07
by jamesbond
No worries. Remind me when a new release is near - that is, when you see some alphas/betas/rcs for the new version being published. Meanwhile I'll upload this to the repo.

Posted: Wed 13 Jan 2016, 04:59
by s243a
I'm surprised that these tools don't give the file length as well as the hash, since it would be easier to match the hash with a bad file if one could change the file size. Perhaps I'm wrong through. Maybe the file size is somehow embedded in the hash.