Have you tried a generic PCL5e, PostScript or dot-matrix driver and send it strait to the printer? a lot times a generic driver will work. I would imagine you have a PCL driver on the windows machine. Also have you set up a share on the windows machine. Make sure you gone through all the basics. > On Tue, 2007-01-23 at 07:23 +0900, John Summerfield wrote: >> > 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. > > Maybe I'm just dumb. But, I thought I explained that the Okidata is > connected to the Windows PC, and is configured there with the Windows > driver. The printer is shared, so I added it to the CentOS 4.4 server > as a raw CUPS queue to let all the processing happen on the Windows box. > > Printing works from console apps on the CentOS server. But, OOo > documents don't print properly. I've assumed that this is because the > Windows driver for the Okidata doesn't understand postscript, so it's > just printing the file directly. So, that's why I was asking if my > reasoning was correct or if something else was broken. > >> 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. > > Yes, that's what I've been thinking. And, it looks like the Windows > driver can't do postscript. > >> 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. > > Agreed. > >> Check IBM's Omni driver suite (which should be installed or on your >> install media), there may be something usable there. > > I've tried all those drivers; basically everything I could find on > linuxprinting.org about getting an Okidata ML 395 working. Nothing has > worked. > > I have to be doing something wrong on the printer itself. Changing the > printer's emulation type should have let me use one of the corresponding > drivers on the CUPS end. > > I'll give it another kick. Then maybe some drop kicks. Then a > "whoops....don't know how it went down the stairs...strange!" > > Regards, > > Ranbir > > -- > Kanwar Ranbir Sandhu > Linux 2.6.19-1.2895.fc6 i686 GNU/Linux > 18:00:55 up 1 day, 2:56, 2 users, load average: 0.03, 0.21, 0.19 > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >