> points. You have not seen the STATUS_REPARSE because it was handled at a
stack location below the one where filemon was installed in the stack.
But if that was the case, I would expect to see create request with
“C:\FileTest.exe” (which is the link name) and not
“C:\Tools32\FileTest.exe”, which is the true name of the EXE.
L.
Filemon queries the file name in post create.
t.
On Thu, 29 Mar 2007, Ladislav Zezula wrote:
> points. You have not seen the STATUS_REPARSE because it was handled at a
> stack location below the one where filemon was installed in the stack.But if that was the case, I would expect to see create request with
“C:\FileTest.exe” (which is the link name) and not
“C:\Tools32\FileTest.exe”, which is the true name of the EXE.L.
Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@openmars.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
This was my question; where is the filename constructed? From the file
object in pre-op, or query of the file system in post-op, or …
“Tracy Camp” wrote in message news:xxxxx@ntfsd…
> Filemon queries the file name in post create.
>
> t.
>
> On Thu, 29 Mar 2007, Ladislav Zezula wrote:
>
>>> points. You have not seen the STATUS_REPARSE because it was handled at
>>> a
>>> stack location below the one where filemon was installed in the stack.
>>
>> But if that was the case, I would expect to see create request with
>> “C:\FileTest.exe” (which is the link name) and not
>> “C:\Tools32\FileTest.exe”, which is the true name of the EXE.
>>
>> L.
>>
>>
>>
>> —
>> Questions? First check the IFS FAQ at
>> https://www.osronline.com/article.cfm?id=17
>>
>> You are currently subscribed to ntfsd as: xxxxx@openmars.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>