S
sporxix
Guest
- We had developed a plugin for the Windows universal printer driver based on the WDK sample "\src\print\oemdll\oemuni".
- This plugin worked fine for the last 15 years, but now with Win10's StoreApps (e.g. Edge) printing doesn't work if "directprint" is configured (printing is okay when running the spooler mode).
- I have also tried other printers like "Fineprint" or "Foxit PDF printer" and there is the same behavior.
- The logging of our printer shows that the plugin is loaded and initialised correctly, but the StoreApp doesn't call the DDIHook function OEMStartDoc() which normally starts the streaming of the page's bitmap.
- I have search this forum for this topic and browsed through WDK docu... I found a lot of similar entries and several solving hints but not a (simple to read and easy to implement) solution for my scenario.
And after the description and constraints now some guesses and questions:
- What is wrong with this scenario? Is this malfunction a "feature" or is there a possibility to get it printing?!
- Is it possible to change one/some authorization options for the StoreApp Runtime to get printing allowed?
- Is it necessary/sufficient to upgrade our driver to level v4? Or has it to be re-implemented from GDI to XPS output?
- Is there a description available somewhere with the topic: "How to upgrade an existing uniprn driver plugin from v3 to v4? A simple upgrade path for ancient Rookies"?
Thanks in advance for good hints... and greetings from Munich :-D
Continue reading...
- This plugin worked fine for the last 15 years, but now with Win10's StoreApps (e.g. Edge) printing doesn't work if "directprint" is configured (printing is okay when running the spooler mode).
- I have also tried other printers like "Fineprint" or "Foxit PDF printer" and there is the same behavior.
- The logging of our printer shows that the plugin is loaded and initialised correctly, but the StoreApp doesn't call the DDIHook function OEMStartDoc() which normally starts the streaming of the page's bitmap.
- I have search this forum for this topic and browsed through WDK docu... I found a lot of similar entries and several solving hints but not a (simple to read and easy to implement) solution for my scenario.
And after the description and constraints now some guesses and questions:
- What is wrong with this scenario? Is this malfunction a "feature" or is there a possibility to get it printing?!
- Is it possible to change one/some authorization options for the StoreApp Runtime to get printing allowed?
- Is it necessary/sufficient to upgrade our driver to level v4? Or has it to be re-implemented from GDI to XPS output?
- Is there a description available somewhere with the topic: "How to upgrade an existing uniprn driver plugin from v3 to v4? A simple upgrade path for ancient Rookies"?
Thanks in advance for good hints... and greetings from Munich :-D
Continue reading...