Sujet : Re: Dimdows Decay Syndrome Continues
De : nospam (at) *nospam* needed.invalid (Paul)
Groupes : comp.os.linux.advocacy alt.comp.os.windows-11Date : 09. Feb 2025, 03:06:33
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vo92j9$ab32$1@dont-email.me>
References : 1 2 3 4
User-Agent : Ratcatcher/2.0.0.25 (Windows/20130802)
On Sat, 2/8/2025 3:12 PM, Andy Burns wrote:
Paul wrote:
when I asked it about
the NTFS file system, rather than answer the question, it told
me to "get a hex editor and figure it out for yourself". Now,
isn't that why we invented AI ??? So... helpful. I would not
have thought of that, using my hex editor and reverse engineering
NTFS. I suppose the next answer will be "why don't you drive
to the Public Library and look that up, pal?".
You could buy the Custer book, but it doesn't cover the newer features such as reparse points or the altered permission inheritance ...
openspecs-windows_protocols-ms-fscc.pdf
IO_REPARSE_TAG_WOF 0x80000017
Used by the Windows Overlay filter, for either WIMBoot
or single-file compression. Server-side interpretation
only, not meaningful over the wire.
IO_REPARSE_TAG_ONEDRIVE 0x80000021 Not used.
I suspect even the Microsoft (derived) documentation
isn't up to date. It's like their WIM spec :-)
The basic idea, is they'll tease you with the value
of the tag, but the rest of it you have to reverse-engineer.
Paul