Path: utzoo!utgpu!watmath!uunet!amdahl!apple!bloom-beacon!mit-eddie!andante!ulysses!att!mtunb!jcm
From: jcm@mtunb.ATT.COM (was-John McMillan)
Newsgroups: unix-pc.general
Subject: Re: UNIX-PX Printer Setup
Keywords: UNIX-PC Printer 7300 3B1
Message-ID: <1435@mtunb.ATT.COM>
Date: 13 Mar 89 16:33:39 GMT
References: <932@mtfmi.att.com> <719@kosman.UUCP>
Reply-To: jcm@mtunb.UUCP (was-John McMillan)
Organization: AT&T ISL Middletown NJ USA
Lines: 22

In article <719@kosman.UUCP> kevin@kosman.UUCP (Root) writes:
>...
>Yep, AT&T did it to you again.  They did it to me, too.  Screen printing
      ^^^^^^^^^^^^^^^^^^              ^^^^^^^^^^^^  AT&T targets precisely ;-)
>works only with AT&T printers, maybe on full compatibles.  This is not too
>surprising because it is built into the kernel and they didn't want to
>clutter that with lots of odd options for different bit-addressing styles
>that different printers have.

(It's always fun reading paranoid broadcasts!-)  AT&T -- according to
the report I heard from within AT&T -- TRIED to include the OKIDATA-92
printer, but supporting this printer's "features" collided with deadlines.

The KERNEL only sends the bits out (ref: 'wd' ioctl): there is a
screendump program that is responible for translating it to the printer
-- and therein's your problem -- at least the software one!

You can generate image FILES -- since I do NOT do this, I'll defer to
others to explain how -- and drive the printer from your own
bitmap-to-printer converter.

jcm