Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!rice!uw-beaver!ubc-cs!alberta!dvinci!news
From: aries@dvinci.UUCP (Aries Project)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Problems with serial device in shared mode
Message-ID: <1989Oct25.170153.15902@dvinci.usask.ca>
Date: 25 Oct 89 17:01:53 GMT
References: <8910240641.AA22293@postgres.Berkeley.EDU>
Sender: news@dvinci.usask.ca
Organization: University of Saskatchewan
Lines: 17

From article <8910240641.AA22293@postgres.Berkeley.EDU>, by dillon@POSTGRES.BERKELEY.EDU (Matt Dillon):
> 
> 	I do this all the time (have one program hold the serial device
>     open whilst I execute another).  Are you sure you are using the 
>     1.3 serial.device ???
> 
> 	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 !!
> 
> 	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.
> 
> 					-Matt