Windows NT File System Internals：A Developer's Guide 精美完整版（附随书源码）要这本书的看这里

    做驱动程序开发，好书是一定少不了的，今天也来给驱动开发论坛做下贡献，把我的珍藏级好书奉献给所有热爱驱动程序开发的朋友们，没有广告，没有密码，没有次数，没有速度限制，不过下载后请一定爱惜哟。
    书名:<<Windows NT File System Internals：A Developer's Guide 精美完整版（附随书源码）>>，迄今为止唯一的一本专门讲述文件系统驱动程序的著作，共12M多，分4个压缩包。
    站点:阿荣小站:[url] http://www.ronggang.533.net[/url]->"其它作品"->"更多作品"->"程序开发"栏中，有需要的朋友前去下载吧，请用网际快车等下载工具下载，直接另存是不能成功的，下载速度爆快。我会慢慢把我珍藏的其它好书放上去的，欢迎朋友们经常来逛逛。
    从此以后，希望网上不会再有找本书电子版的贴子了。
    喜欢本书的，不要只顾下载，请顶一下!

fzx_qd朋友，是否是用网际快车下载呢?硬盘上空间是否足够?我刚才又试了一下，4个链接下载非常正常!速度爆快，没有出现连不上的情况呀。我选用是非常稳定的服务器，不会出现下不了的情况吧!本人主要是想给驱动论坛的朋友们做件好事，如果下载不了，就有违我的初衷了，你可以再试试。谢谢你的回复!我会奉献更多的好书，请有空常来逛逛!

啊，连qtzp.htm都打不开，那我没办法了，我每次都能打开的。你可以晚些再试试看，应该没问题，533.net的服务器还是比较稳定的哟。这个电子版是我从国外一家网站上收集来的，我们公司就有这本书，我对比了一下，非常完整，扫描得也很不错，应该是可以满足收藏的需要了，楼上说的其它版本我没有下过，不知道是不是这个版本，没法比较。另我也将原书配套光盘一并打包，提供下载，所以应该是完整版了。各位不要怀疑，纯粹是无偿提供，提供给需要的朋友，闲人免下!

各位还是打不开，我郁闷，试试这两个网址呢:
http://ronggang.html.533.net/或http://ronggang.533.net

首页应该如下图，是不是没有安装flash插件，完全可以理解你急迫的心情，我也是真心想帮大家，来，这个网址应该没问题，祝好运!
http://ronggang.html.533.net/qtzp.htm

呵呵，也好，差那些页报上来，我来给大家做做好事!

还是有不少热心人呀，明天就会有好消息，敬请期待!

152页:
stored in the UserApcContext field. Some examples of asynchronous system services are directory control, read, write, and lock operations. Note that create/open requests are always processed synchronously, and therefore the AllocationSize field and the AsynchronousParameters form part of the Overlay union structure.

For I/O operations that involve transferring data, the caller supplies a data buffer. This buffer might serve as an input buffer, an output buffer, or both. In any case, the I/O Manager initializes the UserBuffer field with the caller-supplied buffer pointer before invoking IoCallDriver(). Upon IRP completion, if there is any data that needs to be copied back to the caller's buffer, the I/O Manager performs this function as part of postprocessing done on the IRP. If your driver does not specify either direct I/O or buffered I/O as the preferred method of user buffer manipulation, the I/O Manager will assume that you will handle the user-supplied buffer yourself and will therefore not allocate an MDL, or supply your driver with a system address. Your driver can subsequently use the buffer pointer in the UserBuffer field directly.[15]

Tail
An IRP has a Tail structure defined as follows:
union { struct { KDEVICE_QUEUE_ENTRY DeviceQueueEntry; PETHREAD Thread; PCHAR AuxiliaryBuffer; LIST_ENTRY ListEntry; struct _IO_STACK_LOCATION *CurrentStackLocation; PFILE_OBJECT OriginalFileObject; } Overlay; KAPC Apc; ULONG CompletionKey; } Tail;


This structure consists of fields that are manipulated and accessed directly only by the NT I/O Manager. It is not recommended that your driver try to directly access the contents of these fields.

The DeviceQueueEntry field is used to queue IRPs for a specific lower-level driver. Most lower-level drivers allow the NT I/O Manager to maintain a list of pending I/O Request Packets. The I/O Manager uses the DeviceQueueEntry field to queue the packet for the target device object, if the device object is found to be busy when IoStartPacket() is invoked by the device driver dispatch


153页:
routine. The DDK describes the IoStartPacket(), IoStartNextPacket(), and IoStartNextPacketByKey() support routines, which manipulate this field. Kernel-mode drivers should not try to directly access or manipulate the contents of the DeviceQueueEntry field.

Before dispatching an IRP, the I/O Manager initializes the Thread field to point to the thread in whose context the dispatch will occur. This field is subsequently used by both lower-level drivers and file system drivers.

Consider the situation when a hard error occurs. File systems use the IoRaiseInformationalHardError() call to place a pop-up message box on the system console to notify the user of the error situation. This call is blocking and it displays the error by delivering a special kernel APC to the target thread. The problem is that the thread in whose context the message box is displayed is blocked until a user physically dismisses the error message from the system console. If, however, no thread is specified in the argument list to the IoRaiseInformationalHardError() routine, the error message is delivered in the context of a special (single) system worker thread.

Typically, if an error occurs, a kernel-mode driver will examine the Overlay.Thread field to determine if the thread is a system worker thread. If it is, then the driver will send in a NULL Thread argument to IoRaiseInformationalHardError(), because blocking system worker threads for an indefinite amount of time is clearly unacceptable.

Another instance when the Thread field assumes importance is in the handling of removable media. If a user-induced error occurs when reading/writing removable media, the lower level device driver uses the IoSetHardErrorOrVerifyDevice() routine to indicate that something unexpected has occurred and that higher-level drivers should either report an error to the user or verify that the media in the drive is correct. In response to this call, the I/O Manager simply stores the device object to be verified in the DeviceToVerify field for the thread object pointed to by the Overlay.Thread field in the IRP. The higher-level (file system) driver subsequently invokes IoGetDeviceToVerify(), supplying the thread object pointer obtained from the Overlay.Irp field, and the I/O Manager, in response, hands back the stored device object pointer.

Note that the IoAllocateIrp() I/O Manager service routine does not set the Thread object in the returned IRP. This is the responsibility of the caller of this routine.

The AuxiliaryBuffer exists supposedly to pass additional information to a kernel-mode driver that is not contained elsewhere in the IRP. However, at this point, none of the I/O Manager routines use this field to pass information to a kernel-mode driver.[16]

我刚从网上收集到Chapter 4(The NT I/O Manager)的全部内容，比较完整，包括了原书的117-193页，需要的可以在我的站上去下来看。其它的页67，196，460，356，357，358我有空会上传上来，但我看了一下，原书的pdf版，丢失较多，限于本人精力有限，恐难全部扫描，还请谅解。

本人已经利用业余时间，将67，196，460页扫描上载，有需要的可以去我的小站下载，356，357，358原书中就不存在，各位不要以为是掉了页。

第三部分:
Sun Jul 18 20:20:31 2004 正在连接 3.csx.jp:80
Sun Jul 18 20:20:31 2004 正在连接 3.csx.jp [IP=221.251.37.14:80]
Sun Jul 18 20:20:31 2004 已连接.
Sun Jul 18 20:20:31 2004 GET /ronggang/book/Windows%20NT%20File%20System%20Internals：A%20Developer's%20Guide%20精美完整版（附随书源码）.part3.rar HTTP/1.1
Sun Jul 18 20:20:31 2004 Host: 3.csx.jp
Sun Jul 18 20:20:31 2004 Accept: */*
Sun Jul 18 20:20:31 2004 Referer: http://soft.winzheng.com/SoftView/SoftView_19184.htm
Sun Jul 18 20:20:31 2004 User-Agent: Mozilla/4.0 (compatible; MSIE 5.00; Windows 98)
Sun Jul 18 20:20:31 2004 Pragma: no-cache
Sun Jul 18 20:20:31 2004 Cache-Control: no-cache
Sun Jul 18 20:20:31 2004 Connection: close
Sun Jul 18 20:20:36 2004 HTTP/1.1 200 OK
Sun Jul 18 20:20:36 2004 Date: Sun, 18 Jul 2004 12:19:33 GMT
Sun Jul 18 20:20:36 2004 Server: Apache/2.0.48 (Unix)
Sun Jul 18 20:20:36 2004 Last-Modified: Wed, 07 Jul 2004 07:33:35 GMT
Sun Jul 18 20:20:36 2004 ETag: "5bf1c8-2dc6c0-c9ad31c0"
Sun Jul 18 20:20:36 2004 Accept-Ranges: bytes
Sun Jul 18 20:20:36 2004 Content-Length: 3000000
Sun Jul 18 20:20:36 2004 Connection: close
Sun Jul 18 20:20:36 2004 Content-Type: text/plain
Sun Jul 18 20:20:36 2004 开始接受数据!
第四部分:
Sun Jul 18 20:21:41 2004 正在连接 3.csx.jp:80
Sun Jul 18 20:21:41 2004 正在连接 3.csx.jp [IP=221.251.37.14:80]
Sun Jul 18 20:21:41 2004 已连接.
Sun Jul 18 20:21:41 2004 GET /ronggang/book/Windows%20NT%20File%20System%20Internals：A%20Developer's%20Guide%20精美完整版（附随书源码）.part4.rar HTTP/1.1
Sun Jul 18 20:21:41 2004 Host: 3.csx.jp
Sun Jul 18 20:21:41 2004 Accept: */*
Sun Jul 18 20:21:41 2004 Referer: http://soft.winzheng.com/SoftView/SoftView_19184.htm
Sun Jul 18 20:21:41 2004 User-Agent: Mozilla/4.0 (compatible; MSIE 5.00; Windows 98)
Sun Jul 18 20:21:41 2004 Pragma: no-cache
Sun Jul 18 20:21:41 2004 Cache-Control: no-cache
Sun Jul 18 20:21:41 2004 Connection: close
Sun Jul 18 20:21:44 2004 HTTP/1.1 200 OK
Sun Jul 18 20:21:44 2004 Date: Sun, 18 Jul 2004 12:20:41 GMT
Sun Jul 18 20:21:44 2004 Server: Apache/2.0.48 (Unix)
Sun Jul 18 20:21:44 2004 Last-Modified: Wed, 07 Jul 2004 07:34:57 GMT
Sun Jul 18 20:21:44 2004 ETag: "5bf1c9-2bcc2c-ce906a40"
Sun Jul 18 20:21:44 2004 Accept-Ranges: bytes
Sun Jul 18 20:21:44 2004 Content-Length: 2870316
Sun Jul 18 20:21:44 2004 Connection: close
Sun Jul 18 20:21:44 2004 Content-Type: text/plain
Sun Jul 18 20:21:44 2004 开始接受数据!
我每次下都很正常呀!

zhangc98朋友，我就不发到你的信箱了，自己在这里下吧:

birdtomaster有朋友，还有其它朋友们，我本打算做件好事，将自己的好书送给大家学习，但不知各位为什么不能下载，我每次都可以!我也试图将3，4部分上传到本论坛来，上传N次，均以失败告终，又申请了其它空间上传，终因附件太大，再次失败，今天只有申请了一个邮箱，把1至4部分保存在收件箱里，有需要的从邮箱中取吧，如果各位还是不能下载，我已经尽力了，请各位从其它渠道获取本书，我已经无能为力。祝各位好运。恕我不方便在此公布自己的私人邮箱。请到我的留言本上查找邮箱名称及地址。

 从主页[url]http://ronggang.html.533.net/index.html [/url]点"给我留言"进入
不能打开主页的从这里[url]http://www.533.net/cutebook/?act=post_list&userid=14219 [/url]进入
下载后，如果成功，请回复一下，便于我统计朋友的人数，另请勿删除邮件，以方便其它朋友下载，我将不再补齐邮件内容。

最近空间比较紧张，很多免费空间都关闭了，我的主页也没有幸免，有需要本书的朋友，从这里 http://rong_gang.xyinfo.net/进入吧，主力站点暂时不能访问，镜像站可以下载，祝各位好运!

[编辑 -  8/4/04 by  ronggang]

不幸呀，二级域名.1230.net也关闭了，只有这个了: [url] http://rong_gang.xyinfo.net/[/url]

    哎，最近中国正进行着一场轰轰烈烈的打击非法网站的运动，不问青红皂白，一录杀光，株连九族，也是最擅长的手段，无数个人网站纷纷倒下，多少人的心血都付之东流，覆巢之下，安有完卵，在下的小站也到了濒临瘫痪的边缘。
    但只要真正需要本书的朋友存在，我就要保证本书的链接真实可用，为此无论我付出多大的努力也再所不惜，以下是本人重新开通的域名:
http://www.ronggang.te8.com
或
http://ronggang.te8.com
还是那句老话，永远免费提供给需要的朋友，闲人免进，谢谢!    

[编辑 -  8/12/04 by  ronggang]

[编辑 -  8/12/04 by  ronggang]

各位能得到自己心仪已久的好书，也为各位感到高兴。我会继续保证链接的有效性(每日检查)，为更多需要的朋友提供帮助。好东西要和朋友分享，才是最快乐的事!祝好运!

你来得这么凑巧,就在你下载的这一天,给我小站提供空间服务的服务商刚好暂停了服务,所以下载不了.不过没关系,我已经准备了另外的下载地址,请登陆我的论坛,查看《请驱动开发论坛的朋友们看这里》的贴子,你会找到你要的东西.不过,要下载的还是请快些,终究本站使用的是免费资源,本人已经尽了最大的努力来保证各位能下载到本书.请尽快下载,好好爱惜.
我的论坛:
[url] http://www.masonry.cn/cgi-bin/list.cgi?user=ronggang [/url]

[编辑 -  10/29/04 by  ronggang]

缺页补齐部分已经做为附件上传到本主题,请看看我前边的回复,就可以直接下载了.祝好运!