Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • April 30, 2017, 11:27:00 PM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Last post Author Topic: Release: SFV Ninja (Simple File Verification application)  (Read 73008 times)


  • Charter Member
  • Joined in 2006
  • ***
  • Points: 1
  • Posts: 7,871
    • View Profile
    • The Blog of Deozaan
    • Donate to Member
Re: Release: SFV Ninja (Simple File Verification application)
« Reply #150 on: March 17, 2017, 04:45:44 PM »
I have two folders, say named Folder A and Folder B.
They're stored under different paths and have different names. Inside are other nested folders and files, which have the same general directory structure, but may or may not all match. What I'm trying to find out is exactly what's there and what's not, and for the ones that have same filename and patch, whether they're indeed the exact same files.

The fact that SFV Ninja stores relative paths instead of absolute paths lets you accomplish what you want:

  • Use SFV Ninja to create a checksum file for Folder A.
  • Save the resulting checksum file in Folder A.
  • Move the checksum file (or copy it) to Folder B.
  • Open the checksum file with SFV Ninja and have it verify the checksums.
That's what I thought would be the steps, except when I created the checksum file and moved it to the other folder, then selected "Load checksum file" -> "Verify All", all I got was the program re-verifying all the files in the initial folder that the checksum was created from. I also tried "Scan folder for checksum file and load" and got the same result.

That shouldn't happen if you follow my instructions to save the checksum in Folder A. Since the paths are relative, it should verify the checksums for the current folder, which will be Folder B after you copy/move the file.

I also forgot to say that after you've copied/moved the file, you should clear the list, and then add Folder B to the list using the "Add folders to list" option before loading/verifying the checksum file. This will show you which files don't exist in Folder A, since they won't have any checksums saved in the checksum file.


  • Supporting Member
  • Joined in 2015
  • **
  • Posts: 16
    • View Profile
    • Donate to Member
Re: Release: SFV Ninja (Simple File Verification application)
« Reply #151 on: March 22, 2017, 09:30:08 AM »
@Dezoaan Thanks, I got the sfv working now.

This might be a bit confusing but where you save the SFV file is important in relation to which files are in the list:
  • Files that are on the same drive as the saved SFV file path are saved with paths relative to the save folder.
  • Files that are on a different drive than the saved SFV file path are saved with full paths.

Thank you for the reply, but as an average user, it IS rather confusing for me why the location where the sfv file is saved should matter. It's especially hard to understand just from reading the two sentences.  :huh: BtW, by "same drive" do you mean an entire physical hard drive itself or just a logical partition?

I've managed to accomplish the initial goal of comparing those two folders by saving the sfv file first inside the first folder. After some more time testing and using SFV Ninja, I do have some additional questions:
There are some cases where it's not possible to save the sfv file in the exact same location as the files/folders the checksums were being generated for. For example, when reading the contents of a networked drive or an optical disk/image. The original path might be read-only. Is it absolutely necessary to save the checksum in the exact same path? Is there another way?

Also, it would be helpful to be able to export the results of the checksum comparison report as a txt or html formatted file. I've tried to directly use Ctrl + C to copy the results and paste it into notepad, but it appears the contents are not possible to copy into clipboard.