If you find the problem is the rename and returning
STATUS_NOT_SAME_DEVICE does not convert it to a copy/delete, then yes,
you’ll need to implement it yourself as a copy/delete. That status code
will indicate to the calling application that it should perform a
copy/delete but not all applications will do that.
Pete
–
Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295
------ Original Message ------
From: xxxxx@yahoo.com
To: “Windows File Systems Devs Interest List”
Sent: 8/6/2017 1:07:10 AM
Subject: RE:[ntfsd] Overwrite Issue when reparsing MS word to a
different volume
>>NTFS does not support cross-volume renames
>
>Does this mean my solution will not work on NTFS even if I get it to
>the point which the rename is processed?
>
>Is there any work around? May I create the target and write the content
>then delete the source to simulate a rename in pre/post set information
>for a rename operation?
>
>—
>NTFSD is sponsored by OSR
>
>
>MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>software drivers!
>Details at http:
>
>To unsubscribe, visit the List Server section of OSR Online at
>http:</http:></http:>