Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!gatech!mcnc!rti!sas!walker
From: walker@sas.UUCP (Doug Walker)
Newsgroups: comp.sys.amiga
Subject: Re: Help!
Keywords: dnet, dosen't work, huh?
Message-ID: <1202@sas.UUCP>
Date: 11 Sep 89 18:58:05 GMT
References: <6413@hubcap.clemson.edu>
Reply-To: walker@sas.UUCP (Doug Walker)
Organization: SAS Institute Inc, Cary NC
Lines: 22


Well, believe it or not, I still haven't gotten DNET 2.x, so
all my experience is with 1.x, but here it is anyway:

1. Make sure your dnet.servers file is in s:.  Make sure it
   has the correct pathnames for the servers.

2. Make sure both machines have the same baud rate set in
   preferences, or choose a baud rate on the DNET command
   line.

3. Make sure you run DNET on BOTH machines.  BOTH machines
   should have a dialer window up.  When both dialer windows
   are up, you should be able to type into one and see the
   results in the other.  If you can't, don't bother going
   on, it will not work.

I always run DNET -s, which prevents it from running FTERM
once it comes up.  I'm not interested in running FTERM, only
NET:.

--Doug