Printing Problems..


 
Thread Tools Search this Thread
Operating Systems Linux Printing Problems..
# 1  
Old 03-15-2006
Question Printing Problems..

Dear All..
When printing(Epson DotMatrix 9pinX136Cols) an graphics(Graphics2D) document through my Java application, the printer simply take a round and drop the paper out. Nothing printed is it my printer driver(currently using omni driver) problem. Any one of you pls suggest me the suitable driver. Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Perl - Problems iwith colors while printing from dynamic array at runtime..

Hi Perl folks, I am having problems printing elements from an array at runtime. I wish to push elements into array at runtime and the print it later. Now I wish to print this matrix using colors. So I do something like this to enter the runtime values in array: ... (1 Reply)
Discussion started by: som.nitk
1 Replies

2. AIX

printing problems...

hello... we have just recently purchased an ibm h80 system to replace our old machine. the new machine is running aix 5.2 and yesterday i had just completed installing all the remote printers that are connected to windows 2k pc's. today i tried to send a print job to one of them and nothing... (1 Reply)
Discussion started by: petrofyed
1 Replies

3. UNIX for Dummies Questions & Answers

Printing problems

Hi, the print spooler from my unix box keeps putting a header before every page, looks as below User: root Host: blemain.blemain.local Class: blemain.blemain.local Job: SPC075 then it forces the rest of the print to spread accross 2 pages (should be single page prints). Any idea... (0 Replies)
Discussion started by: blemainuser
0 Replies

4. UNIX for Dummies Questions & Answers

lpq, lpr and printing problems

good day! i would just like to ask for advice regarding an lp problem i have.. we currently migrated a GIS appl from sol 2.6 to sol 8 but maintained the same version of jetadmin (for the appl plotters and printers). we are able to print files on a printer but not on a plotter. the... (1 Reply)
Discussion started by: maria_iris
1 Replies

5. UNIX for Dummies Questions & Answers

Printing problems

I am not able to print plain text in a correct manner. When I issue the command "lp -ddestination_printer myfile.txt" the printer prints a page with the following contents: Feb 24 11:26 2005 myfile.txt Page 1 ## Configured using SAM by root on Tue The line beginning... (3 Replies)
Discussion started by: ascanestro
3 Replies

6. SCO

Printing Problems with SCO 5.0

I have several printers setup but nothing prints. I get the following error email Subject: Status of lp request aclj3-2297 Your request aclj3-2297 destined for aclj3 encountered an error while printing on printer aclj3. Reason for failure: cat: cannot open 0: No such file or... (1 Reply)
Discussion started by: Jessie Nand
1 Replies

7. Solaris

emulation problems printing from sun solaris

Genicom LG05 printer with LG emulation. Due to problems with printer a replacement printer was installed with LP+ emulation only. Does the queue on UNIX have to be modified or told about the change in emulation for it to print from sun solaris unix. What's the command? (0 Replies)
Discussion started by: ITBT
0 Replies

8. UNIX for Dummies Questions & Answers

Printing Problems

I have a problem here. I have a printer that is connected to a silicon graphics O2 machine (a Laser Jet 6MP) which is running under the Laser Jet 6 printer driver. I don't have any problems printing from the UNIX box. However, I do have the printer networked through our local intranet (using LPR... (2 Replies)
Discussion started by: bobmcgee
2 Replies

9. UNIX for Advanced & Expert Users

Printing Problems in unix ... ( Bar-cdoe - Ip Printing)

Hi guys ... i need ur help with some printing problem in unix ... first prob. : i wanna print from my NCR unix to an Win NT , Ip based printing server ( HP JetDirect ) . My issue , is it possible to print directly to an Ip address from unix ? How do i make it work to get any results ?... (3 Replies)
Discussion started by: QuickSilver
3 Replies

10. UNIX for Dummies Questions & Answers

Printing via SCO Unix problems ;-(

I get the following when printing from a SCO Unix application { Who are you ?} The user is printing to a printer on a network print sharing device HP 500x. I think this printer is shared via the Unix machine. How does one set up printer sharing on Unix and access permissions for them? ... (2 Replies)
Discussion started by: JoseHose
2 Replies
Login or Register to Ask a Question
tunelp(8)						     Linux Programmer's Manual							 tunelp(8)

NAME
tunelp - set various parameters for the lp device SYNOPSIS
tunelp <device> [-i <IRQ> | -t <TIME> | -c <CHARS> | -w <WAIT> | -a [on|off] | -o [on|off] | -C [on|off] | -r | -s | -q [on|off] | - T [on|off] ] DESCRIPTION
tunelp sets several parameters for the /dev/lp? devices, for better performance (or for any performance at all, if your printer won't work without it...) Without parameters, it tells whether the device is using interrupts, and if so, which one. With parameters, it sets the device characteristics accordingly. The parameters are as follows: -i <IRQ> specifies the IRQ to use for the parallel port in question. If this is set to something non-zero, -t and -c have no effect. If your port does not use interrupts, this option will make printing stop. The command tunelp -i 0 restores non-interrupt driven (polling) action, and your printer should work again. If your parallel port does support interrupts, interrupt-driven printing should be somewhat faster and efficient, and will probably be desirable. NOTE: This option will have no effect with kernel 2.1.131 or later since the irq is handled by the parport driver. You can change the parport irq for example via /proc/parport/*/irq. Read /usr/src/linux/Documentation/parport.txt for more details on parport. -t <TIME> is the amount of time in jiffies that the driver waits if the printer doesn't take a character for the number of tries dictated by the -c parameter. 10 is the default value. If you want fastest possible printing, and don't care about system load, you may set this to 0. If you don't care how fast your printer goes, or are printing text on a slow printer with a buffer, then 500 (5 seconds) should be fine, and will give you very low system load. This value generally should be lower for printing graphics than text, by a factor of approximately 10, for best performance. -c <CHARS> is the number of times to try to output a character to the printer before sleeping for -t <TIME>. It is the number of times around a loop that tries to send a character to the printer. 120 appears to be a good value for most printers in polling mode. 1000 is the default, because there are some printers that become jerky otherwise, but you must set this to `1' to handle the maximal CPU efficiency if you are using interrupts. If you have a very fast printer, a value of 10 might make more sense even if in polling mode. If you have a really old printer, you can increase this further. Setting -t <TIME> to 0 is equivalent to setting -c <CHARS> to infinity. -w <WAIT> is the number of usec we wait while playing with the strobe signal. While most printers appear to be able to deal with an extremely short strobe, some printers demand a longer one. Increasing this from the default 1 may make it possible to print with those print- ers. This may also make it possible to use longer cables. It's also possible to decrease this value to 0 if your printer is fast enough or your machine is slow enough. -a [on|off] This is whether to abort on printer error - the default is not to. If you are sitting at your computer, you probably want to be able to see an error and fix it, and have the printer go on printing. On the other hand, if you aren't, you might rather that your printer spooler find out that the printer isn't ready, quit trying, and send you mail about it. The choice is yours. -o [on|off] This option is much like -a. It makes any open() of this device check to see that the device is on-line and not reporting any out of paper or other errors. This is the correct setting for most versions of lpd. -C [on|off] This option adds extra ("careful") error checking. When this option is on, the printer driver will ensure that the printer is on- line and not reporting any out of paper or other errors before sending data. This is particularly useful for printers that normally appear to accept data when turned off. NOTE: This option is obsolete because it's the default in 2.1.131 kernel or later. -s This option returns the current printer status, both as a decimal number from 0..255, and as a list of active flags. When this option is specified, -q off, turning off the display of the current IRQ, is implied. -T [on|off] This option tell the lp driver to trust or not the IRQ. This option makes sense only if you are using interrupts. If you tell the lp driver to trust the irq, then, when the lp driver will get an irq, it will send the next pending character to the printer uncon- ditionally, even if the printer still claims to be BUSY. This is the only way to sleep on interrupt (and so the handle the irq printing efficiently) at least on Epson Stylus Color Printers. The lp driver automagically detects if you could get improved per- formance by setting this flag, and in such case it will warn you with a kernel message. NOTE: Trusting the irq is reported to corrupt the printing on some hardware, you must try to know if your printer will work or not... -r This option resets the port. It requires a Linux kernel version of 1.1.80 or later. -q [on|off] This option sets printing the display of the current IRQ setting. NOTES
-o, -C, and -s all require a Linux kernel version of 1.1.76 or later. -C requires a Linux version prior to 2.1.131. -T requires a Linux version of 2.1.131 or later. BUGS
By some unfortunate coincidence the ioctl LPSTRICT of 2.0.36 has the same number as the ioctl LPTRUSTIRQ introduced in 2.1.131. So, use of the -T option on a 2.0.36 kernel with an tunelp compiled under 2.1.131 or later may have unexpected effects. FILES
/dev/lp? /proc/parport/*/* tunelp 7 May 1999 tunelp(8)