I downloaded the drivers from: http://www.adobe.com/support/downloads/product.jsp?product=pdrv&platform=win 7.4MB Adobe Universal PostScript Windows Driver Installer 1.0.6 - English 5/23/2002 And installed the Generic Driver, shared the printer and went the the print$ share - none of the expected files were in there ... any ideas??? DEFPRTR2.BPD A 12188 Tue Sep 7 23:27:50 2004 defprtr2.ppd A 13492 Tue Apr 23 12:50:10 2002 efisysprint.sep A 3277 Fri Nov 22 01:54:02 2002 efisysprtj.sep A 3640 Fri Nov 22 01:54:04 2002 EFME4320.BPD A 61420 Tue Sep 7 22:14:24 2004 EFME4320.bxe A 102400 Tue Jan 7 20:23:48 2003 EFME4320.cnt A 1230 Fri Jun 28 23:56:24 2002 EFME4320.dll A 81994 Tue Jan 7 20:24:16 2003 EFME4320.ext A 532535 Tue Jan 7 20:23:48 2003 EFME4320.fin A 1175613 Tue Jan 7 20:23:46 2003 EFME4320.hlp A 56090 Tue May 21 23:44:48 2002 EFME4320.ini A 74 Wed Jan 15 02:24:14 2003 EFME4320.lan A 1851449 Tue Jan 7 20:23:48 2003 EFME4320.oem A 2109512 Tue Jan 7 20:24:10 2003 EFME4320.pge A 4243 Thu Aug 8 18:30:22 2002 EFME4320.PPD A 74812 Sat Jan 11 02:18:42 2003 EFME4320.psr A 47858 Tue Jan 7 20:24:16 2003 EFME4320.uim A 1855546 Tue Jan 7 20:23:46 2003 ehm10.dll A 421930 Wed Jul 17 10:06:00 2002 ehmbrg.dll A 299051 Wed Jul 17 10:05:40 2002 ehmcore.dll A 98348 Wed Jul 17 10:05:20 2002 ehmecol.dll A 155692 Wed Jul 17 10:07:18 2002 ehmefi.dll A 487467 Wed Jul 17 10:06:58 2002 HPLJ4.BUD A 39312 Tue Sep 7 20:21:20 2004 HPLJ4.GPD A 26569 Fri Jul 30 16:02:58 1999 PCL5ERES.DLL A 676352 Tue Nov 30 01:30:54 1999 PS5UI.DLL A 130048 Thu Jun 19 14:05:04 2003 PSCRIPT.HLP A 26038 Mon Jul 22 14:05:04 2002 PSCRIPT.NTF A 792644 Mon Jul 22 14:05:04 2002 PSCRIPT5.DLL A 455168 Thu Jun 19 14:05:04 2003 STDNAMES.GPD A 14362 Thu Jun 19 14:05:04 2003 TTFSUB.GPD A 698 Mon Jun 7 15:48:52 1999 TTY.BUD A 21596 Tue Sep 7 23:22:27 2004 TTY.DLL A 8464 Thu Jun 19 14:05:04 2003 TTY.GPD A 12507 Fri Jul 30 16:06:18 1999 TTY.INI A 62 Fri May 8 18:04:12 1998 TTYRES.DLL A 39424 Thu Jun 19 14:05:04 2003 TTYUI.DLL A 16144 Thu Jun 19 14:05:04 2003 TTYUI.HLP A 14318 Thu Oct 7 15:08:06 1999 UNIDRV.DLL A 239104 Thu Jun 19 14:05:04 2003 UNIDRV.HLP A 21225 Thu Jun 19 14:05:04 2003 UNIDRVUI.DLL A 197120 Thu Jun 19 14:05:04 2003 UNIRES.DLL A 619520 Thu Jun 19 14:05:04 2003
Check the Samba HOWTO on this topic. John specifically points out there are three different ways to install the driver, only one does it correctly. I believe this might be what you are bumping into, but I have no first hand expirence since I read the docs before I dug in. -- Michael Lueck Lueck Data Systems Remove the upper case letters NOSPAM to contact me directly.
On Wed, 08 Sep 2004 13:34:23 -0400, Michael Lueck <mlueck@lueckdatasystems.com> wrote:> Check the Samba HOWTO on this topic. John specifically points out there are three different ways to install the driver, only one does it correctly. I believe this might be what you are bumping into, > but I have no first hand expirence since I read the docs before I dug in. >That is what I am going off - and it lists the dozen files that are needed, and none of them are listed .... Once you have extracted the driver files, create a "drivers" directory in the CUPS data directory (usually /usr/share/cups) and copy the Adobe files using UPPERCASE filenames, as follows: [Windows 95, 98, and Me] ADFONTS.MFM ADOBEPS4.DRV ADOBEPS4.HLP DEFPRTR2.PPD ICONLIB.DLL PSMON.DLL [Windows NT, 2000, and XP] ADOBEPS5.DLL ADOBEPSU.DLL ADOBEPSU.HLP thanks> -- > Michael Lueck > Lueck Data Systems > > Remove the upper case letters NOSPAM to contact me directly. > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
Chris McKeever
2004-Sep-10 13:19 UTC
[Samba] Re: CUPS Print Quality -- WAS -- UPDATE Where are the ADOBE PS Drivers?
n Fri, 10 Sep 2004 09:52:34 +0100, Simon Hobson <shobson-lists@colony.com> wrote:> Chris McKeever wrote:> > > >The reason I ask, was that I thought (for some reason) that the CUPS > >processing made the windows client driver independent - but if the > >windows client uses the PPD - then I am thinking that I was mistaken > > > The first step (as far as Samba printing is concerned), if not > already feeding it the right format, is to pre-process the input file > to extract device specific options and convert them to Cups > parameters and generate a device-independent Postscript file. > > It selects a set of conversion filters, typically using Ghostscript > to generate a bitmap image and then encode this into the printers > native format. > > > If properly configured, there is no reason that Cups should not be > able to produce output as good as any other driver. The quality you > actually get will largely depend on the settings (particularly > resolution and colour depth) for the PS to bitmap conversion, plus an > element of how well the device dependent filter converts the > resulting bitmap to the printers native format. >I believe in my tests, it was becausae I was going to a non PS printer using the generic HPLJ PPD -- and unfortunately, both the PPD's I tested using the ppd test script failed> From the above, you can prbably imagine that if you use a generic > PPD, you can use the same driver and PPD for all printers, but you > won't get access to all the facilities available on a printer. If you > stick with the Adobe PS drivers, then you can use the same driver for > all printers, only the PPD is different. >So - the PPD controls the print options - therefore driver independence isnt fully achievable since you need the printer specific PPD (if you want to be able to set printer specific information per job) from the howto: "A postscript file that was created to contain device-specific ommands for achieving a certain print job output on a specific target machine, may not print as expectd, or may not be printable at all on other models" Now what would be nice (and who knows if at all possible) - if there was a generic CUPS PPD, which gave general print options (duplex/punched) -- when sent from windows into the cups spooled, cups could extract what the client requested, use the PPD of the vendor to ensure what was requested is available, recreated the PS file and send it to the printer. With this, the client could be completely driver/ppd independent from the howto: "for real PS printers, DO NOT use the foomatic PPD's. The original vendor PPD's are always first choice" Thanks for the information - if I am still off, I apologize....> Simon > > -- > Simon Hobson MA MIEE, Technology Specialist > Colony Gift Corporation Limited > Lindal in Furness, Ulverston, Cumbria, LA12 0LD > Tel 01229 461100, Fax 01229 461101 > > Registered in England No. 1499611 > Regd. Office : 100 New Bridge Street, London, EC4V 6JA. > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
Chris McKeever
2004-Sep-10 13:58 UTC
[Samba] Re: CUPS Print Quality -- WAS -- UPDATE Where are the ADOBE PS Drivers?
On Fri, 10 Sep 2004 14:45:08 +0100, Simon Hobson <shobson-lists@colony.com> wrote:> Chris McKeever wrote: > > >So - the PPD controls the print options - therefore driver > >independence isnt fully achievable since you need the printer specific > >PPD (if you want to be able to set printer specific information per > >job) > > Yes, that is true. What I am not sure about as I've not done the > testing to support it, is whether just changing the PPD and > re-running cupsaddsmb will result in the client getting the new ppd > installed (our login script maps the printers on this site). If it > does then swapping out a printer should be as simple as changing the > ppd on the server.I dont think that you can push the client a new PPD by changing it on the server .. it gets downloaded to the client on the first connection. I dont think it looks back into the print$ directory -- I think it pulls defaults/etc from the .TDB database files and that about the most of the interaction it has with the server till it spools the job to it -- but your idea below I find quite interesting regarding a generic PPD> > One of the things about Postscript is that it tends to degrade > reasonably well. I'm fairly confident that in most cases you could > send a file that (for example) requests duplex printing to a printer > without that feature and it will still print (but without the duplex > of course). > > >Now what would be nice (and who knows if at all possible) - if there > >was a generic CUPS PPD, which gave general print options > >(duplex/punched) -- when sent from windows into the cups spooled, cups > >could extract what the client requested, use the PPD of the vendor to > >ensure what was requested is available, recreated the PS file and send > >it to the printer. With this, the client could be completely > >driver/ppd independent > > > > You could roll your own ! > > I don't know if you've looked at the contents of a ppd, but they tend > to be fairly easy to understand (if a bit large for a complex > printer). If you started with a complex printer ppd and stripped out > the bits you don't need then you could end up with something that > would just have the features you want, and I think you would probably > find the output reasonably portable.I have tried 3 of my PPD's all failed the testppd.php script --- figures...but I said this before, striving for driver independence on the client may be a 'holy grail quest'.....> > > > > -- > Simon Hobson MA MIEE, Technology Specialist > Colony Gift Corporation Limited > Lindal in Furness, Ulverston, Cumbria, LA12 0LD > Tel 01229 461100, Fax 01229 461101 > > Registered in England No. 1499611 > Regd. Office : 100 New Bridge Street, London, EC4V 6JA. > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >