Hi Will,
PK> Possibly......;-) The only catch I am aware of is that Windows and
PK> DOS  sessions generally only recognise serial ports identified  as
PK> COM1 - COM4, nothing else. Generally, OS/2 apps can  access a COM
PK> port of almost any name you like (share a COM  port as CHARLIE and
PK> connect to it using an OS/2 comms app,  it works fine.....;-)). 
PK> 
PK> I can report that I have connected and used an OS/2 COM port with
PK> a modem on  it (actually COM2, shared as COM4) from a OS/2 Windows 
PK> session (MS Mail Remote) using NETBIOS over TCP/IP on an 
PK> international connection. It was pretty slow, but it sure  did work.
PK> Left a few MS people with dropped jaws and  blinking hard......;-)
 WH> OK, don't keep me in suspense: HOW?
How what?...;-) The only caution I can think of is to ensure that when you 
CONNECT to a shared COM port, you make sure the COM port number you assigned 
it to is within the range COM1 - COM4.
 WH> I've tried about everything I can
 WH> think of - except using a name like COM4 for the resource. 
The SHARE name of the resource does not matter, it is only used so that OS/2 
can establish a connection betweem the 2 machines. You just have to ensure 
that the connecting machine is creating the COM port within the COM1-4 range. 
Of course this also assumes that the NAME (COMx) you use on the connecting 
machine DOES NOT EXIST already. 
The only other catch I am aware of is that for a WINOS/2 session to "SEE" any 
connections, you MUST establish the connection under OS/2 BEFORE you open the 
DOS or WINOS/2 session. If you establish a connection AFTER opening the 
WINOS/2 session, then you will not see the new connection within the WINOS/2 
session until that session is ended and restarted. This applies to ANY type 
of sharing, file sharing, printer sharing, COM port sharing, etc...
I hope this helps..............pk.
--- Maximus/2 3.01
---------------