DOC: Creating a Minidriver |
Q156536
The information in this article applies to:
- Microsoft Win32 Device Driver Kit (DDK) for Windows NT, version 4.0
SUMMARY
There are incorrect and misleading errors in the Online documentation for the following page:
Graphics Drivers
\Design Guide
\Part 3: Print Components
\Chapter 11 Printer Minidrivers and RasDD
\Developing Windows NT Minidrivers
\Creating a Minidriver
MORE INFORMATION
Step 4 incorrectly states that one of the files that Unitool writes is <driver_name>.RC. It actually writes a <driver_name>.W31 file and not a .RC file. You can verify this by opening a minidriver sample in Unitool, then doing a File/Save without modifying the file, and noting what new files were written to disk.
The last paragraph in step 6 is incorrect and misleading. The reference to <driver_name>.RC should be replaced with <driver_name>.W31 in the documentation. When you save your minidriver project in Unitool, it writes a new <driver_name>.W31 file and a new <driver_name>.GPC file. You must then translate the contents of your new <driver_name>.W31 file to that of your <driver_name>.RC file so you can actually build the minidriver in the build environments.
The <driver_name>.RC file points to your 32-bit font files to be built into the minidriver's resources. The <driver_name>.W31 file points to your 16-bit font files that are converted to 32-bit with the CTT2RLE.EXE and PFM2IFI.EXE utilities. The <driver_name>.GPC file contains the printer descriptions you wrote using Unitool.
Additional query words: 4.00 kbdsh
Keywords :
Issue type :
Technology : kbAudDeveloper kbWinDDKSearch kbWin32sSearch kbWin32DDKSearch kbWin32DDKNT400 kbWin32DDKNTSearch
Last Reviewed: March 6, 1999 |
