home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.3b1:3071 comp.periphs.printers:2362
- Newsgroups: comp.sys.3b1,comp.periphs.printers
- Path: sparky!uunet!cs.utexas.edu!torn!cunews!nrcnet0!bnrgate!bwdls61!bwdlh118!clewis
- From: clewis@ferret.ocunix.on.ca (Chris Lewis)
- Subject: Transparent communications thru parallel port/HP LJIIP+
- Message-ID: <1992Aug13.142629.8120@bwdls61.bnr.ca>
- Originator: clewis@bwdlh118
- Sender: usenet@bwdls61.bnr.ca (Use Net)
- Nntp-Posting-Host: bwdlh118
- Organization: Myself
- Date: Thu, 13 Aug 1992 14:26:29 GMT
- Lines: 44
-
- I just got a HP LJ IIP plus (so now I can test psroff
- before issuing patches ;-) which I've connected to my
- 3b1. The IIP+ has only a parallel port (please, no
- flames about not paying attention when I "acquired"
- this printer - I didn't have a choice as to model number).
-
- Normal text printing works just fine, but as I suspected,
- /dev/lp does apply certain "termio-ish" transformations to
- data going to the parallel port. Which is a real no-no
- when you're trying to download fonts and rasters etc.
-
- <sys/lprio.h> is rather suggestive that there's ways of
- controlling this behaviour via ioctls, but I have no
- documentation, and I can't figure out some of the operations.
- Eg: LP[GS]ET versus LP[GS]ETV or what the "ind" field is for.
-
- a ioctl(/dev/fd, LPGET, &lpriostruct) shows "ind" as zero,
- "rows" as 66, and "cols" as 1024. Chances are I'd get partway
- by LPSET'ing rows and cols to 0, but that won't necessarily
- disable "\n" -> "\n\r" transformations etc.
-
- Does anybody have documentation, or program fragments that
- explain how this works? Or, does the lp driver support
- other minor device numbers for suppressed transforms?
-
- I'd rather not have to binary zap the driver...
-
- While I could obtain a serial to parallel port converter,
- frankly I'd rather keep it on the parallel port for
- reasons of speed - I will probably be doing extensive
- raster graphics, and font downloading isn't exactly
- cheap in terms of communications time. Besides, I think
- my one remaining free serial port got fried by a line transient.
-
- Once I get this working, I'll get groff, and finish
- off all of the issues regarding lack of support for PIC
- on LJs less than IIIs, implying that hp2pbm will give full
- ditroff support on *any* PBM-supported device.
-
- My second question: I'll probably be wanting to upgrade the
- LJIIP+ in the future. More memory, and/or PostScript cartridge.
- What alternatives to HP are there? Particularly in memory.
-
- Thanks
-