WPP in 2K Filters

All,

Attempting to integrate WPP into my 2K filter drivers, I decided to use the
latest NTInsider article. I have had no troubles integrating this for XP for
quite some time but 2K has always given me troubles, until now, or so I
thought.

Following the recipe outlined seemed to make sense, though when I compile I
receive two errors. The first being the bits which I define as my events via
the WPP_DEFINE_BITS macro in the WPP_CONTROL_GUIDS macro are not being
defined and come up as undeclared. Second, the trace function I define in
the RUN_WPP directive in my sources file via the -func option is
unrecognized.

Its interesting that when I build for XP, using the XP way of doing WPP, I
do see my trace message function and the define bits referenced in the tmh
files that are created but when I do the 2K approach, as outlined in the
article, they are no where to be found.

Has anyone successfully integrated WPP into their 2K filesystem filter
driver?

Thanks,

Pete

Kernel Drivers
Windows Filesystem and Device Driver Consulting
www.KernelDrivers.com
(303)546-0300

Pete:

Yes, I’ve successfully gotten WPP working on Win2K for my mini-filter. No,
it was not easy.

I added User Comments at the end of the article
http://osronline.com/article.cfm?id=376 that describes some of my pain.
Hope it helps.

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Scott
Sent: Thursday, March 31, 2005 12:38 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] WPP in 2K Filters

All,

Attempting to integrate WPP into my 2K filter drivers, I decided to use the
latest NTInsider article. I have had no troubles integrating this for XP for
quite some time but 2K has always given me troubles, until now, or so I
thought.

Following the recipe outlined seemed to make sense, though when I compile I
receive two errors. The first being the bits which I define as my events via
the WPP_DEFINE_BITS macro in the WPP_CONTROL_GUIDS macro are not being
defined and come up as undeclared. Second, the trace function I define in
the RUN_WPP directive in my sources file via the -func option is
unrecognized.

Its interesting that when I build for XP, using the XP way of doing WPP, I
do see my trace message function and the define bits referenced in the tmh
files that are created but when I do the 2K approach, as outlined in the
article, they are no where to be found.

Has anyone successfully integrated WPP into their 2K filesystem filter
driver?

Thanks,

Pete

Kernel Drivers
Windows Filesystem and Device Driver Consulting
www.KernelDrivers.com
(303)546-0300


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

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

Hi,

A few quick things:

  1. Do your filters include ntifs.h or ntddk.h? You’re going to have a hard
    time getting the 2K tracing working with ntifs.h cuz the 2K tracing includes
    ntddk.h (though you’d be experiencing a lot more problems than what you’ve
    described if this was the case)

  2. I thought I’d had every tracing problem, but I’ve never had the
    WPP_DEFINE_BIT problem or the tracing function problem. Have you tried
    adding “-v4” as an argument to your RUN_WPP statement? This will add
    versbose output from the trace preprocessor in your build log, which might
    help.

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Peter Scott” wrote in message
news:xxxxx@ntfsd…
>
> All,
>
> Attempting to integrate WPP into my 2K filter drivers, I decided to use
> the
> latest NTInsider article. I have had no troubles integrating this for XP
> for
> quite some time but 2K has always given me troubles, until now, or so I
> thought.
>
> Following the recipe outlined seemed to make sense, though when I compile
> I
> receive two errors. The first being the bits which I define as my events
> via
> the WPP_DEFINE_BITS macro in the WPP_CONTROL_GUIDS macro are not being
> defined and come up as undeclared. Second, the trace function I define in
> the RUN_WPP directive in my sources file via the -func option is
> unrecognized.
>
> Its interesting that when I build for XP, using the XP way of doing WPP, I
> do see my trace message function and the define bits referenced in the tmh
> files that are created but when I do the 2K approach, as outlined in the
> article, they are no where to be found.
>
> Has anyone successfully integrated WPP into their 2K filesystem filter
> driver?
>
> Thanks,
>
> Pete
>
> Kernel Drivers
> Windows Filesystem and Device Driver Consulting
> www.KernelDrivers.com
> (303)546-0300
>
>
>
>
>

Thanks, I’ll give it a go.

Pete

Kernel Drivers
Windows Filesystem and Device Driver Consulting
www.KernelDrivers.com
(303)546-0300

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Cross
Sent: Thursday, March 31, 2005 11:06 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] WPP in 2K Filters

Pete:

Yes, I’ve successfully gotten WPP working on Win2K for my mini-filter. No,
it was not easy.

I added User Comments at the end of the article
http://osronline.com/article.cfm?id=376 that describes some of my pain.
Hope it helps.

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Scott
Sent: Thursday, March 31, 2005 12:38 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] WPP in 2K Filters

All,

Attempting to integrate WPP into my 2K filter drivers, I decided to use the
latest NTInsider article. I have had no troubles integrating this for XP for
quite some time but 2K has always given me troubles, until now, or so I
thought.

Following the recipe outlined seemed to make sense, though when I compile I
receive two errors. The first being the bits which I define as my events via
the WPP_DEFINE_BITS macro in the WPP_CONTROL_GUIDS macro are not being
defined and come up as undeclared. Second, the trace function I define in
the RUN_WPP directive in my sources file via the -func option is
unrecognized.

Its interesting that when I build for XP, using the XP way of doing WPP, I
do see my trace message function and the define bits referenced in the tmh
files that are created but when I do the 2K approach, as outlined in the
article, they are no where to be found.

Has anyone successfully integrated WPP into their 2K filesystem filter
driver?

Thanks,

Pete

Kernel Drivers
Windows Filesystem and Device Driver Consulting
www.KernelDrivers.com
(303)546-0300


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

You are currently subscribed to ntfsd as: xxxxx@comcast.net
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@kerneldrivers.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Scott,

I have tried the -v4 and it shows nothing of particular value. No errors in
the preprocessor and it see’s all the arguments.

One thing, as an experiment I tried this implementation in a standard PnP
class driver. No IFS kit, with 2K support and I get the same errors.

Not sure what could be happening with this.

Pete

Kernel Drivers
Windows Filesystem and Device Driver Consulting
www.KernelDrivers.com
(303)546-0300

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, March 31, 2005 11:07 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] WPP in 2K Filters

Hi,

A few quick things:

  1. Do your filters include ntifs.h or ntddk.h? You’re going to have a hard
    time getting the 2K tracing working with ntifs.h cuz the 2K tracing includes

ntddk.h (though you’d be experiencing a lot more problems than what you’ve
described if this was the case)

  1. I thought I’d had every tracing problem, but I’ve never had the
    WPP_DEFINE_BIT problem or the tracing function problem. Have you tried
    adding “-v4” as an argument to your RUN_WPP statement? This will add
    versbose output from the trace preprocessor in your build log, which might
    help.

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Peter Scott” wrote in message
news:xxxxx@ntfsd…
>
> All,
>
> Attempting to integrate WPP into my 2K filter drivers, I decided to use
> the
> latest NTInsider article. I have had no troubles integrating this for XP
> for
> quite some time but 2K has always given me troubles, until now, or so I
> thought.
>
> Following the recipe outlined seemed to make sense, though when I compile
> I
> receive two errors. The first being the bits which I define as my events
> via
> the WPP_DEFINE_BITS macro in the WPP_CONTROL_GUIDS macro are not being
> defined and come up as undeclared. Second, the trace function I define in
> the RUN_WPP directive in my sources file via the -func option is
> unrecognized.
>
> Its interesting that when I build for XP, using the XP way of doing WPP, I
> do see my trace message function and the define bits referenced in the tmh
> files that are created but when I do the 2K approach, as outlined in the
> article, they are no where to be found.
>
> Has anyone successfully integrated WPP into their 2K filesystem filter
> driver?
>
> Thanks,
>
> Pete
>
> Kernel Drivers
> Windows Filesystem and Device Driver Consulting
> www.KernelDrivers.com
> (303)546-0300
>
>
>
>
>


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

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

Which IFS Kit/DDK are you using to build?

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

Looking forward to seeing you at the Next OSR File Systems Class April
4, 2005 in Boston!

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Scott
Sent: Thursday, March 31, 2005 4:13 PM
To: ntfsd redirect
Subject: RE: [ntfsd] WPP in 2K Filters

Scott,

I have tried the -v4 and it shows nothing of particular value. No errors
in
the preprocessor and it see’s all the arguments.

One thing, as an experiment I tried this implementation in a standard
PnP
class driver. No IFS kit, with 2K support and I get the same errors.

Not sure what could be happening with this.

Pete

Kernel Drivers
Windows Filesystem and Device Driver Consulting
www.KernelDrivers.com
(303)546-0300

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, March 31, 2005 11:07 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] WPP in 2K Filters

Hi,

A few quick things:

  1. Do your filters include ntifs.h or ntddk.h? You’re going to have a
    hard
    time getting the 2K tracing working with ntifs.h cuz the 2K tracing
    includes

ntddk.h (though you’d be experiencing a lot more problems than what
you’ve
described if this was the case)

  1. I thought I’d had every tracing problem, but I’ve never had the
    WPP_DEFINE_BIT problem or the tracing function problem. Have you tried
    adding “-v4” as an argument to your RUN_WPP statement? This will add
    versbose output from the trace preprocessor in your build log, which
    might
    help.

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Peter Scott” wrote in message
news:xxxxx@ntfsd…
>
> All,
>
> Attempting to integrate WPP into my 2K filter drivers, I decided to
use
> the
> latest NTInsider article. I have had no troubles integrating this for
XP
> for
> quite some time but 2K has always given me troubles, until now, or so
I
> thought.
>
> Following the recipe outlined seemed to make sense, though when I
compile
> I
> receive two errors. The first being the bits which I define as my
events
> via
> the WPP_DEFINE_BITS macro in the WPP_CONTROL_GUIDS macro are not being
> defined and come up as undeclared. Second, the trace function I define
in
> the RUN_WPP directive in my sources file via the -func option is
> unrecognized.
>
> Its interesting that when I build for XP, using the XP way of doing
WPP, I
> do see my trace message function and the define bits referenced in the
tmh
> files that are created but when I do the 2K approach, as outlined in
the
> article, they are no where to be found.
>
> Has anyone successfully integrated WPP into their 2K filesystem filter
> driver?
>
> Thanks,
>
> Pete
>
> Kernel Drivers
> Windows Filesystem and Device Driver Consulting
> www.KernelDrivers.com
> (303)546-0300
>
>
>
>
>


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

You are currently subscribed to ntfsd as: xxxxx@kerneldrivers.com
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@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Pete

Kernel Drivers
Windows Filesystem and Device Driver Consulting
www.KernelDrivers.com
(303)546-0300

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Thursday, March 31, 2005 4:05 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] WPP in 2K Filters

Which IFS Kit/DDK are you using to build?

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

Looking forward to seeing you at the Next OSR File Systems Class April
4, 2005 in Boston!

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Scott
Sent: Thursday, March 31, 2005 4:13 PM
To: ntfsd redirect
Subject: RE: [ntfsd] WPP in 2K Filters

Scott,

I have tried the -v4 and it shows nothing of particular value. No errors
in
the preprocessor and it see’s all the arguments.

One thing, as an experiment I tried this implementation in a standard
PnP
class driver. No IFS kit, with 2K support and I get the same errors.

Not sure what could be happening with this.

Pete

Kernel Drivers
Windows Filesystem and Device Driver Consulting
www.KernelDrivers.com
(303)546-0300

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, March 31, 2005 11:07 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] WPP in 2K Filters

Hi,

A few quick things:

  1. Do your filters include ntifs.h or ntddk.h? You’re going to have a
    hard
    time getting the 2K tracing working with ntifs.h cuz the 2K tracing
    includes

ntddk.h (though you’d be experiencing a lot more problems than what
you’ve
described if this was the case)

  1. I thought I’d had every tracing problem, but I’ve never had the
    WPP_DEFINE_BIT problem or the tracing function problem. Have you tried
    adding “-v4” as an argument to your RUN_WPP statement? This will add
    versbose output from the trace preprocessor in your build log, which
    might
    help.

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Peter Scott” wrote in message
news:xxxxx@ntfsd…
>
> All,
>
> Attempting to integrate WPP into my 2K filter drivers, I decided to
use
> the
> latest NTInsider article. I have had no troubles integrating this for
XP
> for
> quite some time but 2K has always given me troubles, until now, or so
I
> thought.
>
> Following the recipe outlined seemed to make sense, though when I
compile
> I
> receive two errors. The first being the bits which I define as my
events
> via
> the WPP_DEFINE_BITS macro in the WPP_CONTROL_GUIDS macro are not being
> defined and come up as undeclared. Second, the trace function I define
in
> the RUN_WPP directive in my sources file via the -func option is
> unrecognized.
>
> Its interesting that when I build for XP, using the XP way of doing
WPP, I
> do see my trace message function and the define bits referenced in the
tmh
> files that are created but when I do the 2K approach, as outlined in
the
> article, they are no where to be found.
>
> Has anyone successfully integrated WPP into their 2K filesystem filter
> driver?
>
> Thanks,
>
> Pete
>
> Kernel Drivers
> Windows Filesystem and Device Driver Consulting
> www.KernelDrivers.com
> (303)546-0300
>
>
>
>
>


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

You are currently subscribed to ntfsd as: xxxxx@kerneldrivers.com
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@osr.com
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: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

Hi,

Can you build the featured2 Toaster sample in the DDK?

I’ve been trying to move things around in the drivers that I have with 2K
tracing to get this error that you’re seeing, but I’m not hitting it. What
does your RUN_WPP statement look like?

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Peter Scott” wrote in message
news:xxxxx@ntfsd…
>
> Scott,
>
> I have tried the -v4 and it shows nothing of particular value. No errors
> in
> the preprocessor and it see’s all the arguments.
>
> One thing, as an experiment I tried this implementation in a standard PnP
> class driver. No IFS kit, with 2K support and I get the same errors.
>
> Not sure what could be happening with this.
>
> Pete
>
> Kernel Drivers
> Windows Filesystem and Device Driver Consulting
> www.KernelDrivers.com
> (303)546-0300
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
> Sent: Thursday, March 31, 2005 11:07 AM
> To: Windows File Systems Devs Interest List
> Subject: Re:[ntfsd] WPP in 2K Filters
>
> Hi,
>
> A few quick things:
>
> 1) Do your filters include ntifs.h or ntddk.h? You’re going to have a hard
> time getting the 2K tracing working with ntifs.h cuz the 2K tracing
> includes
>
> ntddk.h (though you’d be experiencing a lot more problems than what you’ve
> described if this was the case)
>
> 2) I thought I’d had every tracing problem, but I’ve never had the
> WPP_DEFINE_BIT problem or the tracing function problem. Have you tried
> adding “-v4” as an argument to your RUN_WPP statement? This will add
> versbose output from the trace preprocessor in your build log, which might
> help.
>
> -scott
>
> –
> Scott Noone
> Software Engineer
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
> “Peter Scott” wrote in message
> news:xxxxx@ntfsd…
>>
>> All,
>>
>> Attempting to integrate WPP into my 2K filter drivers, I decided to use
>> the
>> latest NTInsider article. I have had no troubles integrating this for XP
>> for
>> quite some time but 2K has always given me troubles, until now, or so I
>> thought.
>>
>> Following the recipe outlined seemed to make sense, though when I compile
>> I
>> receive two errors. The first being the bits which I define as my events
>> via
>> the WPP_DEFINE_BITS macro in the WPP_CONTROL_GUIDS macro are not being
>> defined and come up as undeclared. Second, the trace function I define in
>> the RUN_WPP directive in my sources file via the -func option is
>> unrecognized.
>>
>> Its interesting that when I build for XP, using the XP way of doing WPP,
>> I
>> do see my trace message function and the define bits referenced in the
>> tmh
>> files that are created but when I do the 2K approach, as outlined in the
>> article, they are no where to be found.
>>
>> Has anyone successfully integrated WPP into their 2K filesystem filter
>> driver?
>>
>> Thanks,
>>
>> Pete
>>
>> Kernel Drivers
>> Windows Filesystem and Device Driver Consulting
>> www.KernelDrivers.com
>> (303)546-0300
>>
>>
>>
>>
>>
>
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@kerneldrivers.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>

FYI - My problem turned out to be a finicky preprocessor. It doesn’t like
spaces in the function prototype and I was mismatching a variable name. No
relevant errors though.

Thanks to Scott for figuring that little nuance out.

All is working fine, 2K and XP using the IFS kit.

Pete

Kernel Drivers
Windows Filesystem and Device Driver Consulting
www.KernelDrivers.com
(303)546-0300

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Friday, April 01, 2005 7:27 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] WPP in 2K Filters

Hi,

Can you build the featured2 Toaster sample in the DDK?

I’ve been trying to move things around in the drivers that I have with 2K
tracing to get this error that you’re seeing, but I’m not hitting it. What
does your RUN_WPP statement look like?

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Peter Scott” wrote in message
news:xxxxx@ntfsd…
>
> Scott,
>
> I have tried the -v4 and it shows nothing of particular value. No errors
> in
> the preprocessor and it see’s all the arguments.
>
> One thing, as an experiment I tried this implementation in a standard PnP
> class driver. No IFS kit, with 2K support and I get the same errors.
>
> Not sure what could be happening with this.
>
> Pete
>
> Kernel Drivers
> Windows Filesystem and Device Driver Consulting
> www.KernelDrivers.com
> (303)546-0300
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
> Sent: Thursday, March 31, 2005 11:07 AM
> To: Windows File Systems Devs Interest List
> Subject: Re:[ntfsd] WPP in 2K Filters
>
> Hi,
>
> A few quick things:
>
> 1) Do your filters include ntifs.h or ntddk.h? You’re going to have a hard
> time getting the 2K tracing working with ntifs.h cuz the 2K tracing
> includes
>
> ntddk.h (though you’d be experiencing a lot more problems than what you’ve
> described if this was the case)
>
> 2) I thought I’d had every tracing problem, but I’ve never had the
> WPP_DEFINE_BIT problem or the tracing function problem. Have you tried
> adding “-v4” as an argument to your RUN_WPP statement? This will add
> versbose output from the trace preprocessor in your build log, which might
> help.
>
> -scott
>
> –
> Scott Noone
> Software Engineer
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
> “Peter Scott” wrote in message
> news:xxxxx@ntfsd…
>>
>> All,
>>
>> Attempting to integrate WPP into my 2K filter drivers, I decided to use
>> the
>> latest NTInsider article. I have had no troubles integrating this for XP
>> for
>> quite some time but 2K has always given me troubles, until now, or so I
>> thought.
>>
>> Following the recipe outlined seemed to make sense, though when I compile
>> I
>> receive two errors. The first being the bits which I define as my events
>> via
>> the WPP_DEFINE_BITS macro in the WPP_CONTROL_GUIDS macro are not being
>> defined and come up as undeclared. Second, the trace function I define in
>> the RUN_WPP directive in my sources file via the -func option is
>> unrecognized.
>>
>> Its interesting that when I build for XP, using the XP way of doing WPP,
>> I
>> do see my trace message function and the define bits referenced in the
>> tmh
>> files that are created but when I do the 2K approach, as outlined in the
>> article, they are no where to be found.
>>
>> Has anyone successfully integrated WPP into their 2K filesystem filter
>> driver?
>>
>> Thanks,
>>
>> Pete
>>
>> Kernel Drivers
>> Windows Filesystem and Device Driver Consulting
>> www.KernelDrivers.com
>> (303)546-0300
>>
>>
>>
>>
>>
>
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@kerneldrivers.com
> 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@kerneldrivers.com
To unsubscribe send a blank email to xxxxx@lists.osr.com