Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!bryan
From: bryan@cs.utexas.edu (Bryan Bayerdorffer @ Wit's End)
Newsgroups: comp.sys.amiga
Subject: Re: UW
Message-ID: <268@mothra.cs.utexas.edu>
Date: 24 Feb 89 06:43:51 GMT
References: <6106@super.ORG> <418a531c.1285f@maize.engin.umich.edu> <6591@phoenix.Princeton.EDU> <6354@super.ORG>
Reply-To: bryan@cs.utexas.edu
Organization: Spam Detection & Removal Squad, Austin, TX
Lines: 48
Spam-Content: Negligible

In article <6354@super.ORG> rminnich@brainiac.UUCP (Ronald G Minnich) writes:
=-gee, i can't believe this. all these people who can't get dnet running. 
=-i have run it on several versions of ultra-icks, sunos 3.x and 4.0 and
=-4.02, 4.[2,3] bsd, and who knows what all. What the !@#$ is going 
=-on? ALl i ever do to get it to go is 'make'. You folks all running 
=-old dead code, or what?

	Well, let me just add to the confusion by relating my experiences.
I installed the first release of DNet on a VAX 11/780, BSD 4.3, as well as an
NFSed group of Sun 3/50s, all of which are accessed via a Bridge (NEVER buy one
of these!) communications server that is connected to all the machines by
Ethernet.  Connecting directly to the VAX, DNet exhibited the 'bouncing packet'
disease, though only after a few data packets (typed characters) had been
passed successfully.  The behavior was regular, depending on the characters.  I
suspected that something was twiddling the 8th bit as parity.  When connecting
to the VAX by first logging in on a Sun, and then rloginning (?!) to the VAX,
everything was peachy.  Furthermore, everything worked as advertised on the
Suns.  Since I do most of my work on the Suns, I just left it at that.  I never
installed the newest DNet, since, by the time it came along, I had hacked up
FTerm and DNet on the Amiga end so much, I didn't have time to repeat the
effort.
	Recently I tried installing the DNet UNIX end on our new Sun 4, SunOS
4.0, as well as on a Sequent Balance, Dynix 3.0.  Both have Bouncing Packet
Syndrome (BPS, get it?  Oh well, sorry...), though it's worse than the VAX
was--the initial FTerm manages to connect, but that's it.  My hopes weren't
high for the Sequent, but I was surprised that it blew up on the Sun 4.  I
haven't tried all the possible rlogin combinations, but I suspect that the
Bridge is mostly to blame, since it causes us so many other problems.  I might
put more effort into it when the next official DNet release comes down the
pipe, since I'm interested enough in the IPC stuff that Matt has supposedly
added to replace my current version.
	By the way, I believe I was the first person to point out to Matt that
DNet should actually be called DLink, and that DNET is the name of an optical
network design that belongs to TRW (not to mention some obscure Connection
Machine software), and he didn't even credit me in his Amiga Transactor
article.  Boy am I pissed!! :-) :-)

=-I will say uw was nice, dnet is much, much better. worth the effort.

	UW was a nice idea, poorly implemented.  Just like the Mac.  DNet is to
UW as Amiga is to Macintosh.
 ______________________________________________________________________________ 
/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/
|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|
_No dark sarcasm in the classroom|_____|_____|_____|_____|_____|_____|_____|___
|____Teachers leave the kids alone__|_____|_____|_____|_bryan@cs.utexas.edu___|
___|_____|_____|_____|_____|_____|_____|{vertebrae...}!cs.utexas.edu!bryan_|___
|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|