ML>> does this mean that if one can get COM/IP working and FD
ML>> talking to it for telnet, that FD can exit and hand the
ML>> COM/IP port over to the native win32 version of mystic?

 JC> if com/ip is able to pass the socket handle on a command
 JC> like then yes, that would be possible.

COM/IP is a virtual modem /shim/... it doesn't pass anything other than
data... it sets up virtual com ports and modems that it handles... you just
take your normal DOS telecom apps and point them to the virtual com port
and they are telnetting away thinking that they are sending/receiving data
to/from a modem... the only problem they may have is "dialing"
domain names...

the idea would be that the win32 apps be able to see the virtual com port
and modem and take the handoff from FD...

ie: COM1 physical serial port with a mouse
    COM2 physical serial port with a real modem
    COM3 virtual serial port modem

configure FD task 1 to use COM2 for dialup connections.
configure FD task 2 to use COM3 for telnet connections.

the only thing that may be different between the two is the AT commands
used to talk to the modem before and after the connection...

 JC> i've personally never used com/ip though so i can't say for
 JC> sure if it allows that.

since its not a "server" per se, no, it can't...

)\/(ark