Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Sept/Oct 2019 Issue of The NT Insider available


Download PDF here: http://insider.osr.com/2019/ntinsider_2019_01.pdf

It’s a particularly BIG issue, too: 40 pages of technical goodness, ranging from WDF to Minifilters. Check it out.
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

RE: Directory listings with pattern (was RE: How to q uery for a long filename using IRP_M

OSR_Community_UserOSR_Community_User Member Posts: 110,217
You caught me, Dan. Absolutely right. Zero or more. I'm assuming there is
a brilliant discussion of this somewhere in the IFS Kit documentation, of
course (right Diane? ;-) )

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com


-----Original Message-----
From: Dan Kyler [mailto:xxxxx@privtek.com]
Sent: Tuesday, November 19, 2002 6:48 PM
To: File Systems Developers
Subject: [ntfsd] RE: Directory listings with pattern (was RE: How to query
for a long filename using IRP_MJ_DIRECTO RY_CONTROL/IRP_MN_QUERY_DIR
ECTORY?)

Hi Tony,

> * = "match one or more characters"

I believe that should read "zero or more".

- Dan.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Tuesday, November 19, 2002 12:47 PM
To: File Systems Developers
Subject: [ntfsd] RE: Directory listings with pattern (was RE: How to
query for a long filename using IRP_MJ_DIRECTO
RY_CONTROL/IRP_MN_QUERY_DIR ECTORY?)


There are five wildcard characters in the Windows pattern matching
syntax (that is the syntax implemented by FsRtlIsNameInExpression, that
venerable and nearly inscrutable function.)

* = "match one or more characters"
? = "match one character"
< = "match one or more characters using MS-DOS semantics"
> = "match one character using MS-DOS semantics"
" = "match dot using MS-DOS semantics"

Thus, the last three are for MS-DOS compatibility, which restricts the
character set that can match. For example, spaces are allowed in MS-DOS
names, but not before or after the dot. These MS-DOS patterns match
those semantics.

For building your own strings, I highly recommend sticking with the
Windows semantics, not the MS-DOS semantics.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com


-----Original Message-----
From: Tobias [mailto:xxxxx@linkwave.org]
Sent: Tuesday, November 19, 2002 12:14 PM
To: File Systems Developers
Subject: [ntfsd] Directory listings with pattern (was RE: How to query
for a long filename using IRP_MJ_DIRECTO
RY_CONTROL/IRP_MN_QUERY_DIRECTORY?)

Don't wanna bother, but for (3) I have some additional questions.

The format of "*.doc" is really easy to use (especially when building
directory information buffers), but how about those special wildcards
like "\"" or "<" ( C notation, it's hard to quote a " :) ) ? Is there an
overview of all options for directory wildcards and their meaning
somewhere? Or can one simply use * for any illegal non-zero character?

Regards & TIA,
Tobias


----- Original Message -----
From: "Tony Mason" <xxxxx@osr.com>
To: "File Systems Developers" <xxxxx@lists.osr.com>
Sent: Tuesday, November 19, 2002 2:59 PM
Subject: [ntfsd] RE: How to query for a long filename using
IRP_MJ_DIRECTO RY_CONTROL/IRP_MN_QUERY_DIRECTORY?

> (3) This can either be a file name you wish to find (not a path, just
> a
> filename) or a regular expression (e.g., "*.doc" to find all of the
DOC
> files within the directory.) That name will be used to match the
short OR
> long file name.



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

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



---
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to %%email.unsub%%
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Writing WDF Drivers 21 Oct 2019 OSR Seminar Space & ONLINE
Internals & Software Drivers 18 Nov 2019 Dulles, VA
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 27 Apr 2020 OSR Seminar Space & ONLINE