What's new in BinCmp 2.9.0
Nov 8, 2016
- now BinCmp reports system error code when file operation fails
- now, if left or right file path ends with '' or '/', the file name is extracted from the other file path. For example: bincmp -t -buf=64k \hostsharedfile.ext -copyto . continue copying: "-copyto -c"
- append mode alias: "-copyto -a"
- now BinCmp's full help includes the "Copy Mode"
New in BinCmp 2.8.0 (Aug 5, 2016)
- Added "-patchstr" to patch a file directly from command line.
- Different improvements for the "-x" (extra bytes) mode.
New in BinCmp 2.7.0 (Aug 5, 2016)
- Added "-help" and "-?" for full help (the standard help has been abridged).
- New switch "-x" allows to create and apply patch files that change the size of the input file (file1).
- New switch "-t" - the same as "-t=15000".
New in BinCmp 2.6.0 (Nov 27, 2014)
- copy mode added: "-copyto OutFile",
- return codes 215 and 216 added
- append mode added: "-appendto OutFile"
- write mode added: "-writeto OutFile"
- patch mode: return codes 115 and 116 added
- now bincmp is able to deal with I/O devices,
- return codes 331 and 332 added
- now error messages are mode-specific
- refactoring
- project file for Orwell Dev-C++ added ("bincmp.dev")
- this help file ("bincmp.txt") rearranged
- new switch "-err1"
New in BinCmp 2.5.1 (Nov 5, 2014)
- new switch "-s": if the file sizes are different, don't compare by content
- thus returning immediately when left file size != right file size).
- Correspondingly, return code 3 ("file sizes are different") added.
- some small refactoring
- VERSIONINFO resource added (bincmp.rc)
New in BinCmp 2.5 Beta (Nov 5, 2014)
- aborting by Ctrl+C and Ctrl+Break (+return code 13)
- some refactoring, time-measuring abilities (for development purposes)
- BinaryFilePatcher::parsePatchFile has been rewritten
- small changes in built-in help
- x64 platform added to the project files
New in BinCmp 2.4 Beta (Nov 5, 2014)
- some refactoring
- new return codes 107 and 207
New in BinCmp 2.3.3 Beta (Nov 5, 2014)
- now file (path)names are shown with the last write time
- now system's WideChar-To-MultiByte string conversion is used
- for Unicode file (path)names
New in BinCmp 2.3.2 Beta (Oct 14, 2013)
- small internal changes
- some more information about the patch mode:
- The Patch Mode of BinCmp assumes just one thing: it modifies existing_ bytes of a file. Thus it does not insert, append or delete any byte - i.e. does not perform any operation that changes the size of the file.
- The easiest way to produce a Patch File is to run BinCmp against two files to be compared - and the resulting output will be the Patch File. E.g. bincmp "FileName1" "FileName2" >PatchFile.txt
- Then, when BinCmp will process this Path File, it will take into account just those lines that contain the three values of ": ". Everything else will be skipped.
New in BinCmp 2.3.1 Beta (May 16, 2013)
- fixed: -diffs=0 did not work as expected
New in BinCmp 2.3 Beta (May 16, 2013)
- fixed: FileReader::readFile() might fail because it did not check the return value of ReadFile() and relied on GetLastError() only now patch file accepts lines with and without colon
- HEX file offset> equals to HEX file offset>:
New in BinCmp 2.2 Beta (May 16, 2013)
- patch mode: "-patch patch_file"
- the patch file format is the same as bincmp's comparison output: HEX file offset>:
- Such line has the following meaning: if existing value at offset HEX file offset> is equal to , this value will be
- replaced with . Otherwise the existing value will not be replaced. So, this is a conditional replacement.
- Example:
- 000010A1: 00 0B ; if byte at offset 10A1 is 00, replace it with 0B
- For unconditional replacement, use HEX file offset>: ?
- It will replace any existing value at offset with HEX new byte>.
- Example:
- 00002F70: ? AA ; replace any byte at offset 2F70 with AA Finally, ";" or "#" at the beginning of line is a comment.
- if file could not be opened with FILE_SHARE_READ sharing mode, bincmp retries with (FILE_SHARE_READ | FILE_SHARE_WRITE)
New in BinCmp 2.0.1 Beta (Mar 8, 2012)
- left and right file may have the same path but different offsets
- (for example, to compare first 10 bytes with the next 10 bytes of
- the same file, you can specify:
- bincmp some_file some_file -bytes=10 -offs2=10