what's the total number of "o"s in:
q: why does file copy from ntfs to fat32 change a file's modified date? when copying a file from an ntfs partition to a fat32 device, the new file's modified date is sometimes changed by 1 or 2 seconds.  why does this happen?
this became apparent in a file syncronization program i have that compares mod dates and copies newer files over the older, and in this case can never catch up since the mod date is a moving target.  i tried doing a drag-n-drop copy within windows explorer and it did the same thing.

a: this is because fat32 has 2 second resolution for last write times.
in other words, what you're seeing is a limitation of the file system: it can't store last modified times accurately to the second.
your synchronisation program is going to have to allow a window of a few seconds when comparing dates or use another method to work out which files to copy.  you could checksum the files to compare the contents; if you don't have too many files this can be reasonably fast.

a: i think the only differences between the original fat and fat32 was the long file name support and the size of the fat pointers (up from 16 bits to 32) to allow smaller clusters on large disks.
i don't think they rejigged the directory entry formats which have had a 2-second resolution since the very earliest days of dos. this was to save space on the disk, not so important now, but very important back then.

a: the other reason is because all ntfs permissions are removed.  i've noticed all user profile permissions in ntfs are not on files that have been copied to fat32.

user
The total number of "o"s in that passage is one hundred and nine.
assistant