Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1236 Align with NTFS capabilities

open
nobody
None
5
2013-09-18
2013-09-18
Mike
No

WinMerge appears outdated when used in combination with tools like RoboCopy, as it often can't compare the results. For example, the user copies a folder from an old NTFS disk to a new NTFS disk:

RoboCopy "A:\example" "B:\example" /E /DCOPY:T /IS

After this, there is an expectation that WinMerge can compare the same folders, but this is not the case. This can be for reasons like:

  • "Extra-long" (>256) paths and file names
  • File names like " " (space) or "AUX.info"

These are perfectly valid for NTFS (limitations apply for File Explorer, not for NTFS), and tend to accumulate over a lifetime. RoboCopy copies them fine. They are on the disk. Shouldn't WinMerge be able to compare them?

Currently, WinMerge lists such files with a red error symbol and an empty Comparison result field (although it shows the correct Left Date and Right date).

Discussion

  • Mike
    Mike
    2013-09-18

    The attachment illustrates the cited sample error cases.

     
    Attachments