I am pretty sure that you don't have to do anything
special for a "raw" device exported to a windows
machine: I'm using an EPSON STC 740 with the USB
interface to print from several Linux machines plus
a vmware Windows session and sometimes from a real
Windows machine. I'm however still using the
2.3.39 backport to 2.2.14, which just worked and with
all the problems reported on the list regarding
printing I never bothered to update.
I'm not using any filter that adds any init codes
for every print job. This is what the driver on your
Windows machine will do for you, and the same goes
for GhostScript or the Gimp print plugin. These
packages usually reset the printer before they do
anything else.
Now in Beat's case, the string that's listed is exactly
this init string because he's modifying the UPP file,
which lists all the commands the printer needs, so he's
basically modifying GhostScript.
If you can print with one of the standard GhostScript
drivers you don't have to do anything special. If you
want to queue print jobs from Windows machines on
the net you don't have to do anything special either.
.. and you certainly don't want to modify printer.c
by adding functions that are not part of the USB
driver portion. As I said before, these init strings
are what the applications or drivers will generate.
If an application is not doing this talk to the
author of the software and fix the problem at the
correct level.
Does this explain this init string issue a bit?
Karl Heinz
"Dunlap, Randy" <[EMAIL PROTECTED]> said:
> Manuel,
>
> Is your printer an Epson also (as Beat's is)?
>
>
> > My only problem now is that I also export this printer via
> > Samba to the
> > Windows machines on my network as a networked printer with a "raw"
> > interface. Does anyone know whether just prepending the
> > listed codes at the
> > beginning of each print job would work (ghostscript is doing
> > it at each
> > page, I don't know whether I can write a filter that would do
> > that with binary data being sent from Windows).
> >
> > If this is a one-time initialization string that only needs
> > to be sent each
> > time the printer is powered up, how difficult would it be to
> > put this in printer.c?
>
> Do all printers need this additional init string?
[ ... ]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
