KnightFlyer
Jr. Member

Offline
Posts: 28
|
 |
« Reply #3 on: July 28, 2010, 07:51:43 AM » |
|
I will get back with you, the systems are in another city. I only have an inkjet parallel printer here at home, it installs OK.
At the customer's site we have a 2009 PCLOS print server running with 2 parallel okidata impact Invoice printers, they were installed with the PCC tool, specifying cups and with no-driver raw mode specified. This works best, for our application. There is no problem with that system. Using the same physical computer, but with PCLOS (2010.7 all updates) Printer installed with the PCC tool, we get a working daemon, but when data is sent through the spooler or direct, whether it be just the date, or a directory listing, we get slow printing and garbage. Then when we drop the old hard drive back in with 2009 PCLOS everything is OKAY. Another server on that network has already been upgraded to 2010, and it has a same type printer, same phenomena, and we can't afford the time to take it down, to downgrade to 2009. Our stop-gap measure is to route all printing to the 2009 Print server. This results in another issue, as that 2009PCLOS machine cannot import 2010PCLOS NFS shares. I am sure my customer is getting tired of me and PCLOS. I am sure nothing is wrong with cups, spooler, or pcc.
To test Raw Parallel Impact printers you can login as root, and at the command line prompt type : cat >/dev/lp0. then your keyboard will echo to the printer, after every <RETURN>.
If this simple test fails, then of course the spoolers, and cups will not work, drivers or raw.
My new thoughts are to yank out expansion parallel card, use a single port and assign irq and address in the bios. Anyone else have advice or suggestions?
|