I have noticed that the only file verification prog in PA is the md5check, and so I thought I might try to add my own program DySFV wich is a bit more graphical, and checks sfv files (but not md5 yet).
As far as portability goes, it is portable as it is, there are no settings, and the database for remembering hashed files is always located in the same dir.
Howewer, I wrote it in C#, wich is more or less a product of windows, so I can't really say if it adds anything in tempdirs or clutters something else. Could anyone around here who usually makes portable apps have a quick check? I bet you have some real nice tracing/tracking/monitoring software.
Also, I figured it would need a context menu in explorer and file association to be a bit more easy to use. So in the program you have two neat buttons, one to add contextmenu/fileassoc to registry, and one to remove. But does that violate some holy portability rule?
And finally, is there even interest in having a portable file verifier?
It will of course later in the future be able to read md5, and create sfv/md5, but update progress has been slow, since it has maybe 10 users 
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Since files are starting to come out digitally signed, we should be looking for something to check signatures, like
Sigcheck from Sysinternals.
Also, I'm thinking that C#.NET might not be the best platform, since its runtime is not installed by default on all machines -- meaning that it won't run on those machines without
being admin and (b) downloading and installing the appropriate runtime. Maybe you can adapt it so it doesn't require a runtime?
MC
I guess a tool like that could easily be integrated in any program who interacts with files, but is it really that useful?
Yes, this thought has occured to me as well. But as far as I know .NET is integrated with Vista and shouldn't be a problem there (don't have vista myself), and I think more and more have it installed in WinXP too, since you need it to run any MS app that starts with "Live", or the excellent Paint.NET for that matter. And I bet it will be included in WinXP SP3.
I think trying to get it to work without the runtime is nigh impossible.
If you are talking about SFV or MD5 or SHA or even checking digital signatures, there are dozens of very fast libraries around that do not rely on the dotNet runtime. It is very easy to do, unless your only programming tool is Visual Studio 2005.
Yes, the dotNet libraries are commonly included with new Windows installs, but they are still not universal.
QuickPar can use MD5 and SFV to verify. I don't think it is portable, but it is a vey common program that works reasonably well and doesn't rely on dotNET. MP3audiobookhelper works well too for MP3 files.
MC
I'm using this verification tool every day. It's portable and can calculate hashes, verify and create sfv/md5 file.
Jacksum. Supports most if not all hash algorithms in existence (the ones not considered broken anyway), has a very customizable output format, and excels at handling many files at once.
It's portable, but requires Java (which isn't uncommon, although you'll likely run into an old version).
Vintage!
Is it possible to check sfv/md5/sha1 with jacksum ?
Of course. Like I said, it supports most, if not all hash algorithms that aren't considered broken. Oh, and it uses the standard name for SFV (CRC32). Check out the webpage and read the documentation.
Vintage!