Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!rutgers!mcnc!rti!sas!walker
From: walker@sas.UUCP (Doug Walker)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Parallel-Port network preliminary specs & demonstration code
Message-ID: <1224@sas.UUCP>
Date: 14 Sep 89 13:16:43 GMT
References: <8909082229.AA07771@postgres.Berkeley.EDU> <4535@amiga.UUCP>
Reply-To: walker@sas.UUCP (Doug Walker)
Organization: SAS Institute Inc, Cary NC
Lines: 22

In article <8909082229.AA07771@postgres.Berkeley.EDU> dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
>...to transfer files from one amiga to another via the parallel port...
>
Yay Matt!  I got NET: working with Matt's parallel port routines last night,
and it's FAST FAST FAST!  It is actually FASTER to do a dir opt a of df0:
over the network than locally on my 512k 1000!  I presume this is because you 
don't have to update the display.  It took 54 seconds locally on each of two
tries, and 48 and 50 seconds remotely.

The current problem is that eventually (after 15-20 minutes of heavy use) I
get a write error on the server side.  This is fatal since I didn't put any
retry capability in the first version.  Also, I can only run one direction
at a time since I always use channel 1, but I'll take care of that.

Matt, if you're listening, how do the channels work?  If I do a ParAddress(1),
then write, why do I need to send a '1' as the first parameter (which is what
parman does?)

Expect a new posting within a few days for the parallel version.  Only three
new files to the source code, plus Matt's parallel port stuff.

--Doug