Print Driver Rendering Test (pgremlin2)

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

Type: Automated Test


The Print Driver Rendering Test (pgremlin2) performs rendering tests on a print driver. This test produces numerous pages of output with shapes and gradient fills and alpha blends. It also prints and tests some complex fonts.


PGremlin2 performs rendering tests on a print driver. The rendering tests range from font tests to text extent tests and include printing bitmaps through the print driver. All print drivers are expected to pass this test. The test will fail if the print driver causes any sort of exception during the rendering.

PGremlin2 exercises the following DDs:

  • TransparentBlt

  • GradientFill

  • PlgBlt

  • StretchBlt

  • AlphaBlend

  • SetDIBBitsToDevice

  • PatBlt

  • FillPath

  • StrokeAndFillPath

The actual validation of the rendering is manual and you must perform that validation by looking at the physical paper output from the printer.

Run Time: 2 minutes
Log File:
System Restart Required: No
Test Category:
Supported operating systems for Logo or Signature testing:
  • Windows 7

  • Windows Server 2008 R2

  • Windows Vista

  • Windows Server 2003

  • Windows XP



Software Requirements

The test tool requires the following software:

  • Supported operating system (see list above)

  • Software components included with the device that is being tested

Hardware Requirements

The test tool requires the following hardware:

  • Device to be tested

  • Computer that meets the minimum software requirements

  • Windows keyboard

  • Two-button pointing device

  • Color display monitor capable of at least 1024 by 768 resolution, 32-bits per pixel, 60 Hz

  • Hard drive with a minimum of 20 GB available on partition C:


  • x86

  • x64

  • Itanium

Test Assertions

Windows Logo Program: IMAGING-0030 Printer drivers must be correctly implemented based on the content of the WDK



Build date: 9/14/2012

Community Additions