in reply to Re: Filesize (-s) is consistenly reporting too small of size in Win32
in thread Filesize (-s) is consistenly reporting too small of size in Win32

This is very unlikely to be anything to do with streams.

I don't think there is any way of obtaining a filesize that conflates the sizes of the different streams into a single number. For the most part streams have to treated as if they were entirely different files, whether you are reading them or querying information about them.

The only APIs that treat them as compound entities are the backup APIs, and they are all but inaccessible to most user code.

Despite all the OPs invective about hating windows, this is far more likely to be incompatibilities, or latency in catching, between the underlying Linux OS, the VMWare virtualisation and the hosted Windows code, than any inherent problem in Windows itself.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."
  • Comment on Re^2: Filesize (-s) is consistenly reporting too small of size in Win32