Windows 2000 Device Driver Development Guide

5星 · 超过95%的资源需积分: 9 182 浏览量更新于2024-07-30 3 收藏 6.08MB PDF 举报

"The Windows NT Device Driver Book" 是一本由 Art Baker 和 Jerry Lozano 合著的专业书籍，专注于介绍如何为Windows操作系统编写设备驱动程序。这本书的第二版于2000年11月20日发布，由Prentice Hall PTR出版社出版，拥有480页的内容，专门针对Windows 2000系统进行了全面更新，同时也适用于Windows 98。书中涵盖了Windows Driver Model (WDM)的详细内容，这是Windows 2000及后续版本中用于设备驱动程序开发的主要框架。书中的主要内容包括： 1. **设备驱动程序的规划与实现**：为读者提供构建驱动程序的逐步指导，从前期规划到实际编写代码，再到测试、调试和安装的全过程。 2. **Windows Driver Model (WDM)**：深入解析WDM，它是Windows 2000中引入的新模型，支持Plug-and-Play（即插即用）和Power Management（电源管理）功能，使得驱动程序能更好地适应现代硬件环境。 3. **调试与问题解决**：提供了实用的调试技巧和交互式故障排除方法，帮助开发者在遇到问题时能快速定位和解决问题。 4. **CD-ROM附赠内容**：随书附带的CD-ROM包含了专为驱动程序开发设计的工具，以及丰富的C/C++样本驱动程序库，加速开发进程。 5. **安全的再入代码构造**：讲解如何编写安全的、可重入的驱动代码，避免因多线程或并发访问导致的问题。 6. **处理超时条件**：介绍如何安全有效地处理可能发生的超时情况，确保系统的稳定性和响应性。 7. **高级技术**：涵盖内核模式线程、分层驱动等进阶技术，为有经验的开发者提供了更深层次的学习资料。 8. **Windows Management Instrumentation (WMI)**：讨论了如何利用WMI记录设备错误和事件，并解释如何解读这些信息，以便进行系统监控和诊断。 9. **调试与故障排查技术**：提供了一整套从头到尾的调试和故障排查策略，帮助开发者解决开发过程中遇到的各种问题。这本书是Windows驱动程序开发者的必备参考书，无论是新手还是经验丰富的开发者，都能从中受益匪浅，提升自己的技能和效率。通过阅读本书，开发者可以掌握构建高效、稳定且兼容性强的设备驱动程序所需的知识和实践方法。

< BAC K NEXT >

[oR]

Acknowledgments

I am grateful to many people who helped me with this 2nd edition. First and foremost, I want to thank

Art Baker for his original work. The structure and content of this revision is based on his initial

efforts.

To my partner in life, Carol, who makes everything possible. I thank Carol for both her personal and

professional support. Without your encouragement, I would never have started this project. Without

your help, I would never have finished.

Thanks to Russ Hall, my development editor and friend, for making the book sound good.

Thanks to Patty Donovan and her staff at Pine Tree Composition for making the book look good.

The staff of Prentice Hall PTR, especially Mike Meehan and Anne Trowbridge, deserve considerable

credit for their patience and encouragement in leading me through the entire process.

I wish to thank Bryce Leach of Texas Instruments who tried to correct my misunderstandings of

IEEE 1394. Your comments and suggestions for Chapter 2 were invaluable.

Thanks to Ron Reeves, for several great technical comments on several chapters.

And finally, thanks to the many people who attend my seminars, workshops, and classes for asking

all those wonderful, thought-provoking questions.

< BAC K NEXT >

This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks .

To achieve the robustness and reliability goal, the designers of NT chose a client-server architecture for its

core implementation. A user application runs as a client of OS services.

The user application runs in a special mode of the hardware known generically as user mode . Within this

mode, code is restricted to nonharmful operations. For example, through the magic of virtual memory

mapping, code cannot touch the memory of other applications (except by mutual agreement with another

application). Hardware I/O instructions cannot be executed. Indeed, an entire class of CPU instructions

(designated privileged ), such as a CPU Halt, cannot be executed. Should the application require the use of

any of these prohibited operations, it must make a request of the operating system kernel. A

hardware-provided trap mechanism is used to make these requests.

Operating system code runs in a mode of the hardware known as kernel mode . Kernel-mode code can

perform any valid CPU instruction, notably including I/O operations. Memory from any application is

exposed to kernel-mode code, providing, of course, that the application memory has not been paged out to

disk.

All modern processors implement some form of privileged vs. nonprivileged modes. Kernel-mode code

executes in this privileged context, while user-mode code executes in the nonprivileged environment. Since

different processors and platforms implement privileged modes differently, and to help achieve the goal of

portability, the OS designers provided an abstraction for user and kernel modes. OS code always uses the

abstraction to perform privileged context switches, and thus only the abstraction code itself need be ported

to a new platform. On an Intel platform, user mode is implemented using Ring 3 of the instruction set, while

kernel mode is implemented using Ring 0.

This discussion is relevant to device driver writers in that kernel-mode drivers execute in a privileged

context. As such, poorly written device driver code can and does compromise the integrity of the Windows

2000 operating system. Driver writers must take extra care in handling all boundary conditions to ensure

that the code does not bring down the entire OS.

Portability

To achieve the portability goal, NT designers chose a layered architecture for the software, as shown in

Figure 1.1.

Figure 1.1. The layers of the Windows 2000 operating system

This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks .

剩余543页未读，继续阅读

rock178

粉丝: 3
资源: 8

Windows 2000 Device Driver Development Guide

Windows+NT+技术内幕(第二版） part1

Windows NT 4.0 SP6 中文版 iso格式

linux device driver

Windows NT 4.0 简体中文版.ISO.fs04

windows NT4.0 USB 驱动

Linux device driver中文版.pdf

Windows NT 4.0 简体中文版.ISO.fs013

Windows 2000 Device Driver Book(英文版)

Windows NT Device Driver Book(中文,超星pdg格式)

Windows NT 4.0 简体中文版.ISO.fs09

最新资源