> >> Meanwhile I've puzzled out what caused my problem. > >> w32-get-true-file-attributes now defaults to t! > > > > Interesting. So why is the default now t? > > As far as I can see from a little bit reading it achieves to things: > > - Accurate hard link count (how useful is this?) > - Accurate file attributes (something about avoiding cache on heavily > loaded machines)
That says what it does, but not why the default value was changed.