Many people are interested in driver development, but they often can't find the correct learning method. Of course, this has little to do with the localized materials that drive development. Most of the learning materials for driver development are mainly in English, which makes many beginners of drivers have a headache. I have been engaged in driver development for a short time, about 3-4 years. Most people think that people who will drive development are cattle people, experts and the like. In fact, that's not how experts define cowboys. Before learning-driven development, we must understand a truth: there are specialties in the industry, so don't blindly follow suit. [This content applies to environment and tools]1> 2> Version of Windows Driver Development Kit (DDK (old version) and WDK (new version) higher than VS2003 3 > 4> has the ability to install VMWare[ this content applies to groups]1>; People with C/C++ language foundation 2 >; People with 80x86 assembly foundation 3 >: logical thinking with high school education or above [with Windows system theory books]1> Windows kernel programming 2 > Win32 multithreading programming 3 >: in-depth analysis of Windows operating system 4 >; Windows operating system principle FAQ 1: Why do you need these four books [with Windows system theory books]? A: Driver is an important part of Windows system, which goes deep into the core of Windows system. Because the drive is closely related to the core of the system, it involves many basic theories and principles of the system. Therefore, before learning-driven development, we must first understand the basic development theory and operation principle of Windows system. The architecture of windows system. Then the four books I have provided above are the most classic and comprehensive books on the market at present. [Windows Driver Development Book]1> Detailed explanation of Windows driver development technology 2 & gtWindows device driver WDF development FAQ2: Why do you need these two books [Windows driver development books]? A: Suppose you have a solid understanding of the basic theory of Windows system, have read the four books mentioned above [Windows System Theory Books], and have experience in developing Windows programs or large-scale programs, then you need a classic driver introduction development book to get started correctly when you enter Windows driver development. Now I have provided these two books [Windows Driver Development Books] which are completely aimed at the introduction of Windows driver development. Of course, I recommend it first; So far, the contents of this book explain the driver development very well. Including drive development theory, drive system configuration, etc ... This is a rare good book. So the second book is actually a bit lame, but it involves the explanation of the latest driver development theory WDF, so you can make do with it. [Windows Debugging Basic Theory Books] Software Debugging 2> Efficient Debugging of Windows User Mode Programs FAQ3: Why do you need these two books [Windows Debugging Basic Theory Books]? A: In the case of developing a driver, you have to debug the driver. So how to debug the driver? Windows has considered this problem for you and developed a powerful debugging tool: Windbg. How to learn how to debug this tool? So now only these two books are still explaining Windbg on the market, at least for the use of debugging commands, there are already Chinese explanations. You can have a general understanding of the debugging command of Windbg through two books, and then further GOOGLE search and in-depth study. [Compilation of Basic Theory Books]1> Author of assembly language: Wang Shuang 2 & gt80x86 Assembly Language Programming Course [Green or Black Edition] FAQ4: Why do you need these two books [with basic theory of assembly]? A: Because the driver is developed in the Windows environment, there is a drawback, that is, there are few WDK and DDK documents in Windows, and many descriptions are vague. Therefore, the driver we developed is extremely unstable, and we need the mechanism of reverse Windows driver to deepen our understanding. When the driver is unstable, it will lead to a blue screen of the system, and sometimes the error will not be directly located in your code. At this time, it is necessary to assemble to analyze the cause of the error. As I mentioned earlier, debugging technology is basically described in assembly language. [Driver Development Extension]1> Fishing alone in the cold river -Windows kernel security programming 2 > Windows kernel principle and implementation 3 >: Rootkit Windows kernel security prevention 4 >; Windows kernel scene analysis FAQ5: Why do you need these four books [driver development extension books]? A: As the saying goes, learning is endless, and the field of driver development is a huge system, which is determined by the diversity of driver frameworks. Drivers include: file drivers, disk drivers, graphics drivers, network drivers and so on. Each category is a field, and you decide that your ability needs to be extended to many aspects, so you can consider learning from the four books I provided first. By reading these three books, you will find that drivers can do many unexpected things. I have been engaged in developing drivers for nearly 4 years, only involving file drivers, disk drivers and some small drivers. I just study selectively according to my needs. Everyone has his own ability limit, so everyone should do what he can. [Recommended correct learning method]1> Read the reference books I provided carefully. Use Google more to solve your problems. 3> Try to write your favorite functions with drivers. 4> Improve your English reading ability, because 5 > valuable materials come from foreign countries. Don't rush for success, don't be impetuous, and don't show off the driver development technology.