× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Responding to my own post:

On Thu, May 29, 2014 at 12:11 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

[TechRepublic:]
"The major difference is in the resolution time, which can vary from
10 milliseconds for 'create time' on FAT-formatted files to one hour
for 'access time' on NTFS-formatted files."

This is an amazingly awkward and uninformative statement. What about
the "access time" on FAT or the "create time" on NTFS, or the "change
time" on either? In any case, the one hour seems kind of
preposterous. Even the screen shots in that very article strongly
suggest that the access time has resolution no worse than one second.

I think the resolution on all three times are the same for any given
filesystem. I could be wrong, but it just seems like a ridiculous
idea to make some timestamps have finer resolution than others.

Well, according to the Python documentation (regarding its wrapper for
the "stat" system call), Windows FAT filesystems have 2-second
resolution on modification time and 1-day (yes, day!) resolution on
access time.

So I was definitely wrong. I stand by the assessment that this is
ridiculous, and I am still not completely confident about the
correctness of the TechRepublic article. However, here's a link from
Microsoft, which presumably is as authoritative as we have easy access
to:

http://msdn.microsoft.com/en-us/library/windows/desktop/ms724290%28v=vs.85%29.aspx

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.