Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!well!ewhac
From: ewhac@well.UUCP (Leo L. Schwab)
Newsgroups: comp.sys.amiga
Subject: Re: Multiple Serial Ports (Re: vt100 v2.9)
Summary: I think you do it like this...
Message-ID: <10095@well.UUCP>
Date: 23 Dec 88 07:39:59 GMT
References: <8812150227.AA09671@postgres.Berkeley.EDU> <14049@oberon.USC.EDU> <3102@sugar.uu.net> <14097@oberon.USC.EDU>
Reply-To: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Organization: (-: ACME Flamethrowers.  Mark Ethan Smith, CEO. :-)
Lines: 24
Quote: "We are building a force of extraordinary magnitude."  -- Fistful of Yen

[ 3M TA3 ]

	Well, I just got through catching up with a 350-message backlog in
this group.  Try not to talk so much when I leave on a weekend vacation. :-)

	There has been discussion about how termulators should access the
exec-level device drivers.  ATalk's solution is to put a DEVICE ToolType in
ATalk's icon.

	If I remember correctly from the 1988 DevCon notes, the correct way
to go about supporting multiple serial ports is to go through DOS.  (Wait!
It's not what you think!)  By walking down arcane lists in the DOS, you can
discover the name of the exec device that is associated with a DOS handler.
It is in this manner that you're supposed to get the device name and unit
number for passing to OpenDevice().

	Checking the notes, I find this doesn't work for SER:, PAR:, or
PRT:.  Oh well.  It's worth reading up on, anyway.

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Leo L. Schwab -- The Guy in The Cape	INET: well!ewhac@ucbvax.Berkeley.EDU
 \_ -_		Recumbent Bikes:	UUCP: pacbell > !{well,unicom}!ewhac
O----^o	      The Only Way To Fly.	      hplabs / (pronounced "AE-wack")
"Work FOR?  I don't work FOR anybody!  I'm just having fun."  -- The Doctor