Hi Steven,
You can accomplish this by using SetJob with JOB_INFO_3 to chain the jobs. You
need to pause the jobs first.
More info in the SetJob documentation.
If you do not want to chain, you can also set the position via SetJob. I have
not tried it, so I do not know if the order is guaranteed when setting the
position, or if it might change when new jobs are added.
/christoph
On 10. mar. 2016, at 19.29, Steven Bardwell <SBardwell@xxxxxxxxxx> wrote:---
I would like to find a way to force the Windows Spooler to send jobs to print
in the order the user makes the print request.
These requests are being sent by a single process, one at a time so it seems
there should be some setting in the printer properties that would guarantee
that the print jobs would be sent in order.
I have not found any combination of options on the 'Advanced' tab of the
printer properties that accomplishes this ('Start printing immediately' or
'Start printing after last page is spooled' or 'Print spooled documents
first'). The 'Print directly to the printer' is not an acceptable option
because I need to keep copies of the spool files (so 'Keep printed documents'
is turned on).
The only pattern I have seen is that occasionally, when a large print job is
sent to print, followed by multiple short jobs, some of the short jobs will
get to the printer before the large job.
Steve Bardwell
LBM Systems
---
Questions? First check the UndocPrint pages at
http://www.undocprint.org/winspool
To unsubscribe, visit the List Server page at
//www.freelists.org/list/winprndev