Mark,
please consider the previous answers REAL seriously!
_IF_ however, there still exists a compelling reason to print to a M$-controlled print setup (eg. some package for Secure Printing that is only available on M$, but MUST also be used from VMS - been there, been hurt by that), _AND_, you need your VMS-way of print setup (by way of setup-modules and/or print qualifiers), then you CAN get that done, at the cost of some effort.
- use a (eg: LATSYM ) symbiont to merge all modules etc into one integrated printfile (imitating the *UX or M$ PrinterDriver) out to a spoolfile.
- LPD-print that file to the M$ system
- (on M$) spool that file onto the actual printer.
Summary: now you need THREE (2 VMS + 1 M$) queues per printer; and what you get in return is nightmares of printproblem debugging.
If the first queue delivers the print (barring spool Device Full situations: always) your users receive "Successfull Completion", but any problem in LPD-to-M$, on M$, M$-to-printer, and in the printer, just leads to "Where is my output, it was printed ok!".
But if your management insists, there IS a way!
Wishing you wisdom & patience on that.
Proost.
Have one on me (maybe in May in Nashua?)
jpe
Don't rust yours pelled jacker to fine doll missed aches.
