home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.datacomm
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!wupost!eclnews!cec2!amc1
- From: amc1@cec2.wustl.edu (Adam M. Costello)
- Subject: Re: DNet & niftyterm (Re: Why can't I find one decent term program?)
- Message-ID: <1992Sep9.150234.25675@wuecl.wustl.edu>
- Sender: usenet@wuecl.wustl.edu (Usenet Administrator)
- Nntp-Posting-Host: cec2
- Organization: Washington University, St. Louis MO
- References: <1992Sep8.024138.28616@wuecl.wustl.edu> <1992Sep8.081418.1539@wuecl.wustl.edu> <UefHWme00guKF4y1Rn@andrew.cmu.edu>
- Date: Wed, 9 Sep 1992 15:02:34 GMT
- Lines: 14
-
- In article <UefHWme00guKF4y1Rn@andrew.cmu.edu> Todd Andrew Williamson <tw0i+@andrew.cmu.edu> writes:
- >
- > The problem is that, while FTERM opens its window and does
- >all of its setup before it tries to connect, niftyterm tries to connect
- >first. So DNET isn't ready by the time niftyterm gets started up.
- >Since it takes longer for FTERM to start up (opening windows and
- >such...), it doesn't have this problem.
- >
- >The easiest solution to this is just to start up a niftyterm by hand.
-
- Another I found is to write a short script called delayednifty which
- does a wait 3 and then calls niftyterm. dnet -sdelayednifty then works.
-
- AMC
-