Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!crdgw1!vdsvax!einstein From: perley@einstein (Donald P Perley) Newsgroups: comp.sys.amiga Subject: Re: DNET problems... Message-ID: <10388@vdsvax.crd.ge.com> Date: 12 Dec 89 17:47:17 GMT References: <40950@lll-winken.LLNL.GOV> Sender: news@vdsvax.crd.ge.com Reply-To: perley@einstein (Donald P Perley) Organization: GE Corp. R & D, Schenectady, NY 12345 Lines: 43 In-reply-to: jac@muslix.llnl.gov (James Crotinger) In article <40950@lll-winken.LLNL.GOV>, jac@muslix (James Crotinger) writes: > I recently installed the newest version of dnet (2.10 with fixes). >When I connect to my Sun at work from home, things seem to work fine. >I use: > > dnet -X -8 -b2400 -P0 -Z0 > What I want to do, then, is leave that running so I can access the >stuff at home from my Sun at work. This used to work fine, but now >when I type "dsoc" at work it responds "DOpen: No such file or >directory". Now dsoc works fine when I type it in the fterm window >that is up on my Amiga I just hate "me too" articles, but I will say it: ME TOO! To further clarify: from an fterm window I can do any of the commands such as dprint, or opening an amiga cli. If I rsh to another machine, and rsh back, then try dprint, it says "unable to connect". The fterm windows have some extra environment variables set, like DNETHOST, which may have something to do with it. The ability to have a cli open from sun csh is neat, but loses some of its utility when its only accessable via an fterm window on the amiga console :-(. > Oh, one other thing. Perhaps this was just random noise, but I seem >to be getting a lot more checksum failure errors from dnet than I've ever >gotten before. Anyone else experience this? I have been getting this too. For me it always happens at the page prompt in "more", so it seems to be dependant on the data transmitted. When this happens, all the fterm windows are locked, and the only way out seems to be quitdnet, and restart. -don perley perley@trub.crd.ge.com