4 ms·
some history: this was introduced with XP SP2 as part of the windows security push. was a clever way to track the information without touching the binary data d
by ryanburk 10y ago
some history: this was introduced with XP SP2 as part of the windows security push. was a clever way to track the information without touching the binary data directly and supporting it in IE meant the majority of customers saw the benefit right away. and since most people (in windows) don't move files across file systems.
- ams6110 10y agoPeople in windows often move files across file systems: between the internal hard drive (generally NTFS) to external USB drives (often FAT32, or exFAT)
- GirlsCanCode 10y agoExactly! It's amazing how unaware Mac zealots are of other operating systems. They may learn something if they'd shut up and listen.
- Mikhail_Edoshin 10y agoWhen this happens and the file has alternate streams you get a warning that some of the file's attributes cannot be copied.
- banana_giraffe 10y agoI've not seen that warning before. I just tested on a file I downloaded, which had the 'Zone.Identifier' stream. Using Explorer, I copied it to a FAT32 volume, then back to my NTFS drive. Sure enough, it lost the 'Zone.Identifier' stream, and there was no warning when I opened it. This is on a fairly normal Windows 10 installation. YMMV on different versions, of course.
- Mikhail_Edoshin 10y agoI saw this warning on files copied from Mac OS X (when I transferred them further to a FAT32 filesystem). Maybe it depends on which stream it is. (Windows 8 Pro.)