Xref: utzoo comp.protocols.tcp-ip:10168 comp.dcom.lans:4299 comp.protocols.tcp-ip.ibmpc:2362
Path: utzoo!attcan!uunet!munnari.oz.au!uhccux!ames!amdahl!rtech!wrs!hwajin
From: hwajin@ganges.wrs.com (Hwa Jin Bae)
Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans,comp.protocols.tcp-ip.ibmpc
Subject: Re: tcp/ip for 386 UNIX
Message-ID: <HWAJIN.90Feb7104552@ganges.wrs.com>
Date: 7 Feb 90 18:45:52 GMT
References: <5645@ncrcae.Columbia.NCR.COM> <1990Feb2.154728.17877@ico.isc.com>
	<825@unix386.Convergent.COM> <ADNAN.90Feb6170824@sgtech.UUCP>
Sender: news@wrs.wrs.com
Followup-To: comp.protocols.tcp-ip
Organization: Wind River Systems, Emeryville, CA
Lines: 11
In-reply-to: adnan@sgtech.UUCP's message of 6 Feb 90 17:08:24 GMT

In article <ADNAN.90Feb6170824@sgtech.UUCP> adnan@sgtech.UUCP (Adnan Yaqub) writes:
   For one, in 3.0.  I have a manual in front of which says: "AT&T
   Enhanced TCP/IP WIN/386 Release 3.0" which talks about "Wollongong
   Socket Compatibility Library Routines".

The Wollongong stuff is based on the LAI TCP/IP stuff.  I know cause I've
looked at the sources.  The V.4 will have LAI TCP/IP stuff too.  Trust me.

--
Hwa Jin Bae, Wind River Systems, 1351 Ocean Avenue, Emeryville, CA 94606, USA
hwajin@wrs.com (uunet!wrs!hwajin)   "Omnibus ex nihil ducendis sufficit unum."