checksum 184.108.40.206bA new checksum (and simple checksum) beta has arrived! Here is the skinny..
++ You can now specify the number of errors that checksum will display on- screen before automatically switching to log-to-file mode.. error_display_limit=24 On a 1080p monitor, you could easily manage 50! ++ checksum can write its most recent command-line to a file, for your information. This file is written to your data folder (in portable mode, it's right next to checksum.exe). In checksum.ini.. write_command_line=true You can also specify the name for this file (also in checksum.ini). NOTE: This file is available at the very /start/ of the job. ++ You can now specify a target root directory when verifying non-absolute (aka. "relative") hashes. For example, if you created a relative .hash file for files in "D:\my files" and put the hashes in a folder, "e:\my hashes" using a command-line something like this.. crd("e:\my hashes") "D:\my files" .. You can now verify this .hash file ("e:\my hashes\my files.hash") (or tree of hash files) /in-place/ using similar syntax: vrd("D:\my files") "e:\my hashes" checksum prepends the specified path ("e:\my files") to the beginning of any hashes it finds on-the-fly, so a hash for "foo\bar\file.doc" would correctly translate to "D:\my files\foo\bar\file.doc". Neat. Thanks to Nacho for finally solving the dilemma of how best to approach this feature. A switch, of course! ++ In addition to the current relative path support, I added support for relative path /traversal/ so you can specify, for example.. checksum.exe cr "..\foobar" and have checksum hash a directory /next/ to the current working directory. ++ You can now abort an entire queue from either the system tray menu or tooltip windoid context menu. The option is "Abort Queue". You won't see this unless you have job queueing enabled. +~ Improved the @parent token (used for specifying the hash file name). You can now use multiple @parent tokens in a single command, e.g.. checksum.exe cr1j(@parent+1~@parent~@item)d(b:\backup\hashes) "d:\biz\documents\reports" .. which would output: "b:\backup\hashes\biz~documents~reports.hash" While I'm here; seeing as how you don't have a second, even a FIRST floppy drive any more, wouldn't it be a neat idea to use drive "B" for your BACKUP DRIVE! + Added a special @parent token: @parent* This will automatically create a string (for use in custom .hash file names) that is the entire path of the item being hashed. Whatever character immediately follows the switch is used for the separator. e.g. crj(@parent*~@item) "B:\Documents\Biz\Reports" Specifies a "~" (tilde) separator. This would create the hash file: B~Documents~Biz~Reports.hash + You can now use relative paths inside d() switches, i.e. output directory in creation mode and target root directory in verify mode. In both instances, the path is calculated from the current working directory. To change the working directory in a batch script, do: D: cd D:\My Files\Correct You can also use relative path traversal in these switches, e.g.. cr1d(..\..\..\hashes) "B:\documents\biz\reports" + checksum will warn you if you specify a non-existent output directory for your hashes, and will ask you if you want to create the directory. By design, there is no "don't ask me again" option for this dialog. If you decide to not create the directory, checksum will use its standard fall-back protocols. ++ By request, checksum can ignore custom hash types stored inside .hash files. For example, for use by a script that extracts only the data part of a media file for hashing. e.g. to skip a hash marked so.. #md5_jpg#Always_updating_this_EXIF_data.firstname.lastname@example.org:00 Use: skip_hashes=true skipped_hashes=md5_jpg If you have multiple types to skip, separate them with commas, e.g.. skipped_hashes=md5_jpg,md5_mp3,my_type ~ The out_dir setting is no longer available as a checksum.ini setting, you *must* use the command-line switch to set an output directory when creating checksums using "d(<file path>)". Sorry for any inconvenience. Note: if you want this set for *every* job (risky!) you can add it to your context menu commands. See the tricks & tips page for more info. simple checksum 0.9.4.0 ++ You can now have simple checksum close to the tray rather than exit, when you click the close button (X). This option is available (like most everything else) from the application menu (aka. "app menu") which you can get to by clicking the main program icon in the top-left of the window, or in later Windows versions also by right-clicking anywhere in the titlebar.
Full details in the itstory.
You can grab the latest checksum (and simple checksum) beta from the usual place.