Vbindiff Doesn't Like Spaces In Filenames!

Hi! I have and use VBinDiff with my file compression techniques to compare the decompressor's output to the original file and recently noticed something: it doesn't work properly if there's a space in the filename, even though I'm surrounding the path with quotes: when I attempt to do that, it displays its help text. I'm wondering if this issue was resolved in a recent version, because I had my version for a while.

 

Not that this is ideal but try using either an underscore _ OR using a dash - in place of the spaces to see if that solves that issue you found. As for updates that may have fixed it, I don't know. IF you plan to attempt updating the program, BEFORE you do so, create backups & restore points so IF you don't like what the updates do and/or there are other problems with the updates you can revert back to the version you currently have & are using.

 

If you're talking about renaming the file before using it, I made a copy of the file and renamed the copy, and it worked. As far as updating it, I don't need a restore point, as it doesn't change settings upon install: I just extract and use it. The reason I posted this here is because I didn't like the issue.

 

I just looked, and the program wasn't updated since 2017.

 

If you mainly need to check that decompression reproduced the original bytes, Windows already has a binary comparator: run fc.exe /b "C:\path\original file.bin" "C:\path\decoded file.bin" in Command Prompt. It accepts quoted paths with spaces; exit code 0 means identical, 1 different, and 2 a comparison error (not a mismatch). Use fc.exe rather than fc in PowerShell, where fc can be an alias. That won't fix VBinDiff's interactive viewer, but it avoids renaming your test files just to verify the decompressor.

 

I thank you for your suggestion, but I prefer VBinDiff's interactive approach. I can create another batch file to do this, as I'm using a batch file for VBinDiff. I plan to do it later today.