Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rochester!becker
From: becker@rochester.arpa (Tim Becker)
Newsgroups: comp.mail.uucp,comp.unix.questions
Subject: Re: UUCP thru Annex box
Message-ID: <732@sol.ARPA>
Date: Thu, 23-Jul-87 09:55:36 EDT
Article-I.D.: sol.732
Posted: Thu Jul 23 09:55:36 1987
Date-Received: Sat, 25-Jul-87 06:38:21 EDT
References: <202@spdcc.COM> <706@sol.ARPA> <700@umnd-cs.D.UMN.EDU>
Reply-To: becker@rochester.UUCP (Tim Becker)
Organization: U of Rochester, CS Dept, Rochester, NY
Lines: 19
Xref: mnetor comp.mail.uucp:717 comp.unix.questions:3309

In article <700@umnd-cs.D.UMN.EDU> rhealey@ub.UUCP (Rob Healey) writes:
>	Do you mean have the annex port act like a tty port from the 
>	Encore's point of view. Here in Duluth we set up our Max to
>	communicate to 2 Lazerwriters by having the Max control them
>	as tty's. i.e. ttyh1 would be printer #1 and ttyh2 would be
>	printer #2. You treat ttyh1 and ttyh2 just the same as you
>	treat physically wired tty's on other systems. I didn't
>	do this myself but I can refer anyone to the person who did.

Sounds like you have a computer made by Encore (not just the Annex).
They have a device driver built into their OS (UMAX) that hides the
setting up and tearing down of the connection to the Annex.  I have
4.3bsd Unix, not UMAX.

Would be handy if Encore would give away the code to do this...

Tim Becker.
..!seismo!rochester!becker
becker@cs.rochester.edu