Re: can't print postscript 3.0 on RH 7.2

On Wed, Apr 24, 2002 at 06:46:07PM +0200, Kjetil Tjensvold wrote: > Me too had problems with rh 7.2 and postscript. I > installed Cups (Common Unix Printing System) and now > all works fine. I had no problems when I had rh 7.0 > installed so it is a 7.2 problem. Hm... I thought about it too, and

Re: can't print postscript 3.0 on RH 7.2

Me too had problems with rh 7.2 and postscript. I installed Cups (Common Unix Printing System) and now all works fine. I had no problems when I had rh 7.0 installed so it is a 7.2 problem. -- Anand Buddhdev <[EMAIL PROTECTED]> skrev: > I seem to be unable to print Postscript level 3.0 > files on

Re: can't print

Thanks! I disabled FF and EOT. Now I don't get those two extra pages at the end. But I'm still getting extraneous small horizontal marks on some of the letters, like lower case "t" and "1". On this Red Hat 7.2 machine, I'm using the LaserJet 4050 Postscript driver. Which driver are you using?

RE: can't print

Little diamond? I got it too!!! But the problem fix after I disable these optios: - Send FF - Send EOT I ever found this small diamond could be fixed if use draft quality (300x300 dps) rather than normal or presentation quality. I found this problem on HP Deskjet and Laserjet. Hope this help #

Re: can't print

On Fri, 28 Dec 2001 07:11:29 -0500 Devon <[EMAIL PROTECTED]> implied: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Friday 28 December 2001 01:33 am, ABrady wrote: > > > Sorry but I did that one, too. I'm not sure he tried it after his > > reinstall. > > > > It uses a lexmark-supplie

Re: can't print

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 28 December 2001 01:33 am, ABrady wrote: > Sorry but I did that one, too. I'm not sure he tried it after his > reinstall. > > It uses a lexmark-supplied printer driver. In 7.1 that driver needed > another rpm to be installed (vdk-something)

Re: can't print

On Thu, 27 Dec 2001 22:52:41 -0500 Devon <[EMAIL PROTECTED]> implied: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thursday 27 December 2001 05:52 pm, ABrady wrote: > > On Thu, 27 Dec 2001 12:20:27 -0800 > > > > Hidong Kim <[EMAIL PROTECTED]> implied: > > > Hi, > > > > > > After upgr

Re: can't print

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 28 December 2001 12:21 am, Hidong Kim wrote: > Great! > > After upgrading all of the packages and following your directions, I > can print again. Excellent, glad it helped. > One small problem is that I have a queue set up for a > network

Re: can't print

Great! After upgrading all of the packages and following your directions, I can print again. One small problem is that I have a queue set up for a networked HP LaserJet 4050TN. I chose the PostScript driver under the LaserJet 4050 printer (no TN available in printtool). This driver seems to be

Re: can't print

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 27 December 2001 05:52 pm, ABrady wrote: > On Thu, 27 Dec 2001 12:20:27 -0800 > > Hidong Kim <[EMAIL PROTECTED]> implied: > > Hi, > > > > After upgrading from Red Hat 7.0 to 7.2, I can't print. When I > > submit a print job, the output ha

Re: can't print

On Thu, 27 Dec 2001 12:20:27 -0800 Hidong Kim <[EMAIL PROTECTED]> implied: > Hi, > > After upgrading from Red Hat 7.0 to 7.2, I can't print. When I submit > a print job, the output has several lines that read: > > Unable to open the initial device, quitting. > > > I've tried creating a

Re: can't print

I thought I had these installed. Printing was working fine before I upgraded to 7.2. If I have to reinstall them, how can I do this without recompiling the kernel? Thanks, Hidong Statux wrote: > > Make sure you have the support for the hardware installed (ie. parallel > port drivers/mo

Re: can't print

Make sure you have the support for the hardware installed (ie. parallel port drivers/modules, etc). On Thu, 27 Dec 2001, Hidong Kim wrote: > Hi, > > After upgrading from Red Hat 7.0 to 7.2, I can't print. When I submit a > print job, the output has several lines that read: > > Unable to

RE: Can't print to Win2k Printer

I finally got it to work by removing the Workgroup I had entered in printtool. It may be possible that printtool has a bug accepting workgroups with spaces in its name. Regards, Adam -Original Message- From: Adam Warner [mailto:[EMAIL PROTECTED]] Sent: Monday, 4 December 2000 3:24 p.m. T

Re: can't print local, but can print remote

You're welcome :) On Sun, 19 Nov 2000, Hidong Kim wrote: > Hi, Statux, > > It's so totally working now! I set the permissions on the /usr/lp* > directories according to your configs. Now I remember that I was also > playing around with the permissions in /usr/* for another application. > I mus

Re: can't print local, but can print remote

Hi, Statux, It's so totally working now! I set the permissions on the /usr/lp* directories according to your configs. Now I remember that I was also playing around with the permissions in /usr/* for another application. I must've screwed up the printer directories in the process. Thanks, H

Re: can't print local, but can print remote

my .seq file (which I think gets changed everytime something gets queued for printing, but never disappears) looks like this: -rw-rw---x1 root lp 4 Nov 16 23:23 .seq root:lp with 0661 permissions the parent directory (/var/spool/lpd) is root:daemon with 0775 permissions, th

Re: can't print local, but can print remote

Hi, Statux, Which config files should I be looking at? I see that there are two directories /var/spool/lpd/lp0 and /var/spool/lpd/lp. The printer device is on /dev/lp0. In each of these directories is a file general.cfg. more /var/spool/lpd/lp0/general.cfg [return] # # General config options

Re: can't print local, but can print remote

What do your config files for lp look like? On Mon, 13 Nov 2000, Hidong Kim wrote: > Hi, > > I can't print, and I don't know why. When I submit a print job, like > "lpr .bashrc", I get the error: > > lpr: Printer queue is disabled > > > "lpq" shows: > > Warning: lp is down: lp is ready and