Is type of QueryDirectory.FileName a PSTRING?

NTFSD
1

Hi.

Is type of QueryDirectory.FileName a PSTRING?

I use the Parameters.QueryDirectory.FileName in IRP_MN_QUERY_DIRECTORY
IRP.
I saw that the type of parameter is PUNICODE_STRING in fact.
If I set the QueryDirectory.FileName to PUNICODE_STRING, it well work.
But, if I set the QueryDirectory.FileName to PSTRING, it not work.

Also, I saw that the QueryDirectory.FileName be defined as PSTRING in
ntifs.h (NT, 2000, and XP IFS Kit).

Is the ntifs.h incorrect or not?

Thanks,
mamiya

2

Hi.

Is type of QueryDirectory.FileName a PSTRING?

I use the Parameters.QueryDirectory.FileName in IRP_MN_QUERY_DIRECTORY IRP.
I saw that the type of parameter is PUNICODE_STRING in fact.
If I set the QueryDirectory.FileName to PUNICODE_STRING, it well work.
But, if I set the QueryDirectory.FileName to PSTRING, it not work.

Also, I saw that the QueryDirectory.FileName be defined as PSTRING in
ntifs.h (NT, 2000, and XP IFS Kit).

Is the ntifs.h incorrect or not?

Thanks,
mamiya

3

Isn’t it clear from your words?
PSTRING is NOT PUNICODE_STRING - it is an ANSI_STRING.
So, FileName is of type UNICODE_STRING. It DOES seem that the ntifs.h
is incorrect - the FastFat source references it as a UNICODE_STRING.

Regards, Dejan.

mamiya wrote:

Hi.

Is type of QueryDirectory.FileName a PSTRING?

I use the Parameters.QueryDirectory.FileName in IRP_MN_QUERY_DIRECTORY
IRP.
I saw that the type of parameter is PUNICODE_STRING in fact.
If I set the QueryDirectory.FileName to PUNICODE_STRING, it well work.
But, if I set the QueryDirectory.FileName to PSTRING, it not work.

Also, I saw that the QueryDirectory.FileName be defined as PSTRING in
ntifs.h (NT, 2000, and XP IFS Kit).

Is the ntifs.h incorrect or not?

Thanks,
mamiya

You are currently subscribed to ntfsd as: xxxxx@alfasp.com
To unsubscribe send a blank email to %%email.unsub%%

–
Kind regards, Dejan M. www.alfasp.com
E-mail: xxxxx@alfasp.com ICQ#: 56570367
Alfa File Monitor - File monitoring library for Win32 developers.
Alfa File Protector - File protection and hiding library for Win32
developers.

4

Thank you for answer.

Dejan wrote:

PSTRING is NOT PUNICODE_STRING - it is an ANSI_STRING.

I think so, too.

So, FileName is of type UNICODE_STRING.
It DOES seem that the ntifs.h is incorrect -
the FastFat source references it as a UNICODE_STRING.

If it is so, I have a question.

Why wasn’t ntifs.h corrected until XP IFS Kit release?
Or ntifs.h is correct, so does a case of “FileName is ANSI_STRING” exist?

Because FastFat is so, they may be imaginary fears.

5

QueryDirectory.FileName is actually a PUNICODE_STRING and not an
ANSI_STRING even though the type is PSTRING in NTIFS.H. All the file
systems treat this field as a PUNICODE_STRING.

I’m not sure of the exact history, but I noticed this a few months back
and NTIFS.H is fixed for the .NET server version of the IFS Kit.
Unfortunately, they wouldn’t let me fix it for the XP SP1 version of the
IFS Kit, so the type is still incorrect there, but the data is in
PUNICODE_STRING form.

Molly Brown
Microsoft Corporation

This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: mamiya [mailto:xxxxx@yisd.dnp.co.jp]
Sent: Thursday, August 29, 2002 5:32 AM
To: File Systems Developers
Subject: [ntfsd] Re: Is type of QueryDirectory.FileName a PSTRING?

Thank you for answer.

Dejan wrote:

PSTRING is NOT PUNICODE_STRING - it is an ANSI_STRING.

I think so, too.

So, FileName is of type UNICODE_STRING.
It DOES seem that the ntifs.h is incorrect -
the FastFat source references it as a UNICODE_STRING.

If it is so, I have a question.

Why wasn’t ntifs.h corrected until XP IFS Kit release?
Or ntifs.h is correct, so does a case of “FileName is ANSI_STRING”
exist?

Because FastFat is so, they may be imaginary fears.

You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to %%email.unsub%%

6

Molly Brown wrote:

I’m not sure of the exact history, but I noticed this a few months back
and NTIFS.H is fixed for the .NET server version of the IFS Kit.
Unfortunately, they wouldn’t let me fix it for the XP SP1 version of the
IFS Kit, so the type is still incorrect there, but the data is in
PUNICODE_STRING form.

I see.
Your advice gave certain guideline to me.

I will be expecting fixed version release of IFS Kit.