Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!ginosko!usc!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Problems with serial device in shared mode
Message-ID: <20779@usc.edu>
Date: 24 Oct 89 23:24:45 GMT
References: <8910240641.AA22293@postgres.Berkeley.EDU>
Sender: news@usc.edu
Reply-To: papa@pollux.usc.edu (Marco Papa)
Organization: Felsina Software, Los Angeles, CA
Lines: 25

In article <8910240641.AA22293@postgres.Berkeley.EDU> dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
|	There is a problem... many terminal programs and other programs
|    do not open the serial.device SERF_SHARED !! THIS IS WRONG!  You
|    programmers out there, ALWAYS OPEN SERIAL.DEVICE SERF_SHARED !!

I disagree. Terminal programs should give you the "option" of opening the
serial device in SHARED mode. A-Talk III allows you to do that by using
the SHARED keyword either on the CLI command line or in a Tooltype.

|	The other problem is that the serial.device will refuse to
|    do a SDCMD_SETPARAMS call while active requests are pending, so
|    if you do use something similar to what I've described above you
|    have to be sure that the first program doesn't have any active
|    requests when it executes the second program.

Quite true. The comm program must give you a 'menu' selection that
aborts all active requests and optionally saves the current serial
device status.  A-Talk III does that too.  Of course, none of these 
problems are present when using and XPR-based protocol library.

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