From owner-freebsd-ports Sun Jun 22 11:52:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA17370 for ports-outgoing; Sun, 22 Jun 1997 11:52:13 -0700 (PDT) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA17364 for ; Sun, 22 Jun 1997 11:52:10 -0700 (PDT) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.5/8.8.5) with ESMTP id OAA07488; Sun, 22 Jun 1997 14:51:32 -0400 (EDT) Received: from jtroy.async.vt.edu. (jtroy.async.vt.edu [128.173.22.208]) by sable.cc.vt.edu (8.8.5/8.8.5) with SMTP id OAA27050; Sun, 22 Jun 1997 14:51:30 -0400 (EDT) Message-ID: <33AD7482.41C67EA6@vt.edu> Date: Sun, 22 Jun 1997 14:52:51 -0400 From: "Jesse D. Troy" X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: "Jesse D. Troy" , ports@FreeBSD.ORG, andreas@klemm.gtn.com Subject: Re: Apsfilter and Epson Stylus Color printer References: <33AC6BF6.167EB0E7@vt.edu> <19970622102814.41455@klemm.gtn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Andreas Klemm wrote: > > On Sat, Jun 21, 1997 at 08:04:06PM -0400, Jesse D. Troy wrote: > > I have recently installed apsfilter 4.9.3 on my FreeBSD 2.2.2 machine. > > I am using Ghostscript 4.02 and an Epson Stylus Color printer. > > Which gs driver and resolution do you use for your printer ? > Please enable debugging in /usr/local/apsfilter/bin/apsfilter > by uncommenting set -x. After that you print something and look > at the putput of the logfile (the path you can lookup in > /etc/printcap, lf=...). > > Then look, what conversion is done and how ghostscript is > called. I suggest, that you try to use the same commands > on the commandline, to see, how long it takes for the ghostscript > process, to create the print data ... If you redirect the output > of ghostscript to a file, then you'll get the additional information, > how big the print job really is. > > This file you can print by using "cat file > /dev/your_print_device. > I uncommented the set -x line and looked at my log file. I found the commands that execute a2ps and ghostscript. I executed these commands on the command line and the printing process took the same amount of time as it did when I let apsfilter do the work. I did find though, that if i just use cat (cat > /dev/ltp0) to print an ascii text file it prints very fast...I don't know if this means anything or not... > Maybe apsfilter uses the wrong resolution for the printer ??? So > that the printer works in a not so suitable resolution ??? > Then one could try to tweak resolution in /etc/apsfilterrc ... > I tried specifying different resolutins for ghostscript myself on the command line as well as modifying the /etc/apsfilerrc file. Depending on the resolution I used I would either get the same behavior I was getting or my printer would repeatedly draw in sheets of paper and immediately spit them out with nothing printed on them. This seemed like it would go on forever so I had to deque the job and turn off the printer. > But possibly you only have a hardware configuration error. > How many LPT devices do you have ? > Might there be an interrupt conflict with another device ? > Or possibly you have interrupt problems and might try > to configure the lpt driver to poll the lpt device ... I don't think this is a problem. Considering the fact that I was able to cat an ascii text file to the print device (/dev/lpt0 is my only print device) and the fact that the kernel configuration shows no device confilict, I don't think that is a problem. Any other ideas? Thanks alot, Jesse Troy jtroy@vt.edu