IT> One point to note however is that the process that you are running
 IT> the RxAsync based script in should be a child of the process which
 IT> opened the com port so that it can inherit access to it. This is an
 IT> OS/2 restriction (I think this still holds in 2.x). Also the open
 IT> needs to be of an appropriate type, ie. OPEN_SHARE_DENYNONE so

A process that is inheriting a file handle does NOT require that the handle
have been opened with OPEN_SHARE_DENYNONE,  since it is not reopening the
file/port!!  This is the whole point of passing the hot handle.

The parent probably should have (and DEFINITELY should have for OS/2 comm
programs) opened the port in OPEN_SHARE_DENYREADWRITE mode.  This is
exactly what Maximus does (I wrote it).

 IT> that you are permitted to read and write to it. Unfortunately,
 IT> some things (nameley IBM's SLIP) open in OPEN_SHARE_DENYREADWRITE
 IT> which is down right ornery! If opened via RxAsyncOpen you'll get

Nope -- it's downright CORRECT.  You can't leave the door open for another
uninvited process/session to open a device that is inherently single-user, 
like a serial port.


--- Maximus/2 2.02p1