Announcement

Collapse
No announcement yet.

File integrity checkers

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    File integrity checkers

    Spent some time looking for a decent application to create and verify the checksums of all the files that are stored on a drive
    For years i used a basic generator/checker that did only one file - very time consuming
    After having an experience with a failing backup drive, i was motivated to search for something a bit better
    After quite some time i found Corz Checksum, which was good with a right-click context menu item, but it had nags and also generated the hashes with additional characters that did not show up on notepad.
    Then i tried MD5 Checksum Verifier which was good, but limited in comparison.
    Finally, i tried Fastsum - which is very good.
    It handles sub-folders and can save changes to the checksum file after you have altered the contents of the folder.
    It also creates entries in the right-click context menu.
    i found the best setup was to create checksum files with the extension ".checksum." and to create a checksum file for each folder.
    And hence have organized the files into folders, so that any folder can be checked relatively quickly.
    Movies usually get their own folder, unless there is a series or collection.

    Checksums are a good idea because if you experience any problems with a file, then you can run the checksum verifier and see if the file has being corrupted, and then move on to investigating/eliminating components that may have contributed to the corruption.
    They can give you advanced warning of failing components.

    i think that many of us have some degree of corruption, and hence need to compare our integrity with the ultimate checksum, which is zero, then make appropriate corrections, or mods, and run the file verifier each time we open a file or run an exe, to make sure that the system is relatively well-balanced and stable, or even running better than before.
    If some program is causing problems then it can be thrown into the recycle bin, or re-complied.
    Last edited by socketa; 08-28-2014, 11:58 PM.

    #2
    Re: File integrity checkers

    the GNU md5/sha file hashers do batch mode, so im not sure what your on about.
    Last edited by goontron; 08-29-2014, 12:19 AM.
    Things I've fixed: anything from semis to crappy Chinese $2 radios, and now an IoT Dildo....

    "Dude, this is Wyoming, i hopped on and sent 'er. No fucking around." -- Me

    Excuse me while i do something dangerous


    You must have a sad, sad boring life if you hate on people harmlessly enjoying life with an animal costume.

    Sometimes you need to break shit to fix it.... Thats why my lawnmower doesn't have a deadman switch or engine brake anymore

    Follow the white rabbit.

    Comment


      #3
      Re: File integrity checkers

      Total Commander (Windows Explorer replacement, much better) has a built in hash generator .. you select the files in the folder then go to files > create checksum. From there, you can also choose the hashing algorithm (sha1, md5) and the file is saved with a .sfv extension (it's just a text file with the filename and its hash on each line).
      You can double click that file and Total Commander will automatically check the file against the checksum in the sfv file.

      SFV files are standardized, they're used in the "warez scene" to verify integrity of downloaded files etc etc.

      But anyway... these checksum applications only generate a checksum for files and tell you if the file was changed or not. If the file got corrupted, it's lost either way.

      If you actually want to be able to recover files if they're changed or corrupted, you would be better off using an algorithm like PAR2 which creates recovery information for files.
      In most cases, a recovery record of about 10-15% of original file size will repair the original file when a few bits are corrupted.

      Comment

      Working...