What's new in DupeMerge 1.07
Oct 3, 2013
- Dead Junctions to a different drive could lead to not detecting hardlinks during all operations. Very Nasty, but no dataloss caused
New in DupeMerge 1.06 (Oct 3, 2013)
- Introduced a sanity check for broken NTFS implementations
- When hardlinking a tupel of equal files, the tupels common date is the date of the oldest file of the tupel
- The statistics is printed after the detailed log and not before
New in DupeMerge 1.05 (Oct 3, 2013)
- Fixed a crash during cleanup at the very end when all was correctly done
New in DupeMerge 1.04 (Oct 3, 2013)
- Fixed a crash when files were larger than 16gb
New in DupeMerge 1.03 (Oct 3, 2013)
- The number of new dupegroups was reported non deterministic when huge amounts of files were scanned, but always calculated correct.
- The --output option didn't redirect output properly.
- Improved summary statistics.
- Error message is printed out if the 1024 hardlink limit per file is exceeded.
New in DupeMerge 1.0 (Oct 3, 2013)
- In rare situations not all dupes of a group were merged into one group but in e.g two groups.
- Fast file enumeration is now the default.
- Little tweaks here and there, but in general a long journey has ended and this version qualifies for a 1.0 release
New in DupeMerge 0.999 (Oct 22, 2008)
- Dupemerge preserves the timestamps of original files when it merges the files via hardlinks.
New in DupeMerge 0.998 (Jun 27, 2008)
- Dupemerge respects the NTFS limit of having not more than 1023 hardlink on one file
- Binaries are now availabke for 32bit and 64bit, because compiler for this tool changed to Vs2005