Salutations,

I have just got back after working away from home, so if I'm repeating
anything that has already been said, apologies.

We use an old Epson Stylus Color II as a line printer on lpa0, and we use gs
for printing postscript files to it as follows:

1. From the command line:
    gs -sDevice=stcolor -dNOPAUSE -dBATCH -sOutputFile=\|lp filetoprint.ps

2. From Ghostview:
    Set the default print command to be the same as above, but without the
filename.
    Alternatively type it in to the dialog box at print time if you normally
have gv configured for a different printer.

This seems to work perfectly, giving colour, excellent text and no drift. For
printing text files, we just send them directly, so I can't comment on a2ps.

Typing 'gs -h' shows all the printers that are supported(quite a lot really),
but the names are a bit cryptic(just model numbers for most). This is with
ghostscript 5.50, which supports more printers than 5.10. Presumably 5.83 will
support even more!

regards,
Dave

Richard Rauch wrote:

> On Fri, 21 May 1999, Berndt Josef Wulf wrote:
>
> >Richard Rauch wrote
> >[...]
> >> a) Can someone else confirm the ``drift'' problem with another
> >> configuration?  Or suggest a fix?
> >
> >By memory, I think there was a dip-switch setting for default
> >page-size Letter/A4
>
> I checked; I already had it set to Letter for default.  Since the pages
> were effectively printing a shade ``large'', I decided to try a smaller
> page-size (Quarto).  This made the output a little smaller, but had
> exactly the same ``drift'':
>
> On a 7-logical-page test file, at 2 logical-pages-per-physical, there is
> slight, but visible drift between the 1st page and the 3rd (physical).  On
> the last physical page, the first half is blank (because there are an odd
> number of logical pages), and the drift is _significantly_ more
> pronounced.
>
> Any further ideas?  Since GhostScript works well in general with my
> printer, I assume that gs isn't at fault---but maybe if I lie to gs
> somewhere, a2ps|gs will work.
>
> If I find any answers, I'll post.  I was hoping that someone had run into
> this problem before and knew a hack (or proper fix).
>
>   "I probably don't know what I'm talking about." --rauch@eecs.ukans.edu




--
e-mail: dave@largesalad.co.uk