Path: utzoo!attcan!uunet!seismo!ukma!jgary From: jgary@ms.uky.edu (James E. Gary) Newsgroups: comp.sys.amiga Subject: Re: DNET Hell PART III (the dreaded SUN3) AIIIIIIGHHH! Keywords: DNET, Jeremy, 43, Amiga, Hell, 43 Message-ID: Date: 20 Oct 90 01:46:22 GMT References: <14974@brahms.udel.edu> Organization: U of Ky, Math. Sciences, Lexington KY Lines: 39 jeremym@brahms.udel.edu (Jeremy A Moskowitz) writes: >out that the blasted binarys (the dnet files, etc) >only had the two protection bits set! I had to set >them from wr to wred before they would run. I think this is from zooing under Unix. You can't expect Unix to understand the Amiga's protection bits. Happens to me all the time. >whamo! the dnet thingie disapeared and FTERM came up >saying "trying to connect..." then after about 40 >seconds, the cli said "unable to connect..." Read the docs carefully. DNET originally required an 8-bit path. The latest rev allows (actually defaults to) 7 bits. The safe thing is to run it in 7 bit mode. I start dnet with DNET -P0 -Z0 -m -X -8 on the amiga side and 'dnet -m0' on the unix end. Remove the -m on the amiga and -m0 on unix to use 7 bit mode -- it should be safe. Another problem I had that sounds similar to your 'cannot connect' was a lack of PTY's on our system. We had a limited number and workstation users were really gobbling them up. Each fterm needs a pty. >I was heartbroken. I have spent probiably 24 hours >total on this project now, (ironically because >I wanted to save time in up/down/read/writing messages.) Hey, I tried three, count 'em three seperate times over the course of a year. I would work for a couple of days, get POed, delete everything and vow not to return. When I finally got things working, it seemed worth it. You won't want to go back. -- -- James Gary, BA,MS,SWM U. of Kentucky jgary@ms.uky.edu "Boy, giraffes are selfish" -- B. Fife