Receiving IrpSp->Parameters.SetFile.FileObject as NULL in Win2k3

NTFSD
1

Hi,
I have a file system that was written for NT. It
works on win2k as well as win2k3. The problem that I
am notice is when I share a folder(with full access)
that is in this file system. I mapped it as a drive
letter on another machine.
When I try to rename a file thru the share I receive
IrpSp->Parameters.SetFile.FileObject == NULL.
I tried it with Win2k & I am getting the correct
FileObject.
Modified Filemon & made it to print out
IrpSp->Parameters.SetFile.FileObject. I received the
correct fileobject in win2k3 & win2k in the filemon
log. But when the same Irp was sent down my file
system received this as NULL. I tried mapping the
drive on the same machine in which my FS was running
with filemon & observed the same result.
Is this due to some change in LanmanRedirector or
server in win2k3?
Any feed backs or suggetions will be appreciated.
Thanks.

Thanks & Regards,
Arun.

Do you Yahoo!?
Yahoo! Hotjobs: Enter the “Signing Bonus” Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

2

If you are renaming file within the same directory there is nothing wrong
with IrpSp->Parameters.SetFile.FileObject being NULL.
Your file system should handle this case.

Alexei.

“Arun Joseph” wrote in message news:xxxxx@ntfsd…
> Hi,
> I have a file system that was written for NT. It
> works on win2k as well as win2k3. The problem that I
> am notice is when I share a folder(with full access)
> that is in this file system. I mapped it as a drive
> letter on another machine.
> When I try to rename a file thru the share I receive
> IrpSp->Parameters.SetFile.FileObject == NULL.
> I tried it with Win2k & I am getting the correct
> FileObject.
> Modified Filemon & made it to print out
> IrpSp->Parameters.SetFile.FileObject. I received the
> correct fileobject in win2k3 & win2k in the filemon
> log. But when the same Irp was sent down my file
> system received this as NULL. I tried mapping the
> drive on the same machine in which my FS was running
> with filemon & observed the same result.
> Is this due to some change in LanmanRedirector or
> server in win2k3?
> Any feed backs or suggetions will be appreciated.
> Thanks.
>
> Thanks & Regards,
> Arun.
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the “Signing Bonus” Sweepstakes
> http://hotjobs.sweepstakes.yahoo.com/signingbonus
>

3

> If you are renaming file within the same directory there is nothing wrong

with IrpSp->Parameters.SetFile.FileObject being NULL.
Your file system should handle this case.

Sorry for the newbie question, but what will be the
new file name in this case ?

L.

4

The parent directory name of the new file name is the same as the parent
directory name of the old file name. The new file name (just the part after
the parent directory) is in FILE_RENAME_INFORMATION.FileName.
FILE_RENAME_INFORMATION is to be found at Irp->AssociatedIrp.SystemBuffer.
So … if the old name c:\adir\afile1 and FILE_RENAME_INFORMATION.FileName
contains afile2 then the new file name is C:\adir\afile2

See the nt insider article at http://www.osr.com/ntinsider/1997/rename.htm
for more information about renames.

Shares on a W2K3 server were the first time I saw
IrpSp->Parameters.SetFile.FileObject beingNULL also.

“Ladislav Zezula” wrote in message news:xxxxx@ntfsd…
> > If you are renaming file within the same directory there is nothing
wrong
> > with IrpSp->Parameters.SetFile.FileObject being NULL.
> > Your file system should handle this case.
>
> Sorry for the newbie question, but what will be the
> new file name in this case ?
>
> L.
>
>

5

Thanks Lyndon J Clarke & Alexei for the help.

Arun.

Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/