Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!agate!tornado.Berkeley.EDU!vincelee
From: vincelee@tornado.Berkeley.EDU (Vincent H. Lee)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: PD I/O Board Problems
Message-ID: <1991Mar20.055729.15370@agate.berkeley.edu>
Date: 20 Mar 91 05:57:29 GMT
References: <1991Mar6.112220.20054@agate.berkeley.edu> <309@documail.UUCP>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: ucb
Lines: 19

In article <309@documail.UUCP> rich@documail.UUCP (Rich McCallister) writes:
>In article <1991Mar6.112220.20054@agate.berkeley.edu>, vincelee@tornado.Berkeley.EDU (Vincent H. Lee) writes:
>     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).

Well, I've actually successfully recompiled parnet.device to work with
the ioboard, if I hook up the first three pins of parallel port B to
complete the port.

Unfortunately, this is only in 68000 mode.

-vince
.