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

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

Re: Determining correct rename target path for fully- qualified rename case

David_J._CraigDavid_J._Craig Member Posts: 1,885
Because the pathname is for the file system. What the file system does to
the name is its choice. As a filter, you cannot modify it, before the file
system sees it - if you want that name to go through. If you are
redirecting, then you just have to make sure the name reflects the correct
target and maybe do a reparse.

----- Original Message -----
From: "Ted Hess" <xxxxx@livevault.com>
To: "File Systems Developers" <xxxxx@lists.osr.com>
Sent: Friday, January 17, 2003 4:48 PM
Subject: [ntfsd] Re: Determining correct rename target path for fully-
qualified rename case


> Well then how come the FS can use it?
>
> /ted
>
> -----Original Message-----
> From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
> Sent: Friday, January 17, 2003 4:04 PM
> To: File Systems Developers
> Subject: [ntfsd] Re: Determining correct rename target path for
> fully-qualified rename case
>
>
> > So my question is: Is it legal to use the FileObject.FileName field
> in a
>
> No. FileObject->FileName is valid only in CREATE path down, it can be
> invalid even in CREATE completion.
>
> Max
>
>
>
> ---
> You are currently subscribed to ntfsd as: xxxxx@livevault.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> ---
> You are currently subscribed to ntfsd as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
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 25 Feb 2019 OSR Seminar Space
Developing Minifilters 8 April 2019 OSR Seminar Space