Hello Peter,
Replying to a message of Peter Knapper to Alec Herrmann:
 AH>> The obvious thing to know is that COM ports that are 
 AH>> shared on an OS/2 box can not be used by DOS or Windows 
 AH>> or Win95 boxes as modem ports.
 PK> Sorry, I have to disagree. Provided the COM port number you are using
 PK> for the "emulated" COM port is within the DOS/Windows application
 PK> range (usually COM1 - COM4), and OS/2 is virtualising that COM port
 PK> for you, then the DOS or Windows application has no idea it does not
 PK> really exist and uses it fine. 
I now realize my mistake - I did not pay attention to one detail in the 
message I responded to - that he was using a 'WinOS/2' session and not a 
Windows box.
I was referring to a DOS/Win3x/Win95/WinNT workstation on a network along 
with an OS/2 server box, and the OS/2 server box has shared COM ports.  The 
DOS/etc box can not use the shared COM port located on the OS/2 server box as 
a modem port while another OS/2 box on the network can do so.
 PK> I use an IBM THinkpad with Warp 3 Connect and that has 1 REAL port -
 PK> COM1. It also has COM2 which is the MWave audio device and that also
 PK> provides a modem. MS Mail Remote on that PC can use either COM port.
 PK> Not only that but it can also use COM4 which is a LAN connection to
 PK> another Warp 3 Connect system that has a modem on COM2 and shares it
 PK> as COM3. It all works fine for me......pk.
Yes, this is in a WinOS/2 session on an OS/2 box.  Sorry about my oversight 
on that item.
Regards, Alec
--- FleetStreet 1.12 NR
---------------