Thanks again for all the help Maxim,
I noticed an interesting thing today - first, I have a lot of logging in my
driver to see what's going on.
My premise that Adobe doesn't print on the server is based on the fact that
this log on the server is empty, i.e., it's never even instantiated there.
However, today I had a view of the server's print queue open and sure
enough, the print job appears there momentarily and then disappears - gets
redirected back to the client ! Without even attempting to open the local
driver (the log is still empty).
Anyway - this may be a clue to what's going on - I need to investigate why
for some reason a server might kick a job back to the client. I had a
fleeting thought that what if this "render job on client" setting works in
reverse !
Anyway, no need to reply - if and when I solve this, and if this thread's
still around - I'll post my solution. But for now, I need to step back and
think of another way to debug this.
(I'm not giving up, I promise !)
Regards and have a great new year !
Nate Clark
"Maxim S. Shatskih" wrote:
> > in the DDK help doesn't uncover it !? Did you mean WritePrinter ?
>
> Probably.
>
> The name of the function called by the driver to output the bytes to the print processor/spoolsv.exe
>
> --
> Maxim S. Shatskih
> Windows DDK MVP
>
> http://www.storagecraft.com
>
> .
>
Linear Mode
