I’ve read the information in the DDK about the printing architecture and I
have several questions:
Is there a better documentation about the printing architecture then the
MSDN?
Why some printers print in raw and some in EMF? How this decision is
being taken after an application is issuing a “Print” command? Is there a
way to always produce an EMF file instead of RAW, regardless the printer
being used?
My goal is eventually to get an EMF file from each print request, analyze
it and block / deny the printing. So, Where in the “chain” is the best place
to enter to do such a thing?
Someone else will have to help here, sorry. It appears to be under
user control, so I don’t know if it’s possible to force a driver to
always produce EMF.
Why did you decide that analyzing a undocumented format was the best
way to do the job? Surely there is some better and/or easier way to do
this?
What is the real goal? Is the EMF output the only place the information
needed to allow/deny the printing is available?
ScottR
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Zed y
Sent: Sunday, May 14, 2006 10:57 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Printing drivers architecture
Hi
I’ve read the information in the DDK about the printing
architecture and I have several questions:
Is there a better documentation about the printing
architecture then the MSDN?
Why some printers print in raw and some in EMF? How this
decision is being taken after an application is issuing a “Print”
command? Is there a way to always produce an EMF file instead of RAW,
regardless the printer being used?
My goal is eventually to get an EMF file from each print
request, analyze it and block / deny the printing. So, Where in the
“chain” is the best place to enter to do such a thing?
I though print processor gets RAW / EMF and always outputs RAW.
Or am i wrong?
Is there a sample for such a thing that fits me ?
My final goal is to always produce EMF / SPL containing an EMF from each
print, to analyze the EMF and to dent or allow the print based on this.
On 5/15/06, Christoph Lindemann wrote: > > > 1. Is there a better documentation about the printing architecture then > the MSDN? > > No. Although there are other places that have additional info. Also take a > look at the DDK samples. > > > 2. Why some printers print in raw and some in EMF? > > > http://undocprint.printassociates.com/formats/winspool/spl#when_is_raw_used > > > 3. Where in the “chain” is the best place to enter to do such a thing? > > A print processor would be an ok place to implement this. > > /christoph > > — > Questions? First check the Kernel Driver FAQ at > http://www.osronline.com/article.cfm?id=256 > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer >
Client disables “advanced printing features” in printer properties -
[Isnt this is exactly like the previos section?]
Additionally, for networking printing:
Client doesn’t use a “true” connection - [WHAT does that mean?]
Printing to a “masq” printer [WHAT is masq?]
Server has “printer attribute RAW only” bit set [A printing server?
or the spooler server side? where do you set this bit?]
Server doesn’t accept client’s EMF version [And why is that ?]
On 5/15/06, Zed y wrote: > > A print processor ? > > I though print processor gets RAW / EMF and always outputs RAW. > Or am i wrong? > > Is there a sample for such a thing that fits me ? > > My final goal is to always produce EMF / SPL containing an EMF from each > print, to analyze the EMF and to dent or allow the print based on this. > > > > On 5/15/06, Christoph Lindemann > wrote: > > > > > 1. Is there a better documentation about the printing architecture > > then > > the MSDN? > > > > No. Although there are other places that have additional info. Also take > > a > > look at the DDK samples. > > > > > 2. Why some printers print in raw and some in EMF? > > > > http://undocprint.printassociates.com/formats/winspool/spl#when_is_raw_used > > > > > > > 3. Where in the “chain” is the best place to enter to do such a thing? > > > > A print processor would be an ok place to implement this. > > > > /christoph > > > > — > > Questions? First check the Kernel Driver FAQ at > > http://www.osronline.com/article.cfm?id=256 > > > > To unsubscribe, visit the List Server section of OSR Online at > > http://www.osronline.com/page.cfm?name=ListServer > > > >
----- Original Message -----
From: “Zed y” To: “Windows System Software Devs Interest List” Sent: Monday, May 15, 2006 7:23 PM Subject: Re: [ntdev] Printing drivers architecture
A print processor ?
I though print processor gets RAW / EMF and always outputs RAW. Or am i wrong?
Is there a sample for such a thing that fits me ?
My final goal is to always produce EMF / SPL containing an EMF from each print, to analyze the EMF and to dent or allow the print based on this.
On 5/15/06, Christoph Lindemann wrote: > > > 1. Is there a better documentation about the printing architecture then > the MSDN? > > No. Although there are other places that have additional info. Also take a > look at the DDK samples. > > > 2. Why some printers print in raw and some in EMF? > > > http://undocprint.printassociates.com/formats/winspool/spl#when_is_raw_used > > > 3. Where in the “chain” is the best place to enter to do such a thing? > > A print processor would be an ok place to implement this. > > /christoph > > — > Questions? First check the Kernel Driver FAQ at > http://www.osronline.com/article.cfm?id=256 > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer >
Maxim, i’m new to printer drivers, can you please be more specific ?
Thanks.
On 5/15/06, Maxim S. Shatskih wrote: > > I would better enforce PostScript for this. This will require using > open-source GhostScript though. > > Maxim Shatskih, Windows DDK MVP > StorageCraft Corporation > xxxxx@storagecraft.com > http://www.storagecraft.com > > ----- Original Message ----- > From: “Zed y” > To: “Windows System Software Devs Interest List” > Sent: Monday, May 15, 2006 7:23 PM > Subject: Re: [ntdev] Printing drivers architecture > > > A print processor ? > > I though print processor gets RAW / EMF and always outputs RAW. > Or am i wrong? > > Is there a sample for such a thing that fits me ? > > My final goal is to always produce EMF / SPL containing an EMF from each > print, to analyze the EMF and to dent or allow the print based on this. > > > > On 5/15/06, Christoph Lindemann > wrote: > > > > > 1. Is there a better documentation about the printing architecture > then > > the MSDN? > > > > No. Although there are other places that have additional info. Also take > a > > look at the DDK samples. > > > > > 2. Why some printers print in raw and some in EMF? > > > > > > > http://undocprint.printassociates.com/formats/winspool/spl#when_is_raw_used > > > > > 3. Where in the “chain” is the best place to enter to do such a thing? > > > > A print processor would be an ok place to implement this. > > > > /christoph > > > > — > > Questions? First check the Kernel Driver FAQ at > > http://www.osronline.com/article.cfm?id=256 > > > > To unsubscribe, visit the List Server section of OSR Online at > > http://www.osronline.com/page.cfm?name=ListServer > > > > — > Questions? First check the Kernel Driver FAQ at > http://www.osronline.com/article.cfm?id=256 > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer > > > — > Questions? First check the Kernel Driver FAQ at > http://www.osronline.com/article.cfm?id=256 > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer >
Force the users administratively to install MS’s or Adobe’s PostScript
printer driver with some simple PPD file. Their PostScript will go to the
server, where you will be able to parse it, do what you want, and then print it
on a real printer attached to the server.
----- Original Message -----
From: “Zed y” To: “Windows System Software Devs Interest List” Sent: Monday, May 15, 2006 8:34 PM Subject: Re: [ntdev] Printing drivers architecture
Maxim, i’m new to printer drivers, can you please be more specific ?
Thanks.
On 5/15/06, Maxim S. Shatskih wrote: > > I would better enforce PostScript for this. This will require using > open-source GhostScript though. > > Maxim Shatskih, Windows DDK MVP > StorageCraft Corporation > xxxxx@storagecraft.com > http://www.storagecraft.com > > ----- Original Message ----- > From: “Zed y” > To: “Windows System Software Devs Interest List” > Sent: Monday, May 15, 2006 7:23 PM > Subject: Re: [ntdev] Printing drivers architecture > > > A print processor ? > > I though print processor gets RAW / EMF and always outputs RAW. > Or am i wrong? > > Is there a sample for such a thing that fits me ? > > My final goal is to always produce EMF / SPL containing an EMF from each > print, to analyze the EMF and to dent or allow the print based on this. > > > > On 5/15/06, Christoph Lindemann > wrote: > > > > > 1. Is there a better documentation about the printing architecture > then > > the MSDN? > > > > No. Although there are other places that have additional info. Also take > a > > look at the DDK samples. > > > > > 2. Why some printers print in raw and some in EMF? > > > > > > > http://undocprint.printassociates.com/formats/winspool/spl#when_is_raw_used > > > > > 3. Where in the “chain” is the best place to enter to do such a thing? > > > > A print processor would be an ok place to implement this. > > > > /christoph > > > > — > > Questions? First check the Kernel Driver FAQ at > > http://www.osronline.com/article.cfm?id=256 > > > > To unsubscribe, visit the List Server section of OSR Online at > > http://www.osronline.com/page.cfm?name=ListServer > > > > — > Questions? First check the Kernel Driver FAQ at > http://www.osronline.com/article.cfm?id=256 > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer > > > — > Questions? First check the Kernel Driver FAQ at > http://www.osronline.com/article.cfm?id=256 > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer >