This is a versatile printer with many options. Do you have to send some setup string to make it talk postscript? Are your print files good postscript? Print one to a file and try to read it with gv. And, look at it with vi. Once you have a good postscript file, just cat the file to the /dev/lp0 or where ever the printer is attached. If that works, you should have no trouble printing. I bet you are using some complicated print filtering system instead of some simple filter you wrote yourself. Joel On Sun, Apr 28, 2002 at 06:16:18PM +0200, Andreas Berglund wrote: > On Sun, Apr 28, 2002 at 02:07:46AM CEST or thereabouts, Joel Hammer wrote: > > Why are you trying any drivers at all? Linux apps send postscript files. Try > > a raw filter or a passthrough filter, if you have that choice. > > Joel > > I tried the raw filter and it still produces the same gibberish. > > Andreas > > > > On Sun, Apr 28, 2002 at 02:26:51AM +0200, Andreas Berglund wrote: > > > On Sat, Apr 27, 2002 at 02:46:27AM CEST or thereabouts, Joel Hammer wrote: > > > > This thing is a PostScript printer. What is your problem? > > > > > > My problem is I can't get it to print anything else than pure ascii. > > > For example when setting up the printer in cups and then printing a > > > testpage I get page after page of postscript codes. I've tried the > > > different 4029 drivers that cups has to offer, maybe I should try the > > > generic postscript driver instead. I've also tried other printing > > > systems such as LPRng with no luck. > > > > > > Andreas > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
