From owner-freebsd-hackers Tue May 2 16:48:26 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA20653 for hackers-outgoing; Tue, 2 May 1995 16:48:26 -0700 Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA20640 for ; Tue, 2 May 1995 16:48:22 -0700 Received: from [192.245.33.12] by gateway.cybernet.com (8.6.8/1.0A) id UAA14838; Tue, 2 May 1995 20:21:35 -0400 X-Sender: mtaylor@gateway.cybernet.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 2 May 1995 19:47:20 -0400 To: Joe Greco From: mtaylor@gateway.cybernet.com (Mark J. Taylor) Subject: Re: looking for IP over printer port driver users Cc: hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk >> On Thu, 27 Apr 1995, Poul-Henning Kamp wrote: >> >> > > Once I know the rewritten driver is happy, I'll be adding support >>for the >> > > Crynwr/Linux PLIP protocol format. >> > CooL! >> >> When you have that support going, I can test it for you. I have a linux >> box sitting right next to a freebsd box [both run EPP parallel ports] and >> move data really well with laplink [under DOS] normally. > >Does anybody have a clue how to manufacture the needed cable? I would like >to play with this, but do not want to spend money on a cable that I can >build from parts in stock.. > >... JG In DOS (6.0 or later): HELP INTERLNK At the end of the NOTES section, you'll see a wiring diagram labeled 'Pin Connections for a Parallel Cable'. This should be the same as the Interlink cable, because I've used the cable that I made from this spec with Interlink as well as Laplink. :) -Mark Taylor mtaylor@cybernet.com