Xref: utzoo comp.protocols.tcp-ip.ibmpc:6291 comp.windows.ms.programmer:3387 comp.protocols.nfs:2549
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ncar!unmvax!uokmax!occrsh!fang!att!cbnewsk!cbnewsj!apb
From: apb@cbnewsj.cb.att.com (Amrit Bains)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.windows.ms.programmer,comp.protocols.nfs
Subject: Re: Socket call in Window 3.0 program
Message-ID: <1991Jun28.025505.29432@cbnewsj.cb.att.com>
Date: 28 Jun 91 02:55:05 GMT
References: <1995@nixsin.UUCP> <43724@cup.portal.com>
Organization: AT&T Bell Laboratories
Lines: 20

In article <43724@cup.portal.com> netmanage@cup.portal.com (William - Dunn) writes:
>In response to the question on socket calls from Windows, it is my 
>impression that most of the current implementations are built for
>DOS and have problems interfacing to Windows.  Your solution is either
>to wait for the vendors to come out with a socket interface to Windows
>or to switch to a TCP/IP stack that is implemented as a Windows DLL.
>Obviously I prefer the second approach since NetManage has a full
>TCP/IP stack implemented as a Windows DLL with socket interface.
>I am not going to go into a commercial here so you can contact me
>at netmanage@cup.portal.com or call (408)257-6404.
>
>Boris Yanovsky


NOVELL offers LAN WORKPLACE for DOS and WINDOWS which has a DLL for TCP/IP
with a sockets interface.  It also has sockets libraries for DOS.
We are using it and it seems stable enough for comercial pupposes.

Amrit Bains
abains@attunix.att.com