Network File System Driver

NTDEV
1

Hi,

I am new to writing drivers but not new to writing Win32 code in C/C++. I
have written a simple driver to get notification on process
creation/termination, so I am somewhat familiar with IOCTL calls and event
sync from user-mode code to kernel mode code.

Basically what I want to do next is write a nice source code control
application like clearcase. I would like to write a driver that would
allow me to create network drives on a client machine, and then
communicate to a service running on a server with the source code
repository via sockets. I have looked at the ramdisk example in the
Microsoft DDK, and have made it work on NT4, but it doesn’t seem to work
on XP. I figure I should call IOCreateDevice with the
FILE_DEVICE_NETWORK_FILE_SYSTEM device type, but I have no idea what IOCTL
requests that are going to be made etc etc. I have ordered what seems to
be the bible for windows driver development, “Windows NT Device Driver
Development”. I was hoping I could get more general direction from this
message board.

Thanks in advance for any help.

-Daniel

2

Yeah, for a version control system that would be implemented as a
filesystem you are a long way from it with Ramdisk. I would start with
the osronline filesystem faq, then order the ifskit and read all this
then try to get your hands on a copy of R. Nagar’s book on filesystems,
though dated it is a great reference. You can then take a seminar on it,
osr offers a great one.

Estimate ~12 months of effort to get a system up and running, but not
beta ready, after you have a good idea of what a network filesystem is.

Also try the ntfsd mailing list.

Pete

Peter Scott
xxxxx@KernelDrivers.com
www.KernelDrivers.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
Sent: Tuesday, November 18, 2003 9:50 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Network File System Driver

Hi,

I am new to writing drivers but not new to writing Win32 code in C/C++.
I
have written a simple driver to get notification on process
creation/termination, so I am somewhat familiar with IOCTL calls and
event
sync from user-mode code to kernel mode code.

Basically what I want to do next is write a nice source code control
application like clearcase. I would like to write a driver that would
allow me to create network drives on a client machine, and then
communicate to a service running on a server with the source code
repository via sockets. I have looked at the ramdisk example in the
Microsoft DDK, and have made it work on NT4, but it doesn’t seem to work
on XP. I figure I should call IOCreateDevice with the
FILE_DEVICE_NETWORK_FILE_SYSTEM device type, but I have no idea what
IOCTL
requests that are going to be made etc etc. I have ordered what seems to
be the bible for windows driver development, “Windows NT Device Driver
Development”. I was hoping I could get more general direction from this
message board.

Thanks in advance for any help.

-Daniel

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

3

This is an ambitious project. Heed what Peter Scott said.

By the by, let me dwell on the fact that you latched on to
FILE_DEVICE_NETWORK_FILE_SYSTEM. There is a tendency, and I’ve done exactly
this thing, to search for a parameter or value or whatever that appears
vaguely like what one (thinks he) needs, and then to try to uncover the hidden
service at which the parameter hints. I’ve seen this tendency particularly in
the file system area, eg, the IOCTL known only to initiates that will do
exactly what’s needed and that Microsoft, or whoever, has churlishly not
documented. Almost always, it’s not so. That temptingly named thing is either
misleadingly named, or it is but a tiny piece in a very considerable body of
software. I imagine the latter is the case with
FILE_DEVICE_NETWORK_FILE_SYSTEM, that this is used in a massive component, a
remote file system.

I’m not saying you were wrong or mistaken in searching for this parameter and
in inquiring. In fact, you took the intelligent, time-saving route of asking
others who might know. But beware of parameters that promise magic.

Back to your actual questions: Viscarola and Mason’s book is fine but dated
(when’s that update coming, guys?). Today the standard is Walter Oney’s
“Programming the Microsoft Windows Driver Model,” second edition.

Daniel wrote:

Basically what I want to do next is write a nice source code control
application like clearcase. I would like to write a driver that would
allow me to create network drives on a client machine, and then
communicate to a service running on a server with the source code
repository via sockets. I have looked at the ramdisk example in the
Microsoft DDK, and have made it work on NT4, but it doesn’t seem to work
on XP. I figure I should call IOCreateDevice with the
FILE_DEVICE_NETWORK_FILE_SYSTEM device type, but I have no idea what IOCTL
requests that are going to be made etc etc. I have ordered what seems to
be the bible for windows driver development, “Windows NT Device Driver
Development”. I was hoping I could get more general direction from this
message board.

–
If replying by e-mail, please remove “nospam.” from the address.

James Antognini
Windows DDK MVP

4

With all the cautions mentioned here, one of the approach would be to follow
Rajeev’s book and get a pseudo filesystem driver up and running. The codes
and example in there is just to explain this beast.

I’ve seen commercial, popular, and might be one of the latest approach to
source code control system using that direction…

-prokash

----- Original Message -----
From: “James Antognini”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Wednesday, November 19, 2003 6:46 AM
Subject: [ntdev] Re: Network File System Driver

> This is an ambitious project. Heed what Peter Scott said.
>
> By the by, let me dwell on the fact that you latched on to
> FILE_DEVICE_NETWORK_FILE_SYSTEM. There is a tendency, and I’ve done
exactly
> this thing, to search for a parameter or value or whatever that appears
> vaguely like what one (thinks he) needs, and then to try to uncover the
hidden
> service at which the parameter hints. I’ve seen this tendency particularly
in
> the file system area, eg, the IOCTL known only to initiates that will do
> exactly what’s needed and that Microsoft, or whoever, has churlishly not
> documented. Almost always, it’s not so. That temptingly named thing is
either
> misleadingly named, or it is but a tiny piece in a very considerable body
of
> software. I imagine the latter is the case with
> FILE_DEVICE_NETWORK_FILE_SYSTEM, that this is used in a massive component,
a
> remote file system.
>
> I’m not saying you were wrong or mistaken in searching for this parameter
and
> in inquiring. In fact, you took the intelligent, time-saving route of
asking
> others who might know. But beware of parameters that promise magic.
>
> Back to your actual questions: Viscarola and Mason’s book is fine but
dated
> (when’s that update coming, guys?). Today the standard is Walter Oney’s
> “Programming the Microsoft Windows Driver Model,” second edition.
>
> Daniel wrote:
>
> > Basically what I want to do next is write a nice source code control
> > application like clearcase. I would like to write a driver that would
> > allow me to create network drives on a client machine, and then
> > communicate to a service running on a server with the source code
> > repository via sockets. I have looked at the ramdisk example in the
> > Microsoft DDK, and have made it work on NT4, but it doesn’t seem to work
> > on XP. I figure I should call IOCreateDevice with the
> > FILE_DEVICE_NETWORK_FILE_SYSTEM device type, but I have no idea what
IOCTL
> > requests that are going to be made etc etc. I have ordered what seems to
> > be the bible for windows driver development, “Windows NT Device Driver
> > Development”. I was hoping I could get more general direction from this
> > message board.
>
> –
> If replying by e-mail, please remove “nospam.” from the address.
>
> James Antognini
> Windows DDK MVP
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

5

Rajeev’s book provides a file system filter, it certainly doesn’t provide
enough for a file system redirector. One thing not suggest to the origanal
poster was does he need a file system redirector at all, or can he piggyback
on LanMan or WebDAV. This would eliminate the requirement of client kernel
code, and move all the code into user space on the server. There is SAMBA
for LanMan and public domain WebDAV servers that could give the project a
leg up.

If he does want unique semantics that reqiure a file system redirector, I
think the earlier estimates of 12 months for a prototype are potentially
agressive.

Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting

----- Original Message -----
From: “Prokash Sinha”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, November 19, 2003 10:18 AM
Subject: [ntdev] Re: Network File System Driver

> With all the cautions mentioned here, one of the approach would be to
follow
> Rajeev’s book and get a pseudo filesystem driver up and running. The codes
> and example in there is just to explain this beast.
>
> I’ve seen commercial, popular, and might be one of the latest approach to
> source code control system using that direction…
>
> -prokash
>
> ----- Original Message -----
> From: “James Antognini”
> Newsgroups: ntdev
> To: “Windows System Software Devs Interest List”
> Sent: Wednesday, November 19, 2003 6:46 AM
> Subject: [ntdev] Re: Network File System Driver
>
>
> > This is an ambitious project. Heed what Peter Scott said.
> >
> > By the by, let me dwell on the fact that you latched on to
> > FILE_DEVICE_NETWORK_FILE_SYSTEM. There is a tendency, and I’ve done
> exactly
> > this thing, to search for a parameter or value or whatever that appears
> > vaguely like what one (thinks he) needs, and then to try to uncover the
> hidden
> > service at which the parameter hints. I’ve seen this tendency
particularly
> in
> > the file system area, eg, the IOCTL known only to initiates that will do
> > exactly what’s needed and that Microsoft, or whoever, has churlishly not
> > documented. Almost always, it’s not so. That temptingly named thing is
> either
> > misleadingly named, or it is but a tiny piece in a very considerable
body
> of
> > software. I imagine the latter is the case with
> > FILE_DEVICE_NETWORK_FILE_SYSTEM, that this is used in a massive
component,
> a
> > remote file system.
> >
> > I’m not saying you were wrong or mistaken in searching for this
parameter
> and
> > in inquiring. In fact, you took the intelligent, time-saving route of
> asking
> > others who might know. But beware of parameters that promise magic.
> >
> > Back to your actual questions: Viscarola and Mason’s book is fine but
> dated
> > (when’s that update coming, guys?). Today the standard is Walter Oney’s
> > “Programming the Microsoft Windows Driver Model,” second edition.
> >
> > Daniel wrote:
> >
> > > Basically what I want to do next is write a nice source code control
> > > application like clearcase. I would like to write a driver that would
> > > allow me to create network drives on a client machine, and then
> > > communicate to a service running on a server with the source code
> > > repository via sockets. I have looked at the ramdisk example in the
> > > Microsoft DDK, and have made it work on NT4, but it doesn’t seem to
work
> > > on XP. I figure I should call IOCreateDevice with the
> > > FILE_DEVICE_NETWORK_FILE_SYSTEM device type, but I have no idea what
> IOCTL
> > > requests that are going to be made etc etc. I have ordered what seems
to
> > > be the bible for windows driver development, “Windows NT Device Driver
> > > Development”. I was hoping I could get more general direction from
this
> > > message board.
> >
> > –
> > If replying by e-mail, please remove “nospam.” from the address.
> >
> > James Antognini
> > Windows DDK MVP
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@garlic.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@acm.org
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

6

Anybody knows where I can get a copy of R Nagar’s book at a reasonable
price?
I checked some used books on bn and amazone, the sellers asked for $300 an
up.
TIA.

“Peter Scott” wrote in message
news:xxxxx@ntdev…
>
>
> Yeah, for a version control system that would be implemented as a
> filesystem you are a long way from it with Ramdisk. I would start with
> the osronline filesystem faq, then order the ifskit and read all this
> then try to get your hands on a copy of R. Nagar’s book on filesystems,
> though dated it is a great reference. You can then take a seminar on it,
> osr offers a great one.
>
> Estimate ~12 months of effort to get a system up and running, but not
> beta ready, after you have a good idea of what a network filesystem is.
>
> Also try the ntfsd mailing list.
>
> Pete
>
> Peter Scott
> xxxxx@KernelDrivers.com
> www.KernelDrivers.com
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
> Sent: Tuesday, November 18, 2003 9:50 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Network File System Driver
>
> Hi,
>
> I am new to writing drivers but not new to writing Win32 code in C/C++.
> I
> have written a simple driver to get notification on process
> creation/termination, so I am somewhat familiar with IOCTL calls and
> event
> sync from user-mode code to kernel mode code.
>
> Basically what I want to do next is write a nice source code control
> application like clearcase. I would like to write a driver that would
> allow me to create network drives on a client machine, and then
> communicate to a service running on a server with the source code
> repository via sockets. I have looked at the ramdisk example in the
> Microsoft DDK, and have made it work on NT4, but it doesn’t seem to work
> on XP. I figure I should call IOCreateDevice with the
> FILE_DEVICE_NETWORK_FILE_SYSTEM device type, but I have no idea what
> IOCTL
> requests that are going to be made etc etc. I have ordered what seems to
> be the bible for windows driver development, “Windows NT Device Driver
> Development”. I was hoping I could get more general direction from this
> message board.
>
> Thanks in advance for any help.
>
> -Daniel
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@kerneldrivers.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>

7

> I checked some used books on bn and amazone, the sellers

asked for $300 an
up.

Wow! it’s time for me to put my copy to a safer place.

Calvin Guan, Software Developer xxxxx@nospam.ati.com
SW2D-Radeon NT Core Drivers
ATI Technologies Inc.
1 Commerce Valley Drive East
Markham, Ontario, Canada L3T 7X6
Tel: (905) 882-2600 Ext. 8654
Find a driver: http://www.ati.com/support/driver.html

8

A letter to the publisher pointing out this situation may result in a
reprint.

=====================
Mark Roddy

From: Calvin Guan [mailto:xxxxx@ati.com]
Sent: Wednesday, November 19, 2003 1:37 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: Network File System Driver

I checked some used books on bn and amazone, the sellers
asked for $300 an
up.

Wow! it’s time for me to put my copy to a safer place.

Calvin Guan, Software Developer xxxxx@nospam.ati.com
SW2D-Radeon NT Core Drivers
ATI Technologies Inc.
1 Commerce Valley Drive East
Markham, Ontario, Canada L3T 7X6
Tel: (905) 882-2600 Ext. 8654
Find a driver: http://www.ati.com/support/driver.html
http:

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com</http:>

9

> ----------

From: xxxxx@aol.com[SMTP:xxxxx@aol.com]
Reply To: xxxxx@lists.osr.com
Sent: Wednesday, November 19, 2003 6:50 AM
To: xxxxx@lists.osr.com
Subject: [ntdev] Network File System Driver

Basically what I want to do next is write a nice source code control
application like clearcase. I would like to write a driver that would
allow me to create network drives on a client machine, and then
communicate to a service running on a server with the source code
repository via sockets.

Service and sockets communication is everything you need. You don’t need a
driver at all, nor network drives. It is of course possible to implement
filesystem but it would be very hard and unnecessary. The only advantage
would be you could access source code repository the same way as other
(remote) drives without a need for client software. Is it what you want? I
believe client software is necessary in any case because SCC always needs
special actions which don’t have equivalents with classic file operations.
For example, list all versions of a file, get a version N, compare versions
X and Y and so on. It would be possible to use special semantics for these
operations (copy file.c:N) but client softwate solves it as well and more
elegant way.

Also, why to reinvent a wheel? There is a lot of SCC software available now,
good and mature. Personally, I’m satisfied with Perforce (which doesn’t need
any driver).

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

10

Well, it’s not that hard to add SCC-specific stuff to FS. I do it by
using shell extensions (context menu + property page + column extension
/last one sucks big time, though/). Besides, having native access to
SCC-backed files has a value on its own. Like using it for automated
builds, atomic change of content of a disk (we use it to update web
sites) etc.

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Wednesday, November 19, 2003 11:23 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] RE: Network File System Driver

From: xxxxx@aol.com[SMTP:xxxxx@aol.com]
Reply To: xxxxx@lists.osr.com
Sent: Wednesday, November 19, 2003 6:50 AM
To: xxxxx@lists.osr.com
Subject: [ntdev] Network File System Driver

Basically what I want to do next is write a nice source code control
application like clearcase. I would like to write a driver that would
allow me to create network drives on a client machine, and then
communicate to a service running on a server with the source code
repository via sockets.

Service and sockets communication is everything you need. You don’t need
a
driver at all, nor network drives. It is of course possible to implement
filesystem but it would be very hard and unnecessary. The only advantage
would be you could access source code repository the same way as other
(remote) drives without a need for client software. Is it what you want?
I
believe client software is necessary in any case because SCC always
needs
special actions which don’t have equivalents with classic file
operations.
For example, list all versions of a file, get a version N, compare
versions
X and Y and so on. It would be possible to use special semantics for
these
operations (copy file.c:N) but client softwate solves it as well and
more
elegant way.

Also, why to reinvent a wheel? There is a lot of SCC software available
now,
good and mature. Personally, I’m satisfied with Perforce (which doesn’t
need
any driver).

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

11

> ----------

From:
xxxxx@borland.com[SMTP:xxxxx@borland.com]
Reply To: xxxxx@lists.osr.com
Sent: Wednesday, November 19, 2003 8:32 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] RE: Network File System Driver

Well, it’s not that hard to add SCC-specific stuff to FS. I do it by
using shell extensions (context menu + property page + column extension
/last one sucks big time, though/). Besides, having native access to
SCC-backed files has a value on its own. Like using it for automated
builds, atomic change of content of a disk (we use it to update web
sites) etc.

Still don’t see a need of FS. We use automated builds with Perforce which
also supports atomic changes (and web sites updates is one example of use
listed on their web). Everything necessary for automated builds is a command
line utility for SCC control.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

12

“ChuBun” wrote in message news:xxxxx@ntdev…
>
> Anybody knows where I can get a copy of R Nagar’s book at a
> reasonable price? I checked some used books on bn and amazone,
> the sellers asked for $300 an up.

Just for your information - I once came across a full scanned-in
version of it on the Web.

13

You don’t see a need of FS in SCC because there is no need :slight_smile: There
could be a value - that’s for sure. Does the value justify the effort?
Let decide to those who have time and money :slight_smile: In my case the effort
wasn’t that big at all. 8 man-month to prototype and 8 man-month to make
it a product.

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Wednesday, November 19, 2003 11:46 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] RE: Network File System Driver

From:

xxxxx@borland.com[SMTP:xxxxx@borland.com]

Reply To: xxxxx@lists.osr.com
Sent: Wednesday, November 19, 2003 8:32 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] RE: Network File System Driver

Well, it’s not that hard to add SCC-specific stuff to FS. I do it by
using shell extensions (context menu + property page + column
extension
/last one sucks big time, though/). Besides, having native access to
SCC-backed files has a value on its own. Like using it for automated
builds, atomic change of content of a disk (we use it to update web
sites) etc.

Still don’t see a need of FS. We use automated builds with Perforce
which
also supports atomic changes (and web sites updates is one example of
use
listed on their web). Everything necessary for automated builds is a
command
line utility for SCC control.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

14

> ----------

From:
xxxxx@borland.com[SMTP:xxxxx@borland.com]
Reply To: xxxxx@lists.osr.com
Sent: Wednesday, November 19, 2003 9:59 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] RE: Network File System Driver

You don’t see a need of FS in SCC because there is no need :slight_smile: There
could be a value - that’s for sure. Does the value justify the effort?
Let decide to those who have time and money :slight_smile: In my case the effort
wasn’t that big at all. 8 man-month to prototype and 8 man-month to make
it a product.

Is this product available somewhere? I would be interested to see brief
description with screenshots (only, no time to test).

With enough time and money it is of course interesting project. There is a
value for sure. I just wonder if there is any advantage against classic
approach. Assume both GUI and command line client and server supporting
atomic operations.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

15

Go have a look at what people are selling their NT File System Internals
copy for; Helens book

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Wednesday, November 19, 2003 10:56 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: Network File System Driver

A letter to the publisher pointing out this situation may result in a
reprint.

=====================
Mark Roddy

From: Calvin Guan [mailto:xxxxx@ati.com]
Sent: Wednesday, November 19, 2003 1:37 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: Network File System Driver

I checked some used books on bn and amazone, the sellers
asked for $300 an
up.
Wow! it's time for me to put my copy to a safer place.

Calvin Guan, Software Developer xxxxx@nospam.ati.com
SW2D-Radeon NT Core Drivers
ATI Technologies Inc.
1 Commerce Valley Drive East
Markham, Ontario, Canada L3T 7X6
Tel: (905) 882-2600 Ext. 8654
Find a driver: AMD ׀ together we advance_AI

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

16

Actually, guys, you can go offshore. :slight_smile:

From
http://www.amazon.co.uk/exec/obidos/ASIN/1565922492/ww2afvportainass/202-199
9407-6351021
http:99407-6351021> : 85 pounds.
From http://www.amazon.fr/exec/obidos/ASIN/1565922492/402-1880132-7464105
http: :
62.70 Euros new, 33 Euros used.

I’m sure if I search more I’ll find other good offers. That’s a lot less
than 300 bucks !

Alberto.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Jamey Kirby
Sent: Wednesday, November 19, 2003 8:33 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: Network File System Driver

Go have a look at what people are selling their NT File System Internals
copy for; Helens book

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Wednesday, November 19, 2003 10:56 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: Network File System Driver

A letter to the publisher pointing out this situation may result in a
reprint.

=====================
Mark Roddy

_____

From: Calvin Guan [mailto:xxxxx@ati.com]
Sent: Wednesday, November 19, 2003 1:37 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: Network File System Driver
> I checked some used books on bn and amazone, the sellers
> asked for $300 an
> up.
Wow! it’s time for me to put my copy to a safer place.

Calvin Guan, Software Developer xxxxx@nospam.ati.com
SW2D-Radeon NT Core Drivers
ATI Technologies Inc.
1 Commerce Valley Drive East
Markham, Ontario, Canada L3T 7X6
Tel: (905) 882-2600 Ext. 8654
Find a driver: http://www.ati.com/support/driver.html
http:
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.</http:></http:></http:>