From: Gary Welles 

Please excuse my irrational exuberance over BSD Sockets.  A port
using DV/X's BSD Socket interface would allow it to share the
same network interface with DV/X.  Arachne's control over the
display hardware, would limit it's use, even in DV/X.

The following excerpt from a DV technote may explain why TCP/IP
connection may or may not always work from TASKMGR.

-- Gary Welles

| ...  As a general rule, loading non-DESQview specific network
| shells within a window is not recommended.  The reasons are that
| network shells are actually interrupt arbitrators, re-directors,
| and/or repeaters.  Depending on the shell configuration (and the
| application software) intended to run in the window, two primary
| factors must be considered.
|
| 1.   A packet may arrive for the workstation while this window
|      is not the current task.  The network must retry sending
|      the packet, causing network performance degradation (or the
|      network may timeout and drop the work-station).
|
| 2.   Only that window would be able to see the network.  Loading
|      the network shell in more than one window can also confuse
|      the network unless the shell has been specifically written
|      for this purpose.



--- Internet Rex 2.29