title: How to install pscript/unidrv rendering plugins? DDK/WDK print/oemdll samples are acting strange
body: <p>I'm trying to get something of <a href="http://msdn.microsoft.com/en-us/library/windows/hardware/ff551780%28v=vs.85%29.aspx" rel="nofollow">pscript/unidrv rendering plugins</a>, but the provided DDK samples just can't be installed on any possible combination of DDK/build/target system I ever have.</p>
  
  <p>The message reported is 'The specified port is unknown' for WinXP x64 and 'Element not found' for Win7,Win8 (part of Win7 setupapi log with remarkable <strong>"dvi:                A NULL driver installation is not allowed for this type of device!</strong>" error can be found <a href="http://everfall.com/paste/id.php?c8s0rbt8xax6" rel="nofollow">here</a>).</p>
  
  <p>So far, I've tried to:</p>
  
  <ul>
  <li>change .rc file to match FILESUBTYPE (<code>VFT2_DRV_VERSIONED_PRINTER</code>) and FILETYPE (<code>VFT_DRV</code>)</li>
  <li>sign using test certificate, turn debug mode on</li>
  <li>add empty hw-id followed by normal compatible-id to product names in .inf (<code>"product 1" = product_target,,product_1</code>)</li>
  <li>checked that all files referenced in .inf (.ini, .gpd, .dll) are in place</li>
  <li>remove all additional references to any files excluding my desired <em>oemps</em> target</li>
  <li>run chkinf tests and fix all the warnings</li>
  <li>mess with UAC, file locations, do other Inca dance.</li>
  </ul>
  
  <hr>
  
  <p>What else should be done to get a pscript rendering plugin installed into the system? </p>
  
  <p><em>Are they ever meant to be installed as a normal device, outside of printer drivers? MSDN is really unclear on that, but, guessing from the presence of .inf's inside DDK sources, I guess there's a way to install them 'as is', I just don't found that.. yet.</em></p>
  
  <hr>
  
  <p>UPD: found the description for these samples in WDK8 ("<a href="http://code.msdn.microsoft.com/windowshardware/OEMDLL-Samples-71364d95" rel="nofollow">http://code.msdn.microsoft.com/windowshardware/OEMDLL-Samples-71364d95</a>"), which mentions something that isn't found at main article ("Customizing Microsoft's Printer Drivers") - <strong>"The BITMAP, OEMPS, OEMUI, OEMUNI, OEMPREAN, CUSTHLP, SyncSet, ThemeUI, PSUIRep, and Watermark samples do not affect the printer output"</strong>. </p>