Re: Printer problem

2013-12-14 Thread Brian
On Sat 14 Dec 2013 at 11:22:08 +0100, Gábor Hársfalvi wrote:

 We have got a HP Inkjet f2180 printer and we need use pure black ink
 instead of composite black every time.
 
 How to do this?

What driver package and PPD are you using?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/14122013125105.e5ccfb936...@desktop.copernicus.demon.co.uk



Re: Printer problem

2013-12-14 Thread Siard
Gábor Hársfalvi wrote:
 We have got a HP Inkjet f2180 printer and we need use pure black ink
 instead of composite black every time.
 
 How to do this?

The document to be printed should contain pure black, that is,
CMYK values C=0% M=0% Y=0% K=100%.
Printing offices also require this if you have your document printed
there.

As far as I can see, LibreOffice produces pure black.
PDF's produced by Scribus certainly comply with the standards.
I've often seen documents made with Word, converted to a PDF with a
third party program, that do _not_ have pure black. Don't know what the
latest state of affairs w.r.t. this is though.

In the case of a PDF, if it does not contain pure black, I know that
the latest Adobe Acrobat can do a conversion to repair this.
But of course, that is not a free program, and needs MacOSX or Windows.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131214191533.80474e72.shiems...@kpnplanet.nl



Re: Printer problem

2013-12-14 Thread Siard
Gábor Hársfalvi wrote off-list:
 Thanks.

 So we could tell the driver to use only the black ink for black
 texts/images?

No.  A document containing composite black text is simply not suitable
for printing.  You should try to get a better document.

Of course, you can tell the driver to print only black  white.
But then everything is in grayscale.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131214203709.3346de84.shiems...@kpnplanet.nl



Re: Printer problem

2013-12-14 Thread Brian
On Sat 14 Dec 2013 at 20:37:09 +0100, Siard wrote:

 Gábor Hársfalvi wrote off-list:

If his reply to my post was off-list it will never be seen by me (I only
receive and respond to on-list mail) or (obviously) anyone else. If
Gábor is looking for a response he should check whether any mail was
sent to debian-user.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/14122013202748.abc3ba1a7...@desktop.copernicus.demon.co.uk



Re: Printer Problem - An Insane Solution

2003-02-10 Thread Glenn English
On Mon, 2003-02-10 at 10:03, Thomas H. George,,, wrote:

 PS.  I was going to call this a cock-a-manie (sp?) solution but I can't 
 find the word in any of our dictionaries.  Anyone know a correct 
 spelling and dictionary entry?

Not at all sure, but I think it's cockamamie - it's a term my
grandparents used to use, so I suspect it came out of the 1920's.
It ought to be in the Dictionary of American Slang.

-- 
Glenn English
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: Printer Problem - An Insane Solution

2003-02-10 Thread Gary Turner
Glenn English wrote:

On Mon, 2003-02-10 at 10:03, Thomas H. George,,, wrote:

 PS.  I was going to call this a cock-a-manie (sp?) solution but I can't 
 find the word in any of our dictionaries.  Anyone know a correct 
 spelling and dictionary entry?

Not at all sure, but I think it's cockamamie - it's a term my
grandparents used to use, so I suspect it came out of the 1920's.
It ought to be in the Dictionary of American Slang.

FYI

gt@koko:~$ dict cockamamie
1 definition found

From WordNet (r) 1.7 [wn]:

  cockamamie
   adj : (informal terms) gave me a cockamamie reason for not
 going; wore a goofy hat; a silly idea; some wacky
 plan for selling more books [syn: {cockamamy}, {fool(a)},
  {goofy}, {sappy}, {silly}, {wacky}, {zany},
{unreasonable}]
gt@koko:~$



--
gt  [EMAIL PROTECTED]
 If someone tells you---
 I have a sense of humor, but that's not funny. 
  ---they don't.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: printer problem

2001-05-24 Thread Steve Gran
On Wed, 23 May 2001, Wayne Topa wrote:

 
 
 Subject: printer problem
 Date: Tue, May 22, 2001 at 07:23:54PM -0500
 
 In reply to:Thomas H. George
 
 Quoting Thomas H. George([EMAIL PROTECTED]):
  Trying to make printer (brother HL-730 on parallel port) work from 
  debian linux 2.2.19:
  
  lp testtxt
  
  and from Abiword in ximian gnome desk top.  Compiled the kernel with 
  parallel printer support and autoprobe.
  
 
 Look at the past months mail archive for discussion on this.
 
 I have a Brother HL-10V worling fine using magicfilter.  Could only
 get a great test page out of apsfilter. :(
 
 Works for every program I have tried.
 
 One other thought.  Have you compiled the kernel correctly?  A lot of
 parport options there.  Also have you included the parport options in
 the appends= in lilo.conf?  ie:
 append  = lp=parport0 parport=0x378,none
 
 ( 'none' means don't ise an IRQ, which isn't required for the printer)

I think  you want to try lpr foo.txt instead of lp foo.txt - it may just be 
that it doesn't recognize the command you're trying to give it.  If you can cat 
text to the printer, don't mess with you're base settings (IRQ, DMA, etc.) 
because the information is getting to the right port.  It's something either in 
what you're telling it (i.e., wrong command) or in the configuration (i.e., 
/etc/printcap is misconfigured).  Try man printcap for a description of what 
you should be seeing in the file, and compare irt to what you actually see.
Good luck,
Steve




re: printer problem

2001-05-24 Thread Thomas H. George
I have discovered that apsfilterconfig writes three filters for my 
Brother HL-730 laser printer (which can simulate an HP LJIIP).  In the 
printcap file it generates I find


  ascii|jet2p-letter-ascii-mono|jet2p

  lp|jet2p-letter-auto-mono|jet2p

  raw|jet2p-letter-raw|jet2p

The command lpr -Praw testtest  will print a simple text file written 
with vi.


In Abiword the print instruction with lpr -Plp will print test but not 
dingbats but the font is wrong - font 12 prints as font 30.


I have not discovered a use for the ascii filter.

I pass this along for whatever its worth



Re: printer problem

2001-05-23 Thread Wayne Topa

Subject: printer problem
Date: Tue, May 22, 2001 at 07:23:54PM -0500

In reply to:Thomas H. George

Quoting Thomas H. George([EMAIL PROTECTED]):
 Trying to make printer (brother HL-730 on parallel port) work from 
 debian linux 2.2.19:
 
 lp testtxt
 
 and from Abiword in ximian gnome desk top.  Compiled the kernel with 
 parallel printer support and autoprobe.
 

Look at the past months mail archive for discussion on this.

I have a Brother HL-10V worling fine using magicfilter.  Could only
get a great test page out of apsfilter. :(

Works for every program I have tried.

One other thought.  Have you compiled the kernel correctly?  A lot of
parport options there.  Also have you included the parport options in
the appends= in lilo.conf?  ie:
append  = lp=parport0 parport=0x378,none

( 'none' means don't ise an IRQ, which isn't required for the printer)

:-) HTH, YMMV, HAND :-)

-- 
There can never be a computer language in which you cannot write a
bad program.
___



Re: Printer Problem Solved..sorta..

2001-04-01 Thread Dale Morris
Doing some investigation, I find the problem lies more with StarOffice 5.2
than it does with my printer configuration. I changed lpd to lprng and have
configured it. ABI word prints fine, I can print from mutt, netscape, lyx,
etc.. but nothing happens with StarOffice, the printer just keeps spitting
out blank pages. On an email thread, I saw there were some changes that had
to be made to the printcap file having to do with *levels*? but I've decided
to remove StarOffice. It's so slow loading that I never use it anyhow. 





 The problem is when I try to print from StarOffice. The printer starts but
 nothing is printed to the page. Anyone else have this problem or know the
 solution? I'm using apsfilter, lpd, and an epson stylus color 600 printer.



Re: Printer Problem

2001-03-19 Thread kmself
on Sun, Mar 18, 2001 at 07:59:35PM +0100, Stephan Kulka ([EMAIL PROTECTED]) 
wrote:
 When I try to print out a file , I get the following message:
 
 [EMAIL PROTECTED] - cannot open connection Connection refused
 Make sure LPD server is running on the system.
 
 I am quite confused, because the lpd daemon is started at startup (I even
 rebooted to be sure).
 What is this LPD?? My network is working, I never changed the
 configuration files for the network,so the local network should be ok as
 well.

Have you configured a printer?  I'm not particularly handy at this, but
tend to stumple through printtool, a graphical utility, with some
success.

-- 
Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/
 What part of Gestalt don't you understand?   There is no K5 cabal
  http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org


pgpT6pTwgZbVO.pgp
Description: PGP signature


Re: Printer Problem

2001-02-02 Thread ktb
On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:
 My printer was working perfectly.  I rebuilt the kernel allowing 
 autoprobe.  Printer no longer responds even to
 
cat lptest  /dev/lp0  where lptest is a small text file
 
 and
 
lp lptest
 
 responds normally but nothing is printed and nothing is in the print que.
 
cat /proc/ioports  shows the correct value (0378-037f) for 
 parport0
 
cat /proc/parport/0/irq  reports none (should be irq 7 but is 
 this needed?)
 
 Documentation/parport indicates that a lilo command parport=0x378,7 
 should work but /sbin/lilo rejects this line placed anywhere in 
 lilo.conf.  The documentation also implies that the irq value reported 
 by cat/proc/parport/0/irq can be changed but I don't understand how.
 
 It seems to me that everything is working normally but the printer is 
 not receiving the transmission.  The printcap file is unaltered and lp 
 is directed to lp0.
 
 Where is the missing link?
 

What does dmesg say about parport?
kent

-- 
I'd really love ta wana help ya Flanders but... Homer Simpson



Re: Printer Problem

2001-02-02 Thread Thomas H. George,,,610-444-2626
Thanks for the suggestion. I had not learned about
dmesg. Unfortunately it reported everything in order - i.e. parport0 using
0378 and irq 7. I must look elsewhere for the problem.

Tom George

ktb wrote:
On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:
  My printer was working perfectly.  I rebuilt the kernel allowing autoprobe.  Printer no longer responds even to   cat lptest  /dev/lp0  where lptest is a small text fileand   lp lptestresponds normally but nothing is printed and nothing is in the print que.   cat /proc/ioports  shows the correct value (0378-037f) for parport0   cat /proc/parport/0/irq  reports none (should be irq 7 but is this needed?)Documentation/parport indicates that a lilo command parport=0x378,7 should work but /sbin/lilo rejects this line placed anywhere in lilo.conf.  The documentation also implies that the irq value reported by cat/proc/parport/0/irq can be changed but I don't understand how.It seems to me that everything is working normally but the printer is not receiving the transmission.  The printcap file is unaltered and lp is !
directed to lp0.Where is the missing link?
What does dmesg say about parport?kent




Re: Printer Problem

2001-02-02 Thread Thomas H. George,,,610-444-2626
Thanks for the suggestion; I had not yet learned about dmesg.  
Unfortunately, dmesg reported all in order with parport - i.e. using 
0378 and irq 7.  I must look elsewhere for my problem.


Tom George

ktb wrote:


On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:

My printer was working perfectly.  I rebuilt the kernel allowing 
autoprobe.  Printer no longer responds even to


   cat lptest  /dev/lp0  where lptest is a small text file

and

   lp lptest

responds normally but nothing is printed and nothing is in the print que.

   cat /proc/ioports  shows the correct value (0378-037f) for 
parport0


   cat /proc/parport/0/irq  reports none (should be irq 7 but is 
this needed?)


Documentation/parport indicates that a lilo command parport=0x378,7 
should work but /sbin/lilo rejects this line placed anywhere in 
lilo.conf.  The documentation also implies that the irq value reported 
by cat/proc/parport/0/irq can be changed but I don't understand how.


It seems to me that everything is working normally but the printer is 
not receiving the transmission.  The printcap file is unaltered and lp 
is directed to lp0.


Where is the missing link?



What does dmesg say about parport?
kent





Re: Printer Problem

2001-02-02 Thread Thomas H. George,,,610-444-2626
I was surprised!  After running dmesg I found my printer working again.  
I don't understand why this is so but, as I had done nothing else (I 
send these messages from another computer), dmseg must have corrected 
the problem.


Thanks again for the help.

Tom George

Thomas H. George,,,610-444-2626 wrote:

Thanks for the suggestion.  I had not learned about dmesg.  
Unfortunately it reported everything in order - i.e. parport0 using 
0378 and irq 7.  I must look elsewhere for the problem.


Tom George

ktb wrote:


On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:

My printer was working perfectly.  I rebuilt the kernel allowing 
autoprobe.  Printer no longer responds even to


   cat lptest  /dev/lp0  where lptest is a small text file

and

   lp lptest

responds normally but nothing is printed and nothing is in the print que.

   cat /proc/ioports  shows the correct value (0378-037f) for 
parport0


   cat /proc/parport/0/irq  reports none (should be irq 7 but is 
this needed?)


Documentation/parport indicates that a lilo command parport=0x378,7 
should work but /sbin/lilo rejects this line placed anywhere in 
lilo.conf.  The documentation also implies that the irq value reported 
by cat/proc/parport/0/irq can be changed but I don't understand how.


It seems to me that everything is working normally but the printer is 
not receiving the transmission.  The printcap file is unaltered and lp 
is !

directed to lp0.

Where is the missing link?



What does dmesg say about parport?
kent







Re: Printer Problem

2001-02-02 Thread ktb
On Fri, Feb 02, 2001 at 03:03:31PM -0500, Thomas H. George,,,610-444-2626 wrote:
 I was surprised!  After running dmesg I found my printer working again.  
 I don't understand why this is so but, as I had done nothing else (I 
 send these messages from another computer), dmseg must have corrected 
 the problem.
 
 Thanks again for the help.
 

H, dmesg just shows the output of boot.  I'm glad it is working now
though:)
kent

-- 
I'd really love ta wana help ya Flanders but... Homer Simpson



Re: Printer problem

1999-11-04 Thread John Pearson
On Tue, Nov 02, 1999 at 10:57:59PM +, Alisdair McDiarmid wrote
 On Tue, Nov 02, 1999 at 06:43:00PM +0100, SGaerner wrote:
  You have to edit your local /etc/printcap.
  Add a line
  rm=YOUR_SERVER_IP:\
  rp=lp:\
  
  But I think that you only have to uncomment und modify some lines in your 
  standard
  Debian /etc/printcap.
 
 i'm currently having the same problem.
 
 i've got a printer set up on skinny, which prints locally fine.
 the printcap is:
 
 lp|hplj|HP Laserjet 1100:\
 :lp=/dev/lp0:sd=/var/spool/lpd/hplj:\
 :sh:pw#80:pl#72:px#1440:mx#0:\
 :if=/etc/magicfilter/ljet4l-filter:\
 :af=/var/log/lp-acct:lf=/var/log/lp-errs:
 
 the printcap on letdown is:
 
 lp|hplj|HP Laserjet 1100:\
   :lp=/dev/null:sd=/var/spool/lpd/hplj:rm=skinny.wasters:rp=lp:\
   :sh:pw#80:pl#72:px#1440:mx#0:\
   :if=/etc/magicfilter/ljet4l-filter:\
   :af=/var/log/lp-acct:lf=/var/log/lp-errs:
 

My printcap, that works for remote printing, looks like this:

lp|huiac|lj|HP Laserjet 6MP:\
:lp=:\
:rm=huiac:\
:sd=/var/spool/lpd/lp:\
:af=/var/log/lp-acct:\
:lf=/var/log/lp-errs:\
:pl#70:\
:pw#80:\
:pc#150:\
:mx#0:\
:sh:

Maybe specifying 'lp=/dev/null' is getting your work thrown away before
lpd notices you've specified a remote printer?


John P.
-- 
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Oh - I - you know - my job is to fear everything. - Bill Gates in Denmark


Re: Printer problem

1999-11-04 Thread John Pearson
On Wed, Nov 03, 1999 at 12:23:06AM +, Brian Schramm wrote
 I am sorry.  I did not give a good explanation for the problem.  I am 
 talking security.  I have the printer setup in the printcap file but 
 it is not working because it cannot connect to it.  The machine at the 
 other end says it cannot allow the connection.  I use to create a 
 hosts.lpd file and that would work but I know that this version has 
 some other file to edit.
 
 Brian
 

Slink includes two separate print spoolers - lpr and lprng - which use
different configuration files.  Which are you using?


John P. 
-- 
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Oh - I - you know - my job is to fear everything. - Bill Gates in Denmark


Re: Printer problem

1999-11-04 Thread Alisdair McDiarmid
On Thu, Nov 04, 1999 at 09:55:30AM +1030, John Pearson wrote:
 On Tue, Nov 02, 1999 at 10:57:59PM +, Alisdair McDiarmid wrote
  
  i've got a printer set up on skinny, which prints locally fine.
  the printcap on letdown is:
  
  lp|hplj|HP Laserjet 1100:\
  :lp=/dev/null:sd=/var/spool/lpd/hplj:rm=skinny.wasters:rp=lp:\
  :sh:pw#80:pl#72:px#1440:mx#0:\
  :if=/etc/magicfilter/ljet4l-filter:\
  :af=/var/log/lp-acct:lf=/var/log/lp-errs:
 
 My printcap, that works for remote printing, looks like this:
[snip]
 Maybe specifying 'lp=/dev/null' is getting your work thrown away before
 lpd notices you've specified a remote printer?

That appears to be the problem - it works perfectly now. Thanks,
John!


Re: Printer problem

1999-11-02 Thread SGaerner
You have to edit your local /etc/printcap.
Add a line
rm=YOUR_SERVER_IP:\
rp=lp:\

But I think that you only have to uncomment und modify some lines in your 
standard
Debian /etc/printcap.


Brian Schramm wrote:

 I hope this gets to the list.  I never saw my question post the last
 time.

 I am running Debian slink and I need to share my printers with my
 networked Debian slink workstations.  I know that there is a file I
 need to modify in order to give permission to each computer to do
 this.  I just forgot which one and what to put in it.

 Can someone please help me on this?

 Thanks.

 Brian Schramm
 [EMAIL PROTECTED]

 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null


Re: Printer problem

1999-11-02 Thread Alisdair McDiarmid
On Tue, Nov 02, 1999 at 06:43:00PM +0100, SGaerner wrote:
 You have to edit your local /etc/printcap.
 Add a line
 rm=YOUR_SERVER_IP:\
 rp=lp:\
 
 But I think that you only have to uncomment und modify some lines in your 
 standard
 Debian /etc/printcap.

i'm currently having the same problem.

i've got a printer set up on skinny, which prints locally fine.
the printcap is:

lp|hplj|HP Laserjet 1100:\
:lp=/dev/lp0:sd=/var/spool/lpd/hplj:\
:sh:pw#80:pl#72:px#1440:mx#0:\
:if=/etc/magicfilter/ljet4l-filter:\
:af=/var/log/lp-acct:lf=/var/log/lp-errs:

the printcap on letdown is:

lp|hplj|HP Laserjet 1100:\
:lp=/dev/null:sd=/var/spool/lpd/hplj:rm=skinny.wasters:rp=lp:\
:sh:pw#80:pl#72:px#1440:mx#0:\
:if=/etc/magicfilter/ljet4l-filter:\
:af=/var/log/lp-acct:lf=/var/log/lp-errs:

printing on letdown does nothing: lpq says no printable jobs in
queue, but skinny doesn't appear to even get anything. there are
no logs or output from lpd on either machine to suggest that
anything happened. i think i've set up /etc/lpd.perms to allow
access, but i can't be sure (the only line is DEFAULT ACCEPT).

what could it possibly be? (i have RTFM and FAQ and HOWTO and they
don't help).

thanks,
-- 
alisdair mcdiarmid[EMAIL PROTECTED]
[everything that matters has gone http://wasters.org/]


Re: printer problem not solved anymore {SOLVED]

1999-04-19 Thread Mans Joling




Re: printer problem

1999-04-17 Thread Mark Phillips

 I sent this a few days ago but have gotten no response, so I'll try again.
 
 I have a Hamm system. 
 I've been trying about setting up a Tek printer and have lpd
 confused. If I go into lpc and ask for status lp2 I get
 
 
 lpc status lp2
 lp2:
 queuing is enabled
 printing is enabled
 no entries
 no daemon present

I'm not sure that this is the answer to your question, but it would
seem that your printer daemon is not running --- what happens when it
is running?  Ie, after running (as root)

/etc/init.d/lpd restart

what messages do you get?

Cheers,

Mark.



_/\___/~~\
/~~\_/~~\__/~~\__Mark_Phillips
/~~\_/[EMAIL PROTECTED]
/~~\HE___/~~\__/~~\APTAIN_
/~~\__/~~\
__
They told me I was gullible ... and I believed them! 




Re: printer problem not solved anymore

1999-04-17 Thread Richard Harran
The error indicates that lpd is not running.  Have you tried doing the 
lpr filename
!after! having done as root:
lpd
It looks like lpd has not been started properly.  I guess you could try
installing lpr again.  You could also try looking at the output of kmesg
to see if there is a relavent (lpd related) error there.
Also try:
ls /etc/rc?.d | grep S[0-9]*lpd
to see if lpd is being started anywhere (should get at least one
'Snlpd').  If not, reinstalling lpr should sort this out.  You could
also manually add lpd starting (but this is probably not the easiest
thing to do)

HTH
Rich

Mans Joling wrote:
 
 Hi
 I have running into a new problem.
 Yesterday I uncomment the lastline in dj500-filter and I add a line
 default cat  and so on.
 Then the  printer works fine.
 Today when I say (as normal user) lpr filename (normal text)
 lpr: connect:No such file or directory
 jobs queued, but cannot start deamon.
 When I do ps -ax I see two processes /usr/sbin/lpd
 bash: lpd: command not found
 When I do lpq
 lp is ready and printing.
 As root
 lpd  no messages
 Any idea what is worng
 Mans Joling
 
 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null