VXD technology (2)
Is VxD still beautiful tomorrow?
At the 1996 Windows Hardware Engineering Conference (Winhec) meeting, Microsoft announced a new Windows Device Driver Model --Win32 Driver Model (WDM). This new device driver model will become the core of Windows 2000 (ie Windows NT 5.0).
This message is frustrated by people engaged in Windows Device Drivers (VXD) (although everyone has already expected to come together with the Windows NT series). The WDM's floating surface pushed a bitter VXD developer to a new starting line. If you have went to DDK's assembly code, you must experience this news to the VXD developer is a heavy blow, but for the Windows NT device driver, it is another mood. - Because WDM is basically equal to KERNEL MODE Driver Plug and Play.
VXD will make We deliver, which makes us gratifying, Microsoft announces that Windows 98 (Windows 98 support VXD) may insist on 200X, and the birth of Windows 2000 may be in 2000. During this time, you can also take the initiative to ask the boss to pay the boss. Even when the WDM is unified, it is not discouraged because both VXD is still WDM, which requires developers to have a comprehensive and meticulous understanding of computer hardware. Through VXD exercise, you are at least familiar with the computer's hardware resources and have a deep understanding of the protection mode. These things are hard work in WDM development in the future.
Ok, I should talk about Windows NT. In Windows NT, "protection" of 80386 protection mode is more robust than Windows 95, and this "gold-plated cage" is more strong and difficult to break. In Windows 95, at least the application I / O operation is unrestricted, and in Windows NT, our applications have been deprived.
Windows NT driver model is completely different from Windows 3.1, Windows 95. So, if someone tells you, his machine running Windows NT is destroyed by CIH. You can charge an expert, lesson he: "This is impossible, remember, CIH uses VXD technology, while VXD It is running in Windows NT. "
In Windows NT, there are three Device Driver:
1. "Virtual Device Driver" (VDD). Through VDD, 16-bit applications, such as DOS, and Win16 applications, you can access specific I / O ports (note, not directly access, but to implement access vdd).
2. "GDI DRIVER", provides the GDI function required to display and print.
3. "Kernel Mode Driver" implements the operation of specific hardware, such as CREATEFILE, CloseHandle (for file objects), readfile, writefile, deviceioControl, etc. "Kernel mode driver" or the only Driver that can operate on hardware interrupts and DMA in Windows NT. SCSI MiniPort Driver and NIC NDIS Driver are a special form of Kernel Mode Driver. Ok, let's talk about it, I know very little about Kernel Mode Driver.
If you are interested in the development of Windows device drivers, I suggest you go to the following Web site.
http://hejiasheng.363.net/tppmsgs/msgs0.htm#6
Vireo Software (VToolsd) Home Page
http://hejiasheng.363.net/tppmsgs/msgs0.htm#7
Dan Norton "S DDK Resource Page
http://hejiasheng.363.net/tppmsgs/msgs0.htm#8
Microsoft Home Page
http://hejiasheng.363.net/tppmsgs/msgs0.htm#9
O "REILLY Associates Home Page
http://hejiasheng.363.net/tppmsgs/msgs0.htm#10
Nu-Mega Technologies (Soft-Ice) Home Page
http://hejiasheng.363.net/tppmsgs/msgs0.htm#11
Windows Hardware Technical Information for IHVS AND OEMS
http://hejiasheng.363.net/tppmsgs/msgs0.htm#12
Blue Water Systems (WinRT) Home Page
http://hejiasheng.363.net/tppmsgs/msgs0.htm#13
Universal Serial Bus Home Page
http://hejiasheng.363.net/tppmsgs/msgs0.htm# 14
DDK Annotations
