Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!umd5!terminus.umd.edu!dzoey
From: dzoey@terminus.umd.edu (Joe Herman)
Newsgroups: comp.windows.ms.programmer
Subject: Re: using socket library under Windows3
Message-ID: <7894@umd5.umd.edu>
Date: 24 Jan 91 16:10:07 GMT
References: <1991Jan22.060324.326@technix.oz.au>
Sender: news@umd5.umd.edu
Organization: University of Maryland DOSIP-CSC
Lines: 26

In article <1991Jan22.060324.326@technix.oz.au> enno@technix.oz.au (Enno Davids) writes:
>We're involved in porting an application to windows 3.0 that
>requires a BSD sockets library We have all of the commercial
>sockets libraries (ie. Wollongong, HP, Locus, PC/TCP..) and
>none of them will link with our application to produce a
>valid windows program  (because they are all DOS libraries, the
>function preambles  are different, and they use interupts).

Right.  All the various socket libraries are meant for DOS.  I'm
sure that many of the commercial organizations are working on libraries
for win3 (Wollongong & FTP Inc. have stated this publicaly.
I think they're supposed to be out 1Q91.)  WINQVT/NET uses the NCSA
TCP as a base for their telnet.  This doesn't use a socket library though.
It's possible to talk to a packet driver from windows.  I suppose you
could do what WINQVT/NET did and port NCSA.

You could always see if one of the commercial companies is looking for
beta testers....

				Joe Herman
				U. of Maryland


dzoey@terminus.umd.edu
-- 
"Everything is wonderful until you know something about it."