Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!bloom-beacon!oberon!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga
Subject: Re: vt100 v2.9
Message-ID: <14049@oberon.USC.EDU>
Date: 15 Dec 88 04:13:19 GMT
References: <8812150227.AA09671@postgres.Berkeley.EDU>
Sender: news@oberon.USC.EDU
Reply-To: papa@pollux.usc.edu (Marco Papa)
Organization: Felsina Software, Los Angeles, CA
Lines: 39

In article <8812150227.AA09671@postgres.Berkeley.EDU> dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
|Dave Kinzer <noao!nud!fbog!dbk| writes:
||   And while you are in there fooling around with the code, if it doesn't
||already, add support for a serial device with a name other than 'SER:'.
||One of these days someone is going to come out with a board, then everyone
||will become *really* mad.  This goes for any other software that talks
||to that port also.
|
|	Mmm... terminal programs general do not use the DOS device handler
|(i.e. SER:) but use the device level "serial.device".  One assumes all you
|would need are options to be able to set the device name and unit number.

Version 1.0e of A-Talk III, which I shipped to OXXI last week for duplication,
supports "multiple serial ports", through different UNIT numbers.  As Matt
explains the software does:

OpenDevice(serial.device, unit);

where unit can be 0, 1,2,3, etc...

0 = "standard" serial device

1, 2, 3 = additional ports. 

The UNIT number is set in the TOOLTYPES Info as:

UNIT=x

x = number.

It is currently an "undocumented" feature [though now it's no more :=)].

So harware guys, when are we going to get multiple serial devices?
The software is ready.

-- Marco Papa 'Doc'
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
uucp:...!pollux!papa       BIX:papa       ARPAnet:pollux!papa@oberon.usc.edu
 "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=