Xref: utzoo comp.protocols.tcp-ip.ibmpc:6277 comp.windows.ms.programmer:3367 comp.protocols.nfs:2547
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.windows.ms.programmer,comp.protocols.nfs
Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!lsuc!maccs!beame
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Subject: Re: Socket call in Window 3.0 program
Message-ID: <286A0E03.14277@maccs.dcss.mcmaster.ca>
Organization: McMaster University, Hamilton, Ontario, Canada
References: <1995@nixsin.UUCP> <43724@cup.portal.com>
Date: Thu, 27 Jun 91 16:10:42 GMT

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

	There really is no nead to wait as many TCP/IP vendors have
socket access under Windows 3.0 as DLLs or in other fashions. Here is a
small list of the products that I beleive have such an interface:


	Novell LAN WorkPlace for DOS
	Beame & Whiteside BW-TCP and BW-NFS
	Wollongong 
	FTP software (??? possibly in beta?)

- Carl Beame
Beame & Whiteside Software Ltd.