search for: adobeps

I'm following the Samba HOWTO for CUPS printing, trying to run the 'cupsaddsmb' program but it requires the Adobe PS files. The howto says to get them from www.adobe.com, can anyone be more specific? The files required are: ADFONTS.MFM ADOBEPS4.DRV ADOBEPS4.HLP ADOBEPS5.DLL ADOBESU.DLL ADOBESU.HLP ADOBEPTR2.PPD ICONLIB.DLL I've downloaded the "Universal 1.0.6 English" 7.4MB winsteng.exe[1] for Windows and got all of the above files except "ADOBEPS5.DLL, ADOBEPSU.DLL, and ADOBESU.HLP" from c:\windows\system... Th...

..., According to Samba 2.2.x HOW-TO: You need to download them yourself from the Adobe website. Once extracted, create a drivers directory in the CUPS data directory (usually /usr/share/cups/). Copy the Adobe files using UPPERCASE filenames, to this directory as follows: ADFONTS.MFM ADOBEPS4.DRV ADOBEPS4.HLP ADOBEPS5.DLL ADOBEPSU.DLL ADOBEPSU.HLP DEFPRTR2.PPD ICONLIB.DLL I could not find ADOBEPSU.HLP from adobe, neither from "Adobe Universal PostScript Windows Driver Installer 1.0.6" nor from " PostScript Printer Driver...

...winNT/2000/XP at the same time. The CUPS method is to find one ppd that works for all and I have tried several: those at linuxprinting.org, hp's sourceforge site, vendor winNT ppds (docs suggest these), and vendor win98 ppds. I have tried filtering PJL and not filtering PJL. I have the stock ADOBEPS driver for win9x clients, the cupsdrvr driver for winNT/2000/XP clients and all works as it should except for print quality. Most jobs go through fine, but most is not enough. Depending on the client and the print job, jobs are either printing with bad margins, bad colors, printing postscript err...

> [Samba] cupsaddsmb adobe error message > Sundaram Ramasamy sun at percipia.com > Fri Mar 12 04:18:05 GMT 2004 > > > Hi, > > I am trying to add automatic driver install, its giving me ADOBEPS5.DLL > file not found error message. > You should read the man page of "cupsaddsmb". It would tell you that the preparation to be completed *before* running the command consists, amongst other things, to place the Windows driver files into the "/usr/share/cups/drivers/"...

...rkaround, sort of...set disable spoolss=no, install drivers for the HP printers; then set disable spoolss=yes. Add "use client driver=no" on each of the HP printer entries. Add "use client driver=yes" for the non-HP printers. I have 3 non-HP, and they either use the Lexmark or AdobePS install proggies. Can't install the drivers on the Samba box using APW. I've posted a few items recently while working on the problem; APW is only part of the problem. If disable spoolss=no, adding a printer on my Win2k PC results in the following: 1. Adding a printer from the Samba...

...pdf-generator] comment = PDF Generator path = /var/tmp printable = Yes printing = bsd print command = /usr/share/samba/scripts/print-pdf %s ~%u \\\\\\\\%L\\\\%u %m %I & printer driver = PDF Generator printer driver location = \\%h\PRINTER$\adobeps

Hi, I was wondering if anyone has gotten automatic printer driver downloading to work? The problem I'm seeing here is while trying to upload a printer driver to the Samba print server using Windows 2000 or XP. The Add Printer Driver Wizard runs ok until I click on the Finish button, then it requires a Windows 2000 Advanced Server CD-ROM to be installed, to get a driver out of the

I'm afraid I am stumped, and need some help or pointers. Ever since I've "upgraded" my Win2k boxes to SP4, I've been unable to print to Samba-shared printers (on Solaris and Freebsd). Originally I was running the current 2.2.x, and figured trying to diagnose the problem would provide an impetus for trying 3.0, which I have from beta3 through RC1. That bit of history is

Anyone successfully using a HP 8000 DN or HP 5 Lsi (with JetDirect module and assigned IP) with samba? Subject says it all. If you're successfully doing this, what configs made it work? FAQs tell how to set up with a print server, but what if the printer itself is the server? Trust me, the HP doesn't know jack about port 139. Using samba 2.0.4 on Solaris 7 and NT 4.0 SP5 with

I have a Red Hat Linux release 7.1 (Seawolf) Samba 2.2.4 PDC and fileserver built with --with-ldapsam. The clients are either win9x or WinY2k. Authenitcation, etc... all works great. But print sharing is a real pain. Under 2.2.1a printing worked great, but our VOIP phone system wouldn't joint the domain until we upgraded to 2.2.4. Initial testing of 2.2.4 made it seem like everything