I usually see those error pages from the PCL6 drivers, but not PCL5e. After many printing issues since WS03 SP2, we use PCL5e or PS on almost all queues now. I do agree though that the UPD hasn't really solved any specific problems for us, and it's kind of a pain to have to detect the printer config in order to get it to show up correctly (can't set it up ahead of time).
-Bonnie -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Friday, June 26, 2009 11:00 AM To: NT System Admin Issues Subject: Re: Bleep'n window server 2008 terminal server On Fri, Jun 26, 2009 at 12:58 PM, Gene Giannamore<gene.giannam...@abideinternational.com> wrote: > What about the HP UPD? Has that worked for anyone? We tried it. It's as slow and bloated as their regular drivers. Over-complicated for network configuration. Had trouble turning off the "slice of toast" notification for every print job submitted. Caused several of our printers to stop working entirely; they would just spit out "PCL XL ERROR" pages. YMMV. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
