I am using filespy for monitoring the logs generated through it. I noticed
that with XP, filespy attaches itself with all volumes
,\device\lanmanredirector etc intially when filespy starts execution. But i
found it does not attach itself with any volumes when used in windows 2000.
Is my observation correct . Or is there configuration setting by which we
can attach filespy with all the volumes, lanmanredirector etc at the start
of filespy execution.
Thanks
Rohit
Go read the Filespy source, you will see that between 2000 and XP the
approach for detecting and attaching to volumes changed.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Rohit” wrote in message news:xxxxx@ntfsd…
I am using filespy for monitoring the logs generated through it. I noticed
that with XP, filespy attaches itself with all volumes
,\device\lanmanredirector etc intially when filespy starts execution. But i
found it does not attach itself with any volumes when used in windows 2000.
Is my observation correct . Or is there configuration setting by which we
can attach filespy with all the volumes, lanmanredirector etc at the start
of filespy execution.
Thanks
Rohit
i have seen filespy code and i found that it is not registering the call
back IoRegisterFsRegistrationChange in case of windows 2000. so i have
commented out that part and register callback for 2000 and also change the
start type of driver to boot in registry. Then i found that this driver
started at boot time and attaches itself with /cdfs, lanmanredirector and
fat. but still it is not attaching itself with ntfs. whats the reason
behind that. am i going in wrong direction. Basically i want to attach my
driver with all the file systems.
Regards
Rohit
Is NTFS the boot file system?
What’s your load ordering? If NTFS has already registered (and is the
boot FS) then you won’t get a call.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
Looking forward to seeing you at the next OSR File Systems class in
Boston, MA April 18-21, 2006 (note new date - MS scheduled plugfest the
same week again.)
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Rohit
Sent: Saturday, March 25, 2006 4:19 AM
To: ntfsd redirect
Subject: Re:[ntfsd] Re: attaching Filespy device object with volume
under windows 2000
i have seen filespy code and i found that it is not registering the call
back IoRegisterFsRegistrationChange in case of windows 2000. so i have
commented out that part and register callback for 2000 and also change
the start type of driver to boot in registry. Then i found that this
driver started at boot time and attaches itself with /cdfs,
lanmanredirector and fat. but still it is not attaching itself with
ntfs. whats the reason behind that. am i going in wrong direction.
Basically i want to attach my driver with all the file systems.
Regards
Rohit
— Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17 You are currently subscribed
to ntfsd as: unknown lmsubst tag argument: ‘’ To unsubscribe send a
blank email to xxxxx@lists.osr.com
I am guessing that you have registered your version of filespy in
wrong load order group, so filespy is loaded after NTFS.
L.
Thanks tony and ladik for reply.
I have changed the group load order to filter and now filespy is loaded
before ntfs and filespy is getting the notification for ntfs file system as
an active file system…
Regards
Rohit
Make it Boot start and belonging to a “filter” group.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: “Rohit”
To: “Windows File Systems Devs Interest List”
Sent: Saturday, March 25, 2006 1:18 PM
Subject: Re:[ntfsd] Re: attaching Filespy device object with volume under
windows 2000
i have seen filespy code and i found that it is not registering the call
back IoRegisterFsRegistrationChange in case of windows 2000. so i have
commented out that part and register callback for 2000 and also change the
start type of driver to boot in registry. Then i found that this driver
started at boot time and attaches itself with /cdfs, lanmanredirector and
fat. but still it is not attaching itself with ntfs. whats the reason
behind that. am i going in wrong direction. Basically i want to attach my
driver with all the file systems.
Regards
Rohit
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com