Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!cs.umn.edu!sialis!orbit!pnet51!chucks From: chucks@pnet51.orb.mn.org (Erik Funkenbusch) Newsgroups: comp.sys.amiga.programmer Subject: Re: Accessing BUSY, SEL, and POUT via "parallel.device"? Message-ID: <4660@orbit.cts.com> Date: 19 Apr 91 18:25:01 GMT Sender: news@orbit.cts.com Organization: People-Net [pnet51], Minneapolis, MN. Lines: 31 valentin@public.BTR.COM (Valentin Pepelea) writes: >In article >dillon@overload.Berkeley.CA.US (Matthew Dillon) writes: >> >> The parallel.device only handles a printer. To use the parall port in >> a bidirectional manner you must allocate the appropriate resources >> and access it manually. > >Actually, the parallel.device is bidirectional, depending on what you mean by >that. Just wire-up a NULL-parallel cable, where pins 1 and 10 are crossed and >pins 23 & 25 are cut. Only one computer may send data to the other at any >moment in time, so you have to establish a little protocol in which one >computer tells the other when it is about to be the sender, and how much data >it intends to send. actually, if you want you can set up 4 lines to be input and 4 for output and cut the bytes in half and send them. this way you could achieve a full duplex 4 bit connection. 4 times faster than the serial port. > >Valentin >-- >"An operating system without virtual memory Name: Valentin Pepelea > is an operating system without virtue." Phone: (408) 985-1700 > Usenet: mips!btr!valentin > - Ancient Inca Proverb Internet: valentin@btr.com s UUCP: {amdahl!tcnet, crash}!orbit!pnet51!chucks ARPA: crash!orbit!pnet51!chucks@nosc.mil INET: chucks@pnet51.orb.mn.org