Xref: utzoo comp.sys.amiga:23798 comp.sys.ibm.pc:20092 comp.sys.mac:21334
Path: utzoo!attcan!uunet!husc6!bloom-beacon!mit-eddie!uw-beaver!uw-june!uw-entropy!bones!fetrow
From: fetrow@bones.stat.washington.edu (Dave Fetrow)
Newsgroups: comp.sys.amiga,comp.sys.ibm.pc,comp.sys.mac
Subject: Re: Multiple terminal emulations
Message-ID: <998@entropy.ms.washington.edu>
Date: 8 Oct 88 00:00:07 GMT
References: <55861UH2@PSUVM> <677@picuxa.UUCP>
Sender: news@entropy.ms.washington.edu
Reply-To: fetrow@bones.UUCP ()
Organization: UW Statistics, Seattle
Lines: 19

In article <677@picuxa.UUCP> tgr@picuxa.UUCP (Dr. Emilio Lizardo) writes:
>:
>:I regularly use three different mainframes in my work at the same time.
>:I currently have three terminals in my office so that I can be logged in
>:to all three.  I frequently need to capture info from one, and re-enter it
>:to a program on another.
>
 A cluster controller is not too bad an idea if a lot of folks have this same
problem but Falcon makes a nifty little windowing text terminal that connects
by 3 async ports. It does vt100, etc.

 Of course the "right" solution is a good PC (not necessarily MS-DOS) with 3
ports or (better still) a good network.


BITNET:   dfetrow@uwarita                            -- david d. fetrow --
UUCP:     uw-beaver!entropy!fetrow 
INTERNET: fetrow@bones.biostat.washington.edu
(cond ((lovep you (quote LISP)) (honk)) (t nil))