v0.5.7.5491: New file based configuration backend

Testing release v0.5.7.5491 brings a few significant additions, including a new configuration backend, support for FSUM extended MD5 hash files, configurable algorithm name compatibility remapping, and improved dialogs for processing, recalculating, and verifying files.

The configuration for FileVerifier++ is no longer stored in the Windows Registry, but instead a configuration file residing in either the program directory, or %APPDATA%\FileVerifier++. This allows one to have a truly portable install that does not leave program settings on the computers in which it is run.

Also new is support for FSUM extended MD5 hash files. The extension to the MD5SUM format allows storing the algorithm used to calculate the hash within the file, which allows such files to have hashes that were calculated with algorithms that differ from the algorithm in the file extension (i.e. having SHA1 hashes in a file that ends with .MD5).

Related to this, there is also a new configuration file that specifies algorithm name mapping for different formats (known as algmap.cfg). Different programs use different names for algorithms, such as RMD160 vs. RIPEMD160, so being able to configure this translation is necessary for compatibility with other programs. The program does not have any provisions for editing this file, though it may be edited by hand.

New dialogs for processing files, recalculating, and verifying hashes are included in this release. These dialogs now include information about processed and total byte counts, as well as time elapsed and estimated time remaining for a given operation. The overall progress bar is now associated with these byte counts, as opposed to the file counts as in the past.

See the file CHANGELOG.txt for further details.

As a reminder, it is highly recommended that one reboot after removing an existing version of FileVerifier++ when performing an upgrade, as certain files may be in use, which may prevent the system from updating them, causing incorrect installations. At bare minimum, explorer.exe should be restarted in between uninstall and reinstall.

Posted by Tom Bramer 2008-11-29

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks