Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!news.cs.indiana.edu!maytag!watdragon!trillium!rpbozac
From: rpbozac@trillium.uwaterloo.ca (Roberto Bozac)
Newsgroups: comp.sys.amiga.tech
Subject: Re: DNet and remote login (dumb console window)
Message-ID: <1990Nov30.145012.15595@watdragon.waterloo.edu>
Date: 30 Nov 90 14:50:12 GMT
References: <1229@tau.sm.luth.se> <dillon.7364@overload.Berkeley.CA.US>
Sender: daemon@watdragon.waterloo.edu (Owner of Many System Processes)
Organization: University of Waterloo
Lines: 17

In article <dillon.7364@overload.Berkeley.CA.US> dillon@overload.Berkeley.CA.US (Matthew Dillon) writes:
>In article <1229@tau.sm.luth.se> d88-mbe@sm.luth.se (Michael Bergman) writes:
>>With this, my DNet finally works flawlessly. Thanks again, Matt (but you should
>>have written proper docs!!)
>>
>>Mike
>
>    Well, nobody's perfect.  Glad you found the solution to the problem
>    though!
>
I have discovered one other little thing that people should make sure
to check if they are having problems with DNet.  Despite my best efforts
I was having a _heck_ of a hard time getting dnet running on my computer
because stty was not set quite right.  Make sure that something like
stty intr ^C   or stty dec    apppears in your .cshrc.  I guess the
default intr on my computer causes Dnet alot of grief.  Other than
that the program is most excellent, thanks again, Matt!!