Re: Printing Problem
hi ya roberto
on your print server...
d/l and install magicfilter to make life 10x easier
vi /etc/printcap
#
# http://www.Linux-Consulting.com/Downloads/LPR/printcap
#
lp|Epson800:\
:lp=/dev/lp0:\
:sd=/var/spool/lpd:\
:pw:132:\
:fq:\
:sh:mx#0:\
:if=/usr/local/sbin/printers/stc800:\
:lf=/var/spool/lpd/lp-log:
--
-- you might wanna look for say stc400 instead
-- in that magicfilter directory
--
restart lpd ...
lpr /etc/printcap
-----------------
for your other PCs... those would look at your printserver as
a network printer
for your other linux boxes ... printing to the linux box w/
the epson physcially connected to it
vi /etc/printcap
#
# ip# of the print server
#
lp|Epson800:\
:sd=/var/spool/lpd/lp:\
:rm=w.x.y.z:
resstart lpd ...
post any error messages
and to make things fun...
- print an asci file first
- print a very very small postscript file
- print the tiger
- print from netscape
- print pages side-by-side
c ya
alvin
On Tue, 4 Feb 2003, Roberto Sanchez wrote:
> I am desperately in need of some help here. Over the past week I have been
> completely unsuccesful in getting my printer to cooperate. I have an Epson
> Stylus Color 400 connected to a Pentium Pro 200 running Debian Woody.
> Ultimately I need this printer available over my small home network.
>
> I have tried practically every tutorial and howto that I have been able to
> find. I have tried using Foomatic, PDQ and printtool with no success. I
> have visited linuxprinting.org and downloaded the various automatically
> generated driver files and nothing works. Every time I go to print I get
> garbage (since my cheap inkjet apparently does not speak post script).
>
> What I need at this point is a step-by-step that contains all the info
> (unlike the situation with foomatic/linuxprinting where each one refers to
> the user to the other document for more info). I would really appreciate
> some help with this very frustrating problem. I am typically quite savvy
> with computers and have little trouble resolving difficult issues, but this
> has really thrown me for a loop.
>
Reply to: