12-30-1997,Peter Knapper wrote to Will Honea:
PK> Hi Will,
PK> 
PK>  WH> I'm trying to share a com port across a Warp 4 Peer setup such that 

PK>  WH> WinOS2 app can access a modem via the network (I HATE stringing 
hone
PK>  WH> wires!).  The sharing works fine with OS/2 apps - they use the modem
PK>  WH> slick as can be - but I have yet to be able to get a DOS/WIN app to 
be
PK>  WH> able to use the port.  Am I missing something obvious or is this a 
lost
PK>  WH> cause?
PK> 
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......;-)
OK, don't keep me in suspense: HOW?  I've tried about everything I can
think of - except using a name like COM4 for the resource.  I also
tried a couple of DOS/WIN apps that are supposed to allow sharing under
NT, but no luck there either.  I'm not ready to climb into the attic to
string phone wires yet, but that may be coming.  Teenage daughters get
awfully cranky about their communications media! 
Will Honea
whonea@codenet.net
--- Maximus/2 2.02
---------------