DriverWorks

I am trying to get DriverWorks to help me create a cpp frame work for a file
system filter driver. No where in the settings can I find the options to
create it, can some one help me. Is it not possible to create a file system
filter driver through this product.

I don’t have IFS kit installed in the system, can that be a problem why the
particular wizard is absent?

  • Developer

DriverWorks doesn’t have a wizard for filesystem filters (at not least in the version I have). However, it will generate a very basic framework and does have a mechanism in it for filtering files. I could be mistaken, but I believe it has two file filtering classes Kfilter and KfilterFile. However, you must implement those yourself and there isn’t a whole lot of documentation in the help file on those two classes. You kinda have to figure it out yourself.
----- Original Message -----
From: Developer
To: Windows File Systems Devs Interest List
Sent: Thursday, September 15, 2005 6:21 AM
Subject: [ntfsd] DriverWorks

I am trying to get DriverWorks to help me create a cpp frame work for a file system filter driver. No where in the settings can I find the options to create it, can some one help me. Is it not possible to create a file system filter driver through this product.

I don’t have IFS kit installed in the system, can that be a problem why the particular wizard is absent?

thanks mat,

well these classes are not documented in driver works help :frowning: . By the way,
can you tell me how to build the basic framework from the wizard (atleast
teh closest I can get to FS filtering!!!)

amitrajit

First,

The basic framework I was speaking of is the basic driver routines (entry, dispatch, ect…) Basically stuff you already know how to do (just something to save you a little time).

As I stated, “I could be mistaken, but I believe it has two file filtering classes Kfilter and KfilterFile”, well, I was mistaken. The class you need too look for is KFilterDevice

Just fired up my notebook and saw that…

Even though DriverWorks isn’t really targeted at filesystem drivers, it’s still an awesome package. Softice rocks (I think it’s ten times better than windbg) and you know have that, and the network driver wizard makes building firewall comp.s a snap…
----- Original Message -----
From: Developer
To: Windows File Systems Devs Interest List
Sent: Thursday, September 15, 2005 6:59 AM
Subject: Re: [ntfsd] DriverWorks

thanks mat,

well these classes are not documented in driver works help :frowning: . By the way, can you tell me how to build the basic framework from the wizard (atleast teh closest I can get to FS filtering!!!)

amitrajit

— 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

>The basic framework I was speaking of is the basic driver routines (entry,
dispatch, ect…) Basically >stuff you already know how to do (just
something to save you a little time).

OK, but the problem is which type of driver do i chose, as it is, it doesnt
give a drop down list of trhe available choices, so what “Driver Project
Type” do I use, none of the available options is close enough :frowning:

Closest is WDM driver, and that is *not at all close*

Even if i go on with WDM, and select it, what do I select in “Filter Type”
what name should be typed in device fileter or class filter, does this name
need to be the actual name of the class/device type in the windows
registry???

As I stated, “I could be mistaken, but I believe it has two file
filtering classes Kfilter and >KfilterFile”, well, I was mistaken. The class
you need too look for is KFilterDevice
>Just fired up my notebook and saw that…

Hmmm ya, KFilterDevice does exist.
>Even though DriverWorks isn’t really targeted at filesystem drivers, it’s
still an awesome package. >Softice rocks (I think it’s ten times better than
windbg) and you know have that, and the network >driver wizard makes
building firewall comp.s a snap…

Heck, hope Jason Shay is not tuned in (grin)…well as they say…“If you
want to build a superior product, you should already be involved in making
an inferior one”…

There is one more thing I find a bit strange, the “Sources” file generated
by DriverWorks doesn’t have any distinguishing features for a cpp file entry
point. May be I am totally mistaken, but how does NMAKE find out and
properly compile and link C++ code?

I don’t believe that DriverWorks can create a FS Filter. No matter what you do, you will need the IFS. It sounds like you are new to this. For what it is worth, I would recommed strongly against using DriverWorks unless you have a compeling reason to do so.

MM

>> xxxxx@gmail.com 09/15/05 7:21 AM >>>
I am trying to get DriverWorks to help me create a cpp frame work for a file
system filter driver. No where in the settings can I find the options to
create it, can some one help me. Is it not possible to create a file system
filter driver through this product.

I don’t have IFS kit installed in the system, can that be a problem why the
particular wizard is absent?

  • Developer

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

select an “NT 4 style driver”; wdm is invalid for filter drivers. File system filters can not support power management or other features in WDM.

Under the the next menu, select “none, driver does not control hardware”.

Just click next threw the next menu’s. These next menus will ask for symbolic link names, ect, so pay attention. After the wizard completes, you’ll have to go back and change a few things (remember kfilterdevice). Like I said, the wizard does not support creating filesystem filters. You’ll have to implement that stuff yourself, and there isn’t a lot of doc’s on it.
----- Original Message -----
From: Developer
To: Windows File Systems Devs Interest List
Sent: Thursday, September 15, 2005 8:24 AM
Subject: Re: [ntfsd] DriverWorks

The basic framework I was speaking of is the basic driver routines (entry, dispatch, ect…) Basically >stuff you already know how to do (just something to save you a little time).

OK, but the problem is which type of driver do i chose, as it is, it doesnt give a drop down list of trhe available choices, so what “Driver Project Type” do I use, none of the available options is close enough :frowning:

Closest is WDM driver, and that is *not at all close*

Even if i go on with WDM, and select it, what do I select in “Filter Type” what name should be typed in device fileter or class filter, does this name need to be the actual name of the class/device type in the windows registry???

As I stated, “I could be mistaken, but I believe it has two file filtering classes Kfilter and >KfilterFile”, well, I was mistaken. The class you need too look for is KFilterDevice

Just fired up my notebook and saw that…

Hmmm ya, KFilterDevice does exist.

Even though DriverWorks isn’t really targeted at filesystem drivers, it’s still an awesome package. >Softice rocks (I think it’s ten times better than windbg) and you know have that, and the network >driver wizard makes building firewall comp.s a snap…

Heck, hope Jason Shay is not tuned in (grin)…well as they say…“If you want to build a superior product, you should already be involved in making an inferior one”…

— 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

DriverWorks integrates into visual studio, it has a bunch of special build options added to the enviro. It will figure it out… No need to worry about the build
----- Original Message -----
From: Developer
To: Windows File Systems Devs Interest List
Sent: Thursday, September 15, 2005 8:38 AM
Subject: Re: [ntfsd] DriverWorks

There is one more thing I find a bit strange, the “Sources” file generated by DriverWorks doesn’t have any distinguishing features for a cpp file entry point. May be I am totally mistaken, but how does NMAKE find out and properly compile and link C++ code? — 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 will jump in to agreee with Martin, what do you think you will gain from
using DriverWorks. Over the years, I have run into multiple companies who
used DriverWorks, then had to wait for ever to get support of the current OS
revision. I am at present doing a code review of a driver written with
this, I am amazed by just using the my standard compile checks (/Wall,
PREfast, and PC-Lint) how many bug reports the customer is filing on this
stuff. Finally, this customer is finding the common problem, namely that
there are not a lot of DriverWorks qualified people out there, so they are
looking at replacing all the drivers developed in this stuff.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Martin O’Brien” wrote in message
news:xxxxx@ntfsd…
I don’t believe that DriverWorks can create a FS Filter. No matter what you
do, you will need the IFS. It sounds like you are new to this. For what it
is worth, I would recommed strongly against using DriverWorks unless you
have a compeling reason to do so.

MM

>>> xxxxx@gmail.com 09/15/05 7:21 AM >>>
I am trying to get DriverWorks to help me create a cpp frame work for a file
system filter driver. No where in the settings can I find the options to
create it, can some one help me. Is it not possible to create a file system
filter driver through this product.

I don’t have IFS kit installed in the system, can that be a problem why the
particular wizard is absent?



- Developer


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

>select an “NT 4 style driver”; wdm is invalid for filter drivers.
There is *no* such option. In Project Type you can have

Choose one of the following as your driver project type:
WDM Driver Select this option if your driver is for WDM Kernel Mode
Service Select this option if your driver is kernel mode service NDIS
Driver Select this option if your driver is NDIS network device driver
AVStream Minidriver Select
this option if your driver is AVStream minidriver

Choose a Driver Framework to use:
DriverWorks C++ Framework Select this option to use the DriverWorks C++
Framework DriverNetworks C++ Framework Select this option to use the
DriverNetworks C++ Framework No Framework Select this option to use C
without a Framework

Upon selecting WDM you can go to WDM filter and then to None - Driver Doesnt
control HW.

File system filters can not support >power management or other features in
WDM.

I know, thats why I said, WDM was not close enough.

Just click next threw the next menu’s. These next menus will ask for
symbolic link names, ect, >so pay attention. After the wizard completes,
you’ll have to go back and change a few things >(remember kfilterdevice).
Like I said, the wizard does not support creating filesystem filters. You’ll
have to implement that stuff yourself, and there isn’t a lot of doc’s on
it.

Ok, lets see what I can do about that…

DriverWorks integrates into visual studio, it has a bunch of special build
options added to the >enviro. It will figure it out… No need to worry
about the build

No I am curious to know how the frame work libraries do the trick. Delving
deeper and deeper to knwo more.

thanks for the tips…

amitrajit

>I don’t believe that DriverWorks can create a FS Filter. No matter what you
do, you will need the >IFS. It sounds like you are new to this. For what it
is worth, I would recommed strongly against >using DriverWorks unless you
have a compeling reason to do so.

MM

We will use IFS, no doubt in that, all I was trying out was to evaluate
DriverWorks to find out whether it suits our needs of developing a FS
filter. After all this discussion I don’t think it is going to.

Well, even if I have IFS installed, it doesnt help much with DriverWorks.
Personally I would stick to normal C programming, I feel confortable that
way.

By the way, I did a lot of reading on WDF model, though I never used it, is
that a good approach?

Amitrajit

well, you have have a different version of driver works than I do then…

What version are you using… I believe mine is 2.7… I have the project option of “NT 4 style driver”
----- Original Message -----
From: Developer
To: Windows File Systems Devs Interest List
Sent: Thursday, September 15, 2005 9:19 AM
Subject: Re: [ntfsd] DriverWorks

select an “NT 4 style driver”; wdm is invalid for filter drivers.
There is *no* such option. In Project Type you can have

Choose one of the following as your driver project type:
WDM Driver Select this option if your driver is for WDM
Kernel Mode Service Select this option if your driver is kernel mode service
NDIS Driver Select this option if your driver is NDIS network device driver
AVStream Minidriver Select this option if your driver is AVStream minidriver


Choose a Driver Framework to use:
DriverWorks C++ Framework Select this option to use the DriverWorks C++ Framework
DriverNetworks C++ Framework Select this option to use the DriverNetworks C++ Framework
No Framework Select this option to use C without a Framework

Upon selecting WDM you can go to WDM filter and then to None - Driver Doesnt control HW.

File system filters can not support >power management or other features in WDM.

I know, thats why I said, WDM was not close enough.

Just click next threw the next menu’s. These next menus will ask for symbolic link names, ect, >so pay attention. After the wizard completes, you’ll have to go back and change a few things >(remember kfilterdevice). Like I said, the wizard does not support creating filesystem filters. You’ll >have to implement that stuff yourself, and there isn’t a lot of doc’s on it.

Ok, lets see what I can do about that…

DriverWorks integrates into visual studio, it has a bunch of special build options added to the >enviro. It will figure it out… No need to worry about the build

No I am curious to know how the frame work libraries do the trick. Delving deeper and deeper to knwo more.

thanks for the tips…

amitrajit

— 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 currently have a DriverWorks bus driver that I need to move into the storage stack to function as a filter and enumerate an interface — specifically the IFD for our trusted drives. This driver works fine as a PnP bus driver, but converting it to a filter with an enumerated interface is proving to be a bit hairy, since once again we are constrained by what the boys and girls at Numega/Compuware did not think or care about. From what I have seen, you can write a NON-PnP filter using KFilterDevice, but there is no class for a PnP filter, which means it looks like a “roll your own” using KPnPDevice and/or KLowerDevice.

I have to agree with the general sentiment, having used DriverWorks, and would not recommend it.


The personal opinion of
Gary G. Little

“Developer” wrote in message news:xxxxx@ntfsd…
>I don’t believe that DriverWorks can create a FS Filter. No matter what you do, you will need the >IFS. It sounds like you are new to this. For what it is worth, I would recommed strongly against >using DriverWorks unless you have a compeling reason to do so.
>
>MM

We will use IFS, no doubt in that, all I was trying out was to evaluate DriverWorks to find out whether it suits our needs of developing a FS filter. After all this discussion I don’t think it is going to.

Well, even if I have IFS installed, it doesnt help much with DriverWorks. Personally I would stick to normal C programming, I feel confortable that way.

By the way, I did a lot of reading on WDF model, though I never used it, is that a good approach?

Amitrajit

DriverStudio Wizard Version: 3.2.0 (Build 2485)

amitr0

I know very little about WDM. Very little of the kernel work I do is
for actual (physical) devices. I have seen a prerelease of WDF, which,
as I understand it, is to replace WDM, and it is much, much (much)
simpler. I don’t know if this is an option for you, or, for that
matter, if it is even an option for the general public yet.

>> xxxxx@gmail.com 09/15/05 10:26 AM >>>
I don’t believe that DriverWorks can create a FS Filter. No matter
what you
do, you will need the >IFS. It sounds like you are new to this. For
what it
is worth, I would recommed strongly against >using DriverWorks unless
you
have a compeling reason to do so.

MM

We will use IFS, no doubt in that, all I was trying out was to evaluate

DriverWorks to find out whether it suits our needs of developing a FS
filter. After all this discussion I don’t think it is going to.

Well, even if I have IFS installed, it doesnt help much with
DriverWorks.
Personally I would stick to normal C programming, I feel confortable
that
way.

By the way, I did a lot of reading on WDF model, though I never used
it, is
that a good approach?

Amitrajit


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

WDF is not for file system (at least not yet). It is not a replacelemt for
WDM, since for many drivers you are going to have to dive into WDM fromWDF.
What WDF does is provide a framework where much of the boilerplate code
(some of which like power management is hard to get right) is taken care of
for you.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Martin O’Brien” wrote in message
news:xxxxx@ntfsd…
>I know very little about WDM. Very little of the kernel work I do is
> for actual (physical) devices. I have seen a prerelease of WDF, which,
> as I understand it, is to replace WDM, and it is much, much (much)
> simpler. I don’t know if this is an option for you, or, for that
> matter, if it is even an option for the general public yet.
>
>
>
>
>
>
>>>> xxxxx@gmail.com 09/15/05 10:26 AM >>>
>>I don’t believe that DriverWorks can create a FS Filter. No matter
> what you
> do, you will need the >IFS. It sounds like you are new to this. For
> what it
> is worth, I would recommed strongly against >using DriverWorks unless
> you
> have a compeling reason to do so.
>>
>>MM
>
> We will use IFS, no doubt in that, all I was trying out was to evaluate
>
> DriverWorks to find out whether it suits our needs of developing a FS
> filter. After all this discussion I don’t think it is going to.
>
> Well, even if I have IFS installed, it doesnt help much with
> DriverWorks.
> Personally I would stick to normal C programming, I feel confortable
> that
> way.
>
> By the way, I did a lot of reading on WDF model, though I never used
> it, is
> that a good approach?
>
> Amitrajit
>
> —
> 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
>

IFS kit is *the* best option

My apologies. I really shouldn’t have commented, as my experience with
WDF consists entirely of two seminars at Driver DevCon.

MM

>> xxxxx@acm.org 09/15/05 4:55 PM >>>
WDF is not for file system (at least not yet). It is not a replacelemt
for
WDM, since for many drivers you are going to have to dive into WDM
fromWDF.
What WDF does is provide a framework where much of the boilerplate code

(some of which like power management is hard to get right) is taken
care of
for you.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Martin O’Brien” wrote in message
news:xxxxx@ntfsd…
>I know very little about WDM. Very little of the kernel work I do is
> for actual (physical) devices. I have seen a prerelease of WDF,
which,
> as I understand it, is to replace WDM, and it is much, much (much)
> simpler. I don’t know if this is an option for you, or, for that
> matter, if it is even an option for the general public yet.
>
>
>
>
>
>
>>>> xxxxx@gmail.com 09/15/05 10:26 AM >>>
>>I don’t believe that DriverWorks can create a FS Filter. No matter
> what you
> do, you will need the >IFS. It sounds like you are new to this. For
> what it
> is worth, I would recommed strongly against >using DriverWorks
unless
> you
> have a compeling reason to do so.
>>
>>MM
>
> We will use IFS, no doubt in that, all I was trying out was to
evaluate
>
> DriverWorks to find out whether it suits our needs of developing a
FS
> filter. After all this discussion I don’t think it is going to.
>
> Well, even if I have IFS installed, it doesnt help much with
> DriverWorks.
> Personally I would stick to normal C programming, I feel confortable
> that
> way.
>
> By the way, I did a lot of reading on WDF model, though I never used
> it, is
> that a good approach?
>
> Amitrajit
>
> —
> 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

>


Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

I guess the OP should be looking into the filter
manager. It’s now free if he has WDK beta access.

Long time ago, I put all drivers I’ve written together
and built my own framework for rapid driver
development. With the framework, I can write a
passthrough file system filter or a BUS Filter driver
or a bus driver within 100 lines of code. You will
have all Po/PNP features, WPP, built-in WMI class and
miniport-specific WMI class (think of ndis OIDs and
miniport OIDs) and it’s binary compatible from w2k to
current build of WLH. After WDF and filter manager
were introduced, I stop investigating in this hobby
project and start learning WDF to make sure I can
include it in my resume in the future:).

BTW, does WDF support bus filter driver now?

Calvin


Calvin Guan (Windows DDK MVP)
NetXtreme Longhorn Miniport Prime
Broadcom Corp. www.broadcom.com

— Don Burn wrote:

> WDF is not for file system (at least not yet). It
> is not a replacelemt for
> WDM, since for many drivers you are going to have to
> dive into WDM fromWDF.
> What WDF does is provide a framework where much of
> the boilerplate code
> (some of which like power management is hard to get
> right) is taken care of
> for you.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
>
> “Martin O’Brien” wrote
> in message
> news:xxxxx@ntfsd…
> >I know very little about WDM. Very little of the
> kernel work I do is
> > for actual (physical) devices. I have seen a
> prerelease of WDF, which,
> > as I understand it, is to replace WDM, and it is
> much, much (much)
> > simpler. I don’t know if this is an option for
> you, or, for that
> > matter, if it is even an option for the general
> public yet.
> >
> >
> >
> >
> >
> >
> >>>> xxxxx@gmail.com 09/15/05 10:26 AM >>>
> >>I don’t believe that DriverWorks can create a FS
> Filter. No matter
> > what you
> > do, you will need the >IFS. It sounds like you are
> new to this. For
> > what it
> > is worth, I would recommed strongly against >using
> DriverWorks unless
> > you
> > have a compeling reason to do so.
> >>
> >>MM
> >
> > We will use IFS, no doubt in that, all I was
> trying out was to evaluate
> >
> > DriverWorks to find out whether it suits our needs
> of developing a FS
> > filter. After all this discussion I don’t think it
> is going to.
> >
> > Well, even if I have IFS installed, it doesnt help
> much with
> > DriverWorks.
> > Personally I would stick to normal C programming,
> I feel confortable
> > that
> > way.
> >
> > By the way, I did a lot of reading on WDF model,
> though I never used
> > it, is
> > that a good approach?
> >
> > Amitrajit
> >
> > —
> > 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
> >
>
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as:
> xxxxx@yahoo.ca
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com