[THIN] Re: Printer Hell
- From: "Rick Mack" <ulrich.mack@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Sat, 3 Feb 2007 17:24:56 +1000
Hi George,
I just make the assumption that all drivers are bad until tested and don't
pay any attention to the Citrix list. We've had Adobe postscript drivers
that worked fine for an admin, but crashed the server or the spooler when
used by a non-admin and lots of other intriguing problems.
In this case I suspect it wasn't 'til Citrix actually started looking
seriously at why the cpsvc was flakey despite code that worked fine
otherwise that they found this little can of worms. However I'll suggest to
Citrix that they update CTX110571..
But to answer your question, you've got several options when addprinter says
you've got a driver that causes errors.
If you're lucky HP will have a suitable replacement on their beta driver
site, otherwise there's always HP's universal printer driver (PCL and
Postscript), or a series printer driver (eg 4000 series for a 4100 4200
etc). The last option is to hack the driver as per Citrix' instructions to
remove or replace the offending DLLs and replace them with the updated DLLs
from the HP beta site.
The only painful part is having to update/replace/hack the driver on the
print server first and then make sure the changed driver propagates to all
your TS systems. That's where a rundll32 printui.dll or wmi script to delete
the existing driver and then create/delete a connection to the appropriate
network queue to suck in the updated driver makes things much easier.
regards,
Rick
--
Ulrich Mack
Commander Australia
On 2/3/07, George Yobst <george.yobst@xxxxxxxxx> wrote:
So at the end of all this testing you've replaced 10-15% of the drivers --
with what exactly? Didn't you get HP drivers off the list first that were
supposed to work (or are you telling us that list they post bi-annually is a
piece of trash) -- *CTX110571 *?
-George
Other related posts:
