Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!amdcad!sun!pitstop!sundc!seismo!uunet!nuchat!peter
From: peter@nuchat.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: Multiple serial ports (was Re: Need help with signals)
Message-ID: <530@nuchat.UUCP>
Date: 12 Jan 88 05:14:07 GMT
References: <2245@cup.portal.com> <22374@ucbvax.BERKELEY.EDU> <202@imagine.PAWL.RPI.EDU>
Organization: Public Access - Houston, Tx
Lines: 25

In article <202@imagine.PAWL.RPI.EDU>, jesup@pawl21.pawl.rpi.edu (Randell E. Jesup) writes:
> In article <1359@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
> >#include <libraries/dosextens.h>
> >	fh = Open("SER:", ACCESS_WRITE);
> >	FH = (struct FileHandle *)(fh<<2);

> >Hmmm. The documentation is a mite skimpy on where to go from there. It seems
> >like it should be possible to go with it... send serial port messages to the
> >fh_Port in the structure. But what's the fh_Type feild?

> Unfortunately, AmigaDos handlers are not designed to be a means of access to
> the underlying devices.  In fact there may not BE an underlying device
> (ex: Ram:), or there may be different ones at different times (prt:), or
> there may be multiple devices at the same time (none presently).

So how do people get hold of their own console.device from Input()?

Also... even if the existing handler isn't guaranteed to work for ALL
devices, is there some way of making it work for the serial.device and
to get people writing new devices to work in concert.

The idea of having so many disparate name spaces on the machine is beginning
to gibe me the heebie-jeebies. How hard would it have been to make all the
devices accessible through AmigaDOS? That way you could ALWAYS map ports
around just by using Assign.