This will work for minifilter in a similar way to how filters do this
today to handle changing kernel exports between the various OSes. (The
filespy and sfilter samples in the XP SP1 or later IFS Kits show how to
do this.)
If all the APIs your driver imports are available, the same driver will
run on all the platforms with no special handling. Otherwise, to use
APIs available on only a subset of the OSes, you will need to
dynamically import these new routines from fltmgr.sys (using
FltGetRoutineAddress) and use some other strategy for achieving the same
functionality on OSes without that support.
Today, the APIs supported by fltmgr.sys are the same across all the OSes
so dynamic importing of APIs isn’t needed for fltmgr APIs (although,
there may be kernel APIs where you still need to do this). In future OS
versions, we will be adding more APIs to the filter manager to better
support filters. If you want your minifilter to use these new APIs but
remain compatible across OSes, then you will have to use the dynamic
import mechanism.
Regards,
Molly Brown
Microsoft Corporation
This posting is provided “AS IS” with no warranties and confers no
rights.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Cross
Sent: Sunday, November 14, 2004 2:52 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] OS-specific stuff for mnifilters?
NTFSD Folk:
What’s the difference between a minifilter built for Win XP vs. Srv03
vs.
(eventually) Win 2K?
If virtually all calls are to FltXxx routines which are (as I understand
it) consistent between the various flavors of OS.
So is a separate minifilter really required for Win XP and Srv03 and
(eventually) Win 2K? Is the resulting .sys file interchangeable?
Thanks,
Ken
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com