Comments on: HowTo: Correctly read reparse data in Vista

By: Neil Haven

Neil Haven — Wed, 28 May 2008 21:13:07 +0000

Thanks, Jochen! Anyone trying to implement this, or something like it, should be aware of a few other little gotchas in the Microsoft API. I’ve detailed them at http://brainrack.wordpress.com/2008/05/28/broken-and-ill-documented-api-for-windows-mount-points/

By: Broken and Ill-Documented API for Windows Mount-Points « Brainrack Aborning - Developing a Search Engine

Wed, 28 May 2008 20:25:03 +0000

[…] http://blog.kalmbach-software.de/2008/02/28/howto-correctly-read-reparse-data-in-vista/ […]

By: Jochen Kalmbach’s Blog » Blog Archive » Mal wieder ein Doku Fehler in der MSDN

Fri, 07 Mar 2008 18:37:41 +0000

[…] einen Kommentar ist mir ein Fehler in meinem Beispiel zum Auslesen der Reparse-Daten (Mount-Point, Junctions) […]

By: jkalmbach

jkalmbach — Fri, 07 Mar 2008 18:25:08 +0000

Ok, I found the correct definition in the ntfsi.h file from the DDK and corrected the example; also added support for SymLink and Junctions
Thanks again!

By: jkalmbach

jkalmbach — Fri, 07 Mar 2008 17:33:13 +0000

Hi Sergey,

1. The “correct” (or MS) way is to use FILE_READ_EA; see my screencast about using APILogger-Shim:
http://blog.kalmbach-software.de/2008/03/06/screencast-api-logging-with-the-application-compatibility-layer/

2. I don’t understand; see documentation of REPARSE_DATA_BUFFER
http://msdn2.microsoft.com/en-us/library/ms791514.aspx

By: Sergey Vlasov

Sergey Vlasov — Fri, 07 Mar 2008 17:02:25 +0000

Two little remarks:
1. In my tests it works even without FILE_READ_EA, i.e. CreateFile(szMyFile, 0, …)
2. SymbolicLinkReparseBuffer definition misses “ULONG Flags;”. It should be
struct {
USHORT SubstituteNameOffset;
USHORT SubstituteNameLength;
USHORT PrintNameOffset;
USHORT PrintNameLength;
ULONG Flags;
WCHAR PathBuffer[1];
} SymbolicLinkReparseBuffer;

And you forgot to mention that extracting symbolic link info is left as exercise for the reader It can be tested on _T(”c:\\Users\\All Users”);