Path: utzoo!news-server.csri.toronto.edu!rutgers!mcdchg!documail!rich
From: rich@documail.UUCP (Rich McCallister)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: PD I/O Board Problems
Summary: J. Lavin's IO Expansion
Message-ID: <309@documail.UUCP>
Date: 12 Mar 91 15:44:20 GMT
References: <1991Mar6.112220.20054@agate.berkeley.edu>
Organization: Bell & Howell DocuMail Division, Evanston, Ill.
Lines: 28

In article <1991Mar6.112220.20054@agate.berkeley.edu>, vincelee@tornado.Berkeley.EDU (Vincent H. Lee) writes:
> Well, I've just built Jeff Lavin's PD I/O board, and am, for now disappointed.
> 
> 1) The parallel port software configures incomplete parallel ports.  Let me
> explain...  Each 85C22 (btw, I think the Motorola 6821 may be equivalent, and
> readily available for about $3) provides 20 i/o pins.  Rather than configure
> a complete parallel port for each chip, the provided eightbit.device configures
> two 10-pin (no busy, pout, or sel) parallel ports per chip.
> 
> 4) Source.  The source code is in Macro68 assembly.  I've had a hell of a
> time converting this code to plain vanilla assembly.  
    Could you make the converted code available? This would save others (like
me) the trouble.
> 
> PS: Also, I've been trying to convert ParNet to work with the board.  Is the
> source to it available?  I've been working with a disassembled version.  I
> think I can do it, but a legit source would make it much easier.
     I've been wondering whether or not ParNet uses one or all of the "missing"
signal lines.  Granted, "paper out" has little meaning for a disk drive, but
the ParNet drivers could use it for something else.
     I'd been thinking of taking another approach to the same problem (that is,
of using ParNet and using PRT: with a parallel port).  Why not make the PRT:
use the eightbit.device? That way, your printer could go on par1: or par2:, and
ParNet could use par:.  I assume the printer.device uses the serial.device and
parallel.device; perhaps that can be changed (I haven't check it out yet).
     I have an HP IIP printer, currently on par1:.  I'll try dumping a
bit-mapped image to it, and see if it exhibits the same problem with graphics
that you've seen on the DeskJet.