Thanks for your thoughts, no luck though.
Tried setting the printer in windows to print after last page spooled and
print directly to printer but no change.
Have removed the 'rm' command from the print command also so that I can
check on the file being printed.
I cant find any options other than postscript and raw for the SCO lp
Whatever options I try, my printer simply prints a few characters jammed
As the file created on my unix box each time I send a print request from
windows it appears to be binary, this is not my area so I am assuming here,
this is probably be what is causing the problem. Also I have naturally
tested that a plain text file created in unix prints fine.
Thanks agin for your thoughts, perhaps someone else will pick up on this.
> > Am running Samba V2.2.7a on a SCO 5.0.2 system.
> > The printer 'spmgm3' is a valid unix printer attached to a wyse
> > terminal at /dev/prn1c06.
> > Have added the following to smb.conf to make 'spmgm3' available to
> > windows users.
> > [spmgm3]
> > printing = sysv
> > comment = Johns Test Printer
> > browseable = yes
> > printable = yes
> > printer name = spmgm3
> > public = yes
> > writable = yes
> > create mode = 0755
> > path = /tmp
> > print command = lp -o nobanner -s -c -d %p %s > /dev/null 2>&1 ; rm
> > %s printer driver = Epson LX-300+
> > The printer 'spmgm3' then appears in the network neighborhood, and I
> > am able to create this printer on a windows box. When I print to it, a
> > file '/tmp/smbprn.000004.a0079f' is created and I assume sent to the
> > Epson printer 'spmgm3'.
> > Problem is that the printer prints about 2 characters and locks up,
> > requiring a restart. Looking at the file above is no help as it is not
> > readable. It appears to be a compiled file created by the print
> > process from windows.
> > Can anyone help me with this one??
> > Thanks and regards,
> > John Clarke
> Hi John,
> in the Windows system control go to the printers properties,
> in the extended settings set
> "start printing after spooling last page". This prevents
> a connection timeout which might happen if the first part of
> the print job is submitted and the next page - i.e. a
> complicated graphics - needs a longer time to be printed.
> Another possible problem source is automatic print job
> translation by the print system itself. Some print systems
> (i.e. LPRng i use) classify incoming print jobs to be
> raw print data, postscript, dvi, groff output or plain text...
> and run filters to enforce postscript output.
> When printing from Windows systems your jobs file type
> is binary or raw print data. When running LPRng lpr command
> I can specify "-l" or "-b". Unfortunately I do not know sysv
> printing options for this, please check the man page.
> Yet another problem might be the "lpr ... ; rm ...".
> On some systems the lpr command returns immediately
> while doing the printing in a background process. In this
> case the rm removes the print data file while printing
> is running. LPRng's lpr command has a "-r" option
> to remove the printed file after finishing printing.
> This allows to run "lpr -r ..." instead of
> "lpr ... ; rm ...".
> Check your lp for one of the following options:
> - remove printed file after printing or
> - make lpr return after spooling the file is completed or
> - use a temporary copy of files for printing.
> Hope this helps.
> Dirk Krause