Hi All, I have a raw print queue configured in CentOS 4.4 for a printer connected to a Windows PC. The printer doesn't have a Linux driver of any sort, so this was the only way to print to it. The printer is an Okidata dot matrix printer. Users can print to it from a console application, but if they try printing to it from OOo Writer, the printer spits out reams of pages with what looks like postscript code. The very first page has a line that says "%! PS-Adobe-3.0". Even though the print queue is configured as "raw", why are OOo Writer print jobs still sent as postscript documents? I'm don't know too much about printing, postscript, etc., so I don't know if this is normal or if something broke. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.19-1.2895.fc6 i686 GNU/Linux 13:52:05 up 22:47, 2 users, load average: 0.39, 0.36, 0.26
Kanwar Ranbir Sandhu wrote:> Hi All, > > I have a raw print queue configured in CentOS 4.4 for a printer > connected to a Windows PC. The printer doesn't have a Linux driver of > any sort, so this was the only way to print to it. > > The printer is an Okidata dot matrix printer. Users can print to it > from a console application, but if they try printing to it from OOo > Writer, the printer spits out reams of pages with what looks like > postscript code. The very first page has a line that says "%! > PS-Adobe-3.0". > > Even though the print queue is configured as "raw", why are OOo Writer > print jobs still sent as postscript documents? I'm don't know too much > about printing, postscript, etc., so I don't know if this is normal or > if something broke. > > Regards, > > Ranbir >what type of okidata line printer and how is it connected to the network? there are some generic dot matrix drivers for linux out there that may work for you, and depending on your model some model specific linux drivers at okidata.com.
Kanwar Ranbir Sandhu wrote:> Hi All, > > I have a raw print queue configured in CentOS 4.4 for a printer > connected to a Windows PC. The printer doesn't have a Linux driver of > any sort, so this was the only way to print to it. > > The printer is an Okidata dot matrix printer. Users can print to it > from a console application, but if they try printing to it from OOo > Writer, the printer spits out reams of pages with what looks like > postscript code. The very first page has a line that says "%! > PS-Adobe-3.0". > > Even though the print queue is configured as "raw", why are OOo Writer > print jobs still sent as postscript documents? I'm don't know too much > about printing, postscript, etc., so I don't know if this is normal or > if something broke. > > Regards, > > RanbirWhy would you want to configure the print que as raw when you are printing through an application package? I understand that the console application may need the raw que as it is probably doing all the printer formatting with the application. Simply create another printer que to the same printer using the proper printer driver for that printer and all will be well. Mark Snyder JMK Computerized TDIS 703 S. Glover Ave. Urbana, IL 61802 (800)397-8100
Kanwar Ranbir Sandhu wrote:> Hi All, > > I have a raw print queue configured in CentOS 4.4 for a printer > connected to a Windows PC. The printer doesn't have a Linux driver of > any sort, so this was the only way to print to it.Umm. That means that the applications have to have a driver for the printer.> > The printer is an Okidata dot matrix printer. Users can print to it > from a console application, but if they try printing to it from OOo > Writer, the printer spits out reams of pages with what looks like > postscript code. The very first page has a line that says "%! > PS-Adobe-3.0".So OOo thinks it's printing to a postscript printer. This is not going to work unless the Windows peecee translates postscript to whatever the printer expects.> > Even though the print queue is configured as "raw", why are OOo Writer > print jobs still sent as postscript documents? I'm don't know too much > about printing, postscript, etc., so I don't know if this is normal or > if something broke.Something broke; the problem is there right behind your eyes:-) If you don't have a Linux printer driver for that printer, you're not going to get far unless something on Windows does the translation. Check IBM's Omni driver suite (which should be installed or on your install media), there may be something usable there. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list