[Samba] UPDATE Where are the ADOBE PS Drivers?

[Chris McKeever]

I had an old version 1.02 of the PSDRIVER - that turns out to have all
the correct files needed - SO - I am thinking that V1.06 has been
updated, and the files are no longer available.




On Wed, 8 Sep 2004 13:22:17 -0500, Chris McKeever <techjedi at gmail.com> wrote:
> On Wed, 08 Sep 2004 14:15:48 -0400, Michael Lueck
> <mlueck at lueckdatasystems.com> wrote:
> > Chris McKeever wrote:
> >
> > > A - install the ADOBE POSTSCRIPT file onto a windows machine - check
> > > B - SHARE that printer  - check
> > > C - Grab the specified files from the print$ share on the windows machine
> > >     -- none are there...
> > > D - Place them into: /usr/share/cups
> > > E - run the cupsaddsmb
> >
> > Maybe John himself will jump in as these instructions sound redundant... and I'm not walking over to the book shelf.
> >
> > Redundant as... if steps a-c post files to print$, then there should be no need for cupsaddsmb as that is the Linux command line equiv of uploading the driver from a Windows client box.
> >
> 
> You are missing a small piece - the only way to get the ADOBE files
> (unless you already have them broken out of the installer) is to
> install on a windows client machine, grab them and install them on the
> CUPS server .... the print$ share that is being referred to is that on
> the client machine, hence why you need to copy them and then use
> cupsaddsmb, which then put them into the print$ onto the cups/samba
> server
> 
> it is a bit redundant, but the only way to get the files
> 
> my issue is that, none of the files needed for the cupsaddsmb are
> there - almost as if ADOBE has changed the driver and those are no
> longer included -- however, the archives say the 1.06 version does
> contain them...yet, as I posted earlier, these are the installed
> files:
> 
> 
> 
> 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
> 
> 
> > If you just had the driver files from Adobe, including the .INF file,
> 
> that is the issue -- there is no INF, and the files reuired are not in
> the downloaded/installed driver that I have gotten
> 
> 
> 
> then you should be able to upload them through the printer wizard just
> like any other driver... or use cupsaddsmb from the Linux
> > command line.
> >
> >
> >
> > --
> > 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
> >
>