Rapid development of VXD with VC6.0 integrated environment

The VxD (virtual Device Driver), the dummy device driver, is a driver running at the processor RING0 privilege level that can execute any processor instructions to access any data registers in the machine. VXD is used as an interface between Windows 9x systems and physical devices, extending the core services of Windows systems to access and control the actual hardware environment.

With the launch of Win 2000 and the next generation of device driver WDM (Windows Driver Model), the VxD is expected to slowly become obsolete, but the reality is: a random opening of a Network counter statistics window will find that the Windows 98 system still occupies 90% The above market share. How to master a time-saving and efficient way to develop VxD has become an urgent problem for programmers to solve.

Reviewing the traditional method, using Microsoft's DDK to write VxD, is a very lengthy process:

1 edit code unexpectedly no graphical interface, or in the DOS command line with Edit,edit does not support multiple windows, view, replace the code is very inconvenient.

2 compilation can only use VC5.0, but can not use the VC6.0. In the win-DDK help, the System Requirements section, Microsoft clearly reminds you that this is the Visual C + + 6.0 isn't supported for any of the samples.

3 to static VxD, each rewrite code, need in the System.ini file, on the section [386ENH] plus one line: device= vxd filename, each rewrite, to restart the computer, each time after a long wait process, it is unbearable.

How to solve the above 3 problems, the author only on the experience gained in the work, talk about using VC6.0 integrated environment rapid development of VxD method, hope to bring some help.

In the development of protective flower messenger anti-yellow software, the author adopts vtoolsd 3.0来 to write File Protection VxD module.

VTOOLSD 3.0 is a software package developed by the Compuware Company and includes several utilities:

1. Quickvxd: Create a VxD C and C + + language framework that supports not only VC5.0 and VC6.0, but also Borland C + + 5.x. Similar to VC's AppWizard, Quickvxd is equivalent to a code generator, unlike AppWizard uses MFC class libraries to generate program frameworks, and Quickvxd uses a series of custom macros and classes to generate the program framework.

2. Debug Monitor: Dynamic loading and unloading and display VxD debugging information, not only can load dynamic VxD, but also can load static VxD, after loading debugging completed, whether dynamic or static VxD, can be unloaded at any time. This is a strong enough to make Microsoft ashamed of the powerful features, successfully avoided writing static VxD every time to restart the trouble, to the programmer to bring great convenience.

3. VxdVer.exe:DOS command line tool, you can set the version information for a VxD. This gadget is also important because the VxD version information cannot be set with VC6.0 and can only be set manually by Vxdver.

The following is a detailed introduction to the rapid development of a VXD with the VC6.0 integrated environment:

First, use Quickvxd to generate a VxD frame program, click: Start Menu/numega vtoolsd/quickvxd, open Quickvxd, select Device Parameters, set device Name =my, select output Files, and then press the Generate Now button to generate the VxD frame source, which includes 3 files: a header file with the suffix. h, a code file with a. c or CPP suffix, and a. Mak project file. Then, we copy the 3 files: MY.h, MY.cpp, and My.mak to the E:\my\ directory. The traditional way to generate a VxD on the command line is as follows:

Click: Start Menu/development kits/windows ddk/checked (free) build environment,

To set up the compilation environment, on the DOS command line, locate the My. Mak file, set E:\my to the current directory, and input directives: nmake to generate a suffix of. A VxD file.