Yes, I know - this is quite a challenge!
This feature of NTFS (ADS) has been around for quite some time without anybody (except M$) making much use of it. But I wouldn't bet on this staying that way.
In fact I am using it myself to attach comments to files (and folder) that do not get lost when I copy or move them (to other NTFS partitions).
But if you really come to think of it, a binary comparison is probably what most people would want to use to ensure that two file are identical. They would then take it for granted that these files are the same and possibly delete one of them. Fact is, they have only compared the file's default stream, and may be deleting some important information in the ADS.
Yes - you are warned by the OS, if you move the file to a FAT32 partition - but not if you simply delete it.
AFAIK there is currently no comparison tool to compare ADS along with the default stream, or even to warn the user that a file has ADS attached!
This is not a good situation. I would like to see BC -as the IMO leading software for that purpose- tackle that problem. Or is this on the developers' agenda already?
This feature of NTFS (ADS) has been around for quite some time without anybody (except M$) making much use of it. But I wouldn't bet on this staying that way.
In fact I am using it myself to attach comments to files (and folder) that do not get lost when I copy or move them (to other NTFS partitions).
But if you really come to think of it, a binary comparison is probably what most people would want to use to ensure that two file are identical. They would then take it for granted that these files are the same and possibly delete one of them. Fact is, they have only compared the file's default stream, and may be deleting some important information in the ADS.
Yes - you are warned by the OS, if you move the file to a FAT32 partition - but not if you simply delete it.
AFAIK there is currently no comparison tool to compare ADS along with the default stream, or even to warn the user that a file has ADS attached!
This is not a good situation. I would like to see BC -as the IMO leading software for that purpose- tackle that problem. Or is this on the developers' agenda already?
Comment