In the Visual Studio 6.0 integrated environment, the development device driver is on Windows, the development environment provided by Windows DDK is based on command line, and it is extremely inconvenient to operate. I believe that friends who have developed driver must be deeply sick. On the other hand, Visual Studio 6.0 provides us with a very friendly and easy-to-use integrated environment, let us have a feeling of tiger. So, can you use the Visual Studio's integrated environment to develop drivers? After multi-exploration, and combined with its own development driver experience, I have explored a practical approach to create my own driver development integrated environment by simple settings for the Visual Studio integration environment. Some of the experiences of the author are dedicated to share with you, if there is nothing, welcome to correct. 0. The system requires DDK Visual C 6.0 (all tools to be installed) installed. 1. Transform DDK / BIN / STENV.BAT Remove the relevant statement of MSTools (if you want to develop drive in the command line environment Add Call VC_DIR / VC98 / BIN / VCVARS32. BAT) to use VC related tools in the command line; if you just want to develop vcvars32.bat if you want to develop, you can set it in the VC environment. 7. Create a directory Driverenv (directory name random), as a big home camp you developed 3. Create a batch file MakeDrvr.bat in this directory, the content is as follows: @echo offif "% 1" == "" goto USAGEIF "% 3" == "" goto usageif not exist% 1 / bin / setENV.BAT GOTO USAGECALL% 1 / bin / setENV% 1% 4% 2CD% 3BUILD -B -W% 5% 6% 7% 8% 9goto exit: usageecho usage MakeDrvr DDK_dir Driver_Drive Driver_Dir free / checked [build_options] echo eg MakeDrvr %% DDKROOT %% C: %% WDMBOOK %% free -cef: exit the batch first parameter to make some checks pass, then call ddk The setENV command sets the environment variable, then change the directory as the drive and directory where the source program is located, and finally calls build, -b ensures that the full error message is displayed, and the -w guarantees that the warning is output on the screen, which can be in the Output window in the VC IDE. See these errors and warnings.
