This may be a memory issue... Remember that the rasterizer buffers the entire page on the Linux machine first then attempts to send it en-masse to the printer. Some printers drivers deal with this by sending enough code to print a line or two of graphics at a time. Others (such as HPGL & HPPCL) try to send the entire page. If your printer cannot handle the volume of data coming it's way, it will normally stop half way or spit out half printed pages, followed by junk. -JMS -----Original Message----- From: Guilherme Cirne [mailto:[EMAIL PROTECTED]] Sent: Friday, August 17, 2001 10:00 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [newbie] Network Printer on Win98 At 13:53 15/08/01 -0400, you wrote: >If you are at least getting smbclient to work, you are almost there! > >Now the problem is how Cups' filters treat the remote winblows printer. > >Cups tries to run thru the Linux/Unix style printer filters which feed >GIMP/GHOSTSCRIPT or some other ratherizer. The problem is that the >rasterizer rarely puts out information that is compatible with the >winblows printers... > >Your first step should be to set up the Winblows printer as a text mode >printer and try printing plain text to it from Linux/Cups. > >Make sure that you can get plain text to print FIRST! > >If you can this far, you can start searching for Winblows compatible >Linux/Cups filters in the driver database. > >Additional printer control init sequences may differ between CUPS and >Winblows which is another problem... > >-JMS I finally got it to work. The only strange thing is that sometimes the printer stops in the middle of a page and I have to start again. But anyway thanks for the help. Guilherme Cirne [EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://wwww.mandrakestore.com
