Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site oliveb.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!houxz!vax135!cornell!uw-beaver!tektronix!hplabs!oliveb!jerry
From: jerry@oliveb.UUCP (Jerry Aguirre)
Newsgroups: net.dcom,net.lan,net.wanted
Subject: Looking for improved ways to connect terminals to system
Message-ID: <116@oliveb.UUCP>
Date: Mon, 9-Jul-84 18:08:35 EDT
Article-I.D.: oliveb.116
Posted: Mon Jul  9 18:08:35 1984
Date-Received: Fri, 13-Jul-84 04:14:51 EDT
Organization: Olivetti ATC, Cupertino, Ca
Lines: 33

I am looking for an improved method for connecting terminals to our
host systems.  Our current configuration consists of 4 PDP-11/70s
(48 ports each), 1 Vax (48 ports) and >200 vt100s all connected by
a mass of individual cables in the walls and under the computer room
floor.

I am considering:
    1 - An ethernet cable connecting the terminals and systems.  I
	have read about a device that Interlan makes which allows
	10 async terminals to connect to the ethernet.
	  * Has anyone used this unit?
	  * Could one ethernet handle 200 terminals @9600 baud
	    (assuming ~50 in use)?
	  * How badly will the host ethernet/pseudo-tty processing load
	    the system (assuming ~10 in use per system)?
	  * Is the Interlan box difficult for a novice to use?

    2 - A system which piggy-backs the data on the phone line.  Each
	user has a modem under his phone which splits the data and
	voice.  This system eliminates cabling to each terminal but
	still requires a massive set going to the PBX.  Also we
	frequently have more terminals at a location than phone
	lines.

    3 - A conventional patch panel.  If we were to go with conventional
	cabling and a patch panel then cost would be the big issue as
	it would not be buying us much.

If you use or know of any system that might be useful then I would
appreciate hearing about it.

					    Jerry Aguirre
    {hplabs|fortune|ios|tolerant|allegra|tymix}!oliveb!jerry