Hello,
I think I had a similar problem with my network redirector under Windows
2000.
I discovered that the function IRP_MJ_QUERY_INFORMATION failed with
INVALID_PARAMETER
when requested for FileNameInformation if FileInformationClass is:
FileAttributeTagInformation
The problem was that, since my driver does not support this class, my
dispatch
routine would not check for this case and return the status of
STATUS_INVALID_INFO_CLASS.
Apparently, Windows 2000 does not like this. So, the solution is for the
dispatch routine to check for
this case and, if your driver does not support it, return with the status
STATUS_NOT_IMPLEMENTED.
The bottomline is that if your driver does not support an information class,
return the status of
STATUS_NOT_IMPLEMENTED instead of STATUS_INVALID_INFO_CLASS.
I believe under Windows NT, either this information class is never used or
its ok to return the status
of STATUS_INVALID_INFO_CLASS. by default.
I am not sure though if your problem is similar to this one.
Hope this helps.
Qasim
-----Original Message-----
From: I?aki Castillo [mailto:xxxxx@pandasoftware.es]
Sent: Monday, May 22, 2000 7:59 AM
To: File Systems Developers
Subject: [ntfsd] W2000: IRP_MJ_QUERY_INFORMATION and FileNameInformation
Hi,
I have noticed that under W2000 function IRP_MJ_QUERY_INFORMATION fails
sometimes when requested for FileNameInformation.
It fails with INVALID_PARAMETER when the target for the request is the
LanMan
redirector. I have checked thousand of times all parameters but cannot
discover the
problem.
Anyone knows about some difference in this function under W2000 with regards
to NT4.
Please, note that for local file systems under W2000 it works okay.(Under
NT4 is works in all cases)
Thanks.
Inaki.
You are currently subscribed to ntfsd as: xxxxx@Attachmate.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)