Path: utzoo!attcan!uunet!munnari.oz.au!uhccux!ames!think!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!m.cs.uiuc.edu!suna5!meyer
From: meyer@suna5.cs.uiuc.edu
Newsgroups: comp.windows.ms
Subject: Re: TCP under MS-Windows
Message-ID: <41900004@suna5>
Date: 16 Feb 90 17:41:26 GMT
References: <972@ssp18.idca.tds.philips.nl>
Lines: 22
Nf-ID: #R:ssp18.idca.tds.philips.nl:972:suna5:41900004:000:935
Nf-From: suna5.cs.uiuc.edu!meyer    Feb 15 16:38:00 1990


I'll bet that the problems all are having with running TCP librarys with 
MS Windows code is that the libraries are expecting the C standard
dynamic memory allocation functions, and are instead contending with the 
MS Windows memroy allocation system at link.  Or maybe it is a fight between
the two different systems for the memory that is available.

Even if the TCP libs are using the Windows memory functions correctly, one
must remember that Windows moves data segments around alot, and these libs
may be depending on stationary data segments.

Just a few random thoughts...

BTW: I, too, would LOVE to see a reasonably priced TCP / Sockets package
that works with windows.

_____
   Don Meyer		
   Internet:	   dlmeyer@uiuc.edu
   disclaimer:     UIUC policy can't agree with me, that might make sense.
   quote du jour: "If, indeed, there exists Artificial Intelligence,
		     then there must also exist Artificial Stupidity"