Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!cica!iuvax!noose.ecn.purdue.edu!mentor.cc.purdue.edu!pur-ee!pur-phy!murphy From: murphy@pur-phy (William J. Murphy) Newsgroups: comp.sys.amiga Subject: Re: Dnet Keywords: Dnet, Telebit Trailblazer Message-ID: <3213@pur-phy> Date: 7 Mar 90 16:13:04 GMT References: <25358@swrinde.nde.swri.edu> Reply-To: murphy@newton.physics.purdue.edu.UUCP (William J. Murphy) Distribution: na Organization: Purdue Univ. Physics Dept., W. Lafayette, IN Lines: 52 In article <25358@swrinde.nde.swri.edu> kent@swrinde.nde.swri.edu (Kent D. Polk) writes: >I have been running every version of Dnet connected to a Sun 3 until >this last one. I can't get it to start up correctly. I have both a >hardwired connection (9600 at work), and a modem connection (at home). >I have been through several trial sessions from each end, trying every >option that I could think of to no avail. The best I can do is : > >1) Direct connect - startup Dnet on the Sun, start an Fterm, the fterm >fails to connect, the Dnet window pops up & quickly disappears, the >fterm attempts again, .... > >2) Modem - startup Dnet on the Sun, but the Amiga Dnet window never >disappears. > >Both connections are 8 bit, no parity. > >==================================================================== >Kent Polk - Southwest Research Institute - kent@swrinde.nde.swri.edu > "Anything worth asking for is worth over asking for" >==================================================================== Well, after what sound like similar problems, I finally succeeded in getting dnet 2.10 to run. Onthe Amiga end I start it with this part of a shell script. Path Comm:dnet/bin add assign dnet: Comm:dnet assign >NIL: DPIPE: exists if warn mount DPIPE: mount NULL: endif cd Comm:dnet/bin run dnet -X -P0 -b2400 -Z0 -m0 After I get logged into the Unix I then run dnet by typing dnet -m0 Of course dnet.servers and dnet.config are copied into s: and altered to reflect that the binaries are located in Comm:dnet/bin. Interestingly, you don't need dnet.servers and dnet.config to login and start dnet on the Unix. I was able to get the Fterm going but wasn't getting putfiles on the Unix to work. Then I thought about dnet.servers and copied it into s: and modified it. Now putfiles works. I run dnet over a modem with 8-bit connection and no parity. Hope this helps, -- Bill Murphy murphy@newton.physics.purdue.edu Enjoying my Amiga 2000, but holding out for a real computer: The Amiga 3000!!