VXD technology (1)
Speaking of VXD technology, many people who have exposed to computer will feel unfamiliar, but mentioning CIH viruses, I believe you must no longer shook your head.
People who have a certain Windows programming experience may hear vxd. The protection model of 80386 gave us a lot of "protection", for people who have pursued freedom, "gold-plated cage is also a cage", fluttering about Windows programming, perhaps ultimately find such a universal freedom Door: Try a try vxd.
What is VXD? Why will CiH be so embarrassing?
CiH runs in Ring 0, hooks the IFS (Installable File System) service, intercepting the file opening operation, then "infect" to other files in other PE formats, if it comes to the time of the episode, it attacks the motherboard's Flash Memory .
The reason why CiH can damage hardware resources (by attacking the motherboard's flash memory, the purpose of destroying hardware) is because it utilizes VXD technology. For a general running Windows application, it is impossible to destroy the motherboard, because this is the 80386 protection mode is not allowed for code permissions. The result is mostly caused by operating system. , That is, in Windows, it is often accelerated, and the blue bottom is white.
Vxd = Virtual "Something" Device, the x represents Something. For example, VKD represents Virtual Keyboard Device (Keyboard Drive), VPICD represents Virtual ProgramMable Interrupt Device. VXD is the driver model of Windows 3.1, Windows 95 (Windows 98 also supports VXD).
In many people's impression, VXD is dealing with hardware devices. It is not too much for software. One of whose reasons are: DDK used to develop VXDs Generally, it is distributed to hardware developers, for software The people developed, SDK is to look at the family, and the SDK is very little about VXD. This idea is a big fault.
Since VXD runs in the system's RING 0, with the same level as the operating system, VXD can maximize us to get out of the 80386 protection model to impose our "gold-plated cage." We took a very sensational CIH virus to say that the power of the sword of VXD. "General Protection Fault", here, we should thank the "gold-plated cage", at least it prevents us from the neighbor's children who have learned Turbo C programming.
What can VXD can be used for destruction?
Here I simply talk about the application of VXD.
Since VXD can virtually at all hardware, therefore, you can use vxd virtual hardware dog to crack some copyright software protection (how is it dry? I just want to tell the hardware dog's manufacturer: Some ghosts want to pass this The means to save money, early work!).
Since VXD works at the bottom of the operating system, master it enables you to extend your operating system. Have you ever thought about pressing the Ctrl Alt Delete button in Windows 95, then popping up is your own dialog box (smart, you must play your genius imagination, such as showing photos of your girlfriend to remind yourself After I don't forget to go to the date after the computer), VXD can help you open it with Windows 95. Ok, let's talk about it. Do you want to use VXD to do something such as "real-time" control? Of course, doing real-time industrial control, the preferred operating system or DOS, but if you can't get the temptation of the beautiful face of Windows, you can also work as "accurate real-time" control applications on Windows. In general, through VXD assistance, in many cases, we can still get a more satisfactory real-time effect. According to the test, the 486/66 PC runs Windows 95 on the PC, and if there is no other application interference, VXD can handle 10kHz hardware interrupt, and will not miss an interrupt! Carefully design your app and vxd (it is best to buy a good computer), I believe you can get a satisfactory "real-time" effect.
Tell a fun application (I am a little dizzy today, I don't love the braggy.). If you have a pile of 16-bit DLL, (assuming that you have made the application development in Windows 31, and have written a lot of functional DLLs for the boss, and you are too lazy to pass the code Or use the cumbersome thunk to move down to Windows 95, then try the VXD, you may give you the experience of "Its Mountain stone to attack jade". Of course, my premise is that you have more knowledge of VXD and some actual experience, otherwise you will probably cause neurasthenia.
A more interesting application is said. I don't want to make some cooperation between DOS TSR, WIN16 applications, Win32 applications? Do you want to break the limit of Win32 application 4GB independent linear address space? Through VXD, you will find that the original "10,000 things are passed by one". Don't believe that the authority "No" sitting opposite you, I believe yourself.
For VXD, we have already said enough, maybe you have been excited to go to the bookstore to find this "21st and easy to master VXD technology" is fast. First quiet, now start pouring cold water
