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.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 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.
BtW, by "same drive" do you mean an entire physical hard drive itself or just a logical partition?
