In the Windows NT/2K environment, you will have
to extract each component “token” of the path
yourself - given the entire path name.
To do so, you may wish to utilize FSRTL functions
such as the following:
(a) FsRtlDissectName()
(b) FsRtlDoesNameContainWildCards()
(c) FsRtlIsNameInExpression()
(d) FsRtlAreNamesEqual()
and others …
- rajeev
Rajeev Nagar
(408) 246 3623 x11
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of John S. Yates, Jr
Sent: Friday, April 21, 2000 9:40 PM
To: File Systems Developers
Subject: [ntfsd] path parsing
I am at the begining of trying to port a W9x FSD to NT.
At this point I am just trying to match up features and
functionality between the two environements.
This FSD has somewhat unusual directory semantics. Under
W9x the path parsing and name matching features are a big
help since I have to work with individual path components.
I assume that NT has similar primitives but I am having
trouble finding them…
TIA
/john
John Yates
EverFile
40 Pine Street
Needham, MA 02492
781 400-1015
You are currently subscribed to ntfsd as: xxxxx@ntcoresvcs.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)