OSRLogo
OSRLogoOSRLogoOSRLogo x OSR Custom Development Services
OSRLogo
x

Everything Windows Driver Development

x
x
x
GoToHomePage xLoginx
 
 

    Thu, 14 Mar 2019     118020 members

   Login
   Join


 
 
Contents
  Online Dump Analyzer
OSR Dev Blog
The NT Insider
The Basics
File Systems
Downloads
ListServer / Forum
  Express Links
  · The NT Insider Digital Edition - May-June 2016 Now Available!
  · Windows 8.1 Update: VS Express Now Supported
  · HCK Client install on Windows N versions
  · There's a WDFSTRING?
  · When CAN You Call WdfIoQueueP...ously

Windows XP® IFS Kit Errata

It's confirmed. Microsoft inadvertently left out IOCTL_REDIR_QUERY_PATH from the Windows XP IFS Kit.


This IOCTL is needed by redirectors that support the Universal Naming Convention (you know - resolving names with a leading double backslash.) The definition has not changed from the Windows 2000 IFS Kit, so it can be used by simply using the older definition. Word is that Microsoft will fix this in the .NET version of the IFS Kit.


For your reference, the old definition is:

#define IOCTL_REDIR_QUERY_PATH CTL_CODE(FILE_DEVICE_NETWORK_FILE_SYSTEM,
99, METHOD_NEITHER, FILE_ANY_ACCESS)

The two data structures that go along with this IOCTL are:

typedef struct _QUERY_PATH_REQUEST { ULONG PathNameLength; PIO_SECURITY_CONTEXT SecurityContext; WCHAR FilePathName[1];
} QUERY_PATH_REQUEST, *PQUERY_PATH_REQUEST;

typedef struct _QUERY_PATH_RESPONSE { ULONG LengthAccepted;
} QUERY_PATH_RESPONSE, *PQUERY_PATH_RESPONSE;

Related Articles
Win2K IFS Kit Bug Fix
Want the XP IFS Kit? You'll have to ORDER it!

User Comments
Rate this article and give us feedback. Do you find anything missing? Share your opinion with the community!
Post Your Comment

Post Your Comments.
Print this article.
Email this article.
bottom nav links