Hi,
I wonder if one of you gurus out there could help me. I have written a
filter driver which is originally based on filespy from the 3790 IFS kit. It
is intended for the filter to operate under Win2K, WinXP
and Win2K3. It all works fine under XP and 2K3 but I have problems under
WIN2K. The driver start type is set to 1 (SERVICE_SYSTEM_START). I see the
driver attaching to FAT, LanManRedirector and CDFS but not NTFS. All the
FsControlMountVolume requests I see going through for the NTFS volumes are
failing with code C000014f (Unrecognised file system) so I never attach to
them). I am sure the filter did originally work on these volumes. I also
have XP and 2K3 installed in different partitions. I am wondering if when I
booted the other systems, they updated the version of NTFS on there and this
is now causing problems ? It’s odd because once the system completes the
boot phase, all the volumes are visible in explorer. In case I had screwed
something up, I tried filespy and it has the same problems - it only
attaches to the FAT partitions.
So, if you guys have any thoughts, I would much appreciate to hear from you.
Kind Regards,
Trevor Heartfield.
OK, I’ve now set my filter to load at boot. It seems I do not get the
notification that NTFS is loading. I searched the archives and a couple of
other people had this problem but I haven’t seen anyone supply the answer.
“Trevor Heartfield” wrote in message
news:xxxxx@ntfsd…
> Hi,
> I wonder if one of you gurus out there could help me. I have written a
> filter driver which is originally based on filespy from the 3790 IFS kit.
> It is intended for the filter to operate under Win2K, WinXP
> and Win2K3. It all works fine under XP and 2K3 but I have problems under
> WIN2K. The driver start type is set to 1 (SERVICE_SYSTEM_START). I see the
> driver attaching to FAT, LanManRedirector and CDFS but not NTFS. All the
> FsControlMountVolume requests I see going through for the NTFS volumes are
> failing with code C000014f (Unrecognised file system) so I never attach to
> them). I am sure the filter did originally work on these volumes. I also
> have XP and 2K3 installed in different partitions. I am wondering if when
> I booted the other systems, they updated the version of NTFS on there and
> this is now causing problems ? It’s odd because once the system completes
> the boot phase, all the volumes are visible in explorer. In case I had
> screwed something up, I tried filespy and it has the same problems - it
> only attaches to the FAT partitions.
>
> So, if you guys have any thoughts, I would much appreciate to hear from
> you.
>
> Kind Regards,
> Trevor Heartfield.
>
>
>
On Win2K, if your filter loads AFTER the file system, it will not learn
of its loading. On XP and W2K3 the load is reported to your filter even
though you have loaded after the file system (assuming you are using
IoRegisterFsRegistrationChangeNotification).
Even though you might be loading at boot time, you are still starting
too late in the sequence. Make sure your load group is BEFORE the boot
file system group.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Trevor Heartfield
Sent: Tuesday, November 09, 2004 1:59 PM
To: ntfsd redirect
Subject: Re:[ntfsd] Filter failing to attach to NTFS volumes under Win2K
OK, I’ve now set my filter to load at boot. It seems I do not get the
notification that NTFS is loading. I searched the archives and a couple
of
other people had this problem but I haven’t seen anyone supply the
answer.
“Trevor Heartfield” wrote in
message
news:xxxxx@ntfsd…
> Hi,
> I wonder if one of you gurus out there could help me. I have written a
> filter driver which is originally based on filespy from the 3790 IFS
kit.
> It is intended for the filter to operate under Win2K, WinXP
> and Win2K3. It all works fine under XP and 2K3 but I have problems
under
> WIN2K. The driver start type is set to 1 (SERVICE_SYSTEM_START). I see
the
> driver attaching to FAT, LanManRedirector and CDFS but not NTFS. All
the
> FsControlMountVolume requests I see going through for the NTFS volumes
are
> failing with code C000014f (Unrecognised file system) so I never
attach to
> them). I am sure the filter did originally work on these volumes. I
also
> have XP and 2K3 installed in different partitions. I am wondering if
when
> I booted the other systems, they updated the version of NTFS on there
and
> this is now causing problems ? It’s odd because once the system
completes
> the boot phase, all the volumes are visible in explorer. In case I had
> screwed something up, I tried filespy and it has the same problems -
it
> only attaches to the FAT partitions.
>
> So, if you guys have any thoughts, I would much appreciate to hear
from
> you.
>
> Kind Regards,
> Trevor Heartfield.
>
>
>
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Hi Tony,
Thanks for your reply. It turns out my mistake was that I forgot that the
‘FSFilter xxxxx’ groups only came in with XP/2K3 - doh! So, changed the
group to ‘Filter’ and it’s working fine again.
Kind Regards,
Trevor.
“Tony Mason” wrote in message news:xxxxx@ntfsd…
On Win2K, if your filter loads AFTER the file system, it will not learn
of its loading. On XP and W2K3 the load is reported to your filter even
though you have loaded after the file system (assuming you are using
IoRegisterFsRegistrationChangeNotification).
Even though you might be loading at boot time, you are still starting
too late in the sequence. Make sure your load group is BEFORE the boot
file system group.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Trevor Heartfield
Sent: Tuesday, November 09, 2004 1:59 PM
To: ntfsd redirect
Subject: Re:[ntfsd] Filter failing to attach to NTFS volumes under Win2K
OK, I’ve now set my filter to load at boot. It seems I do not get the
notification that NTFS is loading. I searched the archives and a couple
of
other people had this problem but I haven’t seen anyone supply the
answer.
“Trevor Heartfield” wrote in
message
news:xxxxx@ntfsd…
> Hi,
> I wonder if one of you gurus out there could help me. I have written a
> filter driver which is originally based on filespy from the 3790 IFS
kit.
> It is intended for the filter to operate under Win2K, WinXP
> and Win2K3. It all works fine under XP and 2K3 but I have problems
under
> WIN2K. The driver start type is set to 1 (SERVICE_SYSTEM_START). I see
the
> driver attaching to FAT, LanManRedirector and CDFS but not NTFS. All
the
> FsControlMountVolume requests I see going through for the NTFS volumes
are
> failing with code C000014f (Unrecognised file system) so I never
attach to
> them). I am sure the filter did originally work on these volumes. I
also
> have XP and 2K3 installed in different partitions. I am wondering if
when
> I booted the other systems, they updated the version of NTFS on there
and
> this is now causing problems ? It’s odd because once the system
completes
> the boot phase, all the volumes are visible in explorer. In case I had
> screwed something up, I tried filespy and it has the same problems -
it
> only attaches to the FAT partitions.
>
> So, if you guys have any thoughts, I would much appreciate to hear
from
> you.
>
> Kind Regards,
> Trevor Heartfield.
>
>
>
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com