File Verification Part 2

A little while back I mentioned a project I was working on called File Verification. I have some feedback and it seems that it may have been a little 'heavy going' and the underlying idea may have gotten masked resulting in a brief visit and swift departure.

I've 'pulled' the web page and will restore it with a brief description with a downloadable help file. A draft has been prepared and is being proof read by another member who will also contribute ideas to rewriting sections where I have muddied the waters by my style of writing.

I won't mention who it is as, like myself, he is busy on other matters.

I will also be writing a setup type file requiring just the usual one click install.

With regard to a particular file which may be corrupt I have written an app where two or more members with the same file can conclusively show whether or not the suspect file is corrupt.

Knowing for definite one way or the other can save a lot of time including searching for a replacement when one is not needed.

There are precious few programs which can do this for us varying from shareware packages doing much more besides to freeware which uses many variations on a theme.

Mine uses one method and concentrates on doing one job, does not need VB run times, dlls and supporting files. It is simply a 29KB file zipped to 16.6KB - 4 seconds using dialup.

It has been vigorously tested alongside other apps available but vigorous testing wasn't really neccessary. The file has, of course, passed a virus check.

Cost: Free and no restrictions on use.

Pop over to FV Part 2

PS deltarho=gammaepsilon, the latter being my middle name

 

Added another app for local comparisons.

No interest shown in Sha1dr so perhaps WinBBS members never suffer from file corruption. Funny thing is I've seen quite a few posts in the last twelve months suggesting otherwise. It crops up in the MSKB a few times.

Still, it only happens to other folks and when it does 20 or so posts will be spent talking about extracting from cab files and where to get the latest version of a dll when all the while the file wasn't corrupt in the first place. Then we have the other scenario with all sorts of remedies being put forward when all the while the problem is a corrupt file. Nothing wrong with this - I've always said "Why write a sentence when a paragraph will do. "