MS couldn't even write a decent TCP/IP stack.

Post #4,285 by Brandioch 8/8/01 5:15:19 PM Reply	MS couldn't even write a decent TCP/IP stack. They tried, and they ended up taking the BSD one. While it might be a great idea (for MS), I haven't seen anything indicating that they are technically capable of designing/implementing such. This has about as much likelyhood as his previous article about MS leaving the country. What's up with him lately?
Post #4,313 by static 8/8/01 9:28:59 PM Reply	Actually, I think he has a different point. I suspect Cringely's point is that Microsoft want to do this - never mind how capable they actually are of it. It's very ambitious, though. Wade. "All around me are nothing but fakes Come with me on the biggest fake of all!"
Post #5,304 by acagle 8/15/01 3:23:40 PM Reply	Re: MS couldn't even write a decent TCP/IP stack. Could you point me to the documentation on that? I've seen it refernced a couple of places. Petreley also mentioned some other stuff that MS used open source for but won't admit to.
Post #5,330 by tjsinclair 8/15/01 6:23:14 PM Reply	Re: MS couldn't even write a decent TCP/IP stack. I think if you run 'strings' (or some other tool that can look at ASCII text embedded in a binary) on the TCP/IP binaries (like WINSOCK) you should get the Berkeley copyright notice. I haven't haven't done this, so feel free to correct me on this.
Post #5,338 by a6l6e6x 8/15/01 8:00:52 PM Reply	Windows ME winsock.dll copyright says it's Microsoft's. Description: BSD Socket API for Windows. Copyright: Copyright (C) Microsoft Corp. 1993-1997 File version: 4.90.0.3000 I just checked. YMMV. Alex Only two things are certain: the universe and human stupidity; and I'm not certain about the universe. -- Albert Einstein (1879-1955)
Post #5,371 by tjsinclair 8/16/01 12:10:05 AM Reply	So why does it say BSD if it's Microsoft's?
Post #5,392 by kmself 8/16/01 6:30:45 AM Reply	API, not implementation I'm not speaking for what's in the software. But an API is a schema, an implementation is a work. It's possible to code up an alternative implementation of an API. Mind, if there's BSD code that Microsoft's not acknowledging, they might have some interesting times with UC's IP rights management folk. -- Karsten M. Self [link\|mailto:kmself@ix.netcom.com\|kmself@ix.netcom.com] What part of "gestalt" don't you understand?
Post #5,444 by a6l6e6x 8/16/01 2:33:54 PM Reply	What he said! :) I agree. Alex Only two things are certain: the universe and human stupidity; and I'm not certain about the universe. -- Albert Einstein (1879-1955)
Post #5,470 by wharris2 8/16/01 4:59:52 PM Reply	Tried a google search The best reference I could come up with was a reference to someone who thought he'd seen a Berkley reference in the license to NT 3.51. That's not very strong evidence unless I can actually run across a copy of NT 3.51 and see the license myself. The winsock.h headers do include the following: * This file includes parts which are Copyright (c) 1982-1986 Regents * of the University of California. All rights reserved. The * Berkeley Software License Agreement specifies the terms and * conditions for redistribution. but as noted, this doesn't necessarily have anything to do with the actual TCP/IP stack implementation. French Zombies are zapping me with lasers!
Post #5,537 by Andrew Grygus 8/16/01 11:32:43 PM Reply	ID number was a point. TCP/IP stacks report an ID number which is different for each vendor - except Microsoft's TCP/IP reportes the same ID as Berkeley. [link\|http://www.aaxnet.com\|AAx]
Post #5,554 by wharris2 8/17/01 12:35:16 AM Reply	Re: ID number was a point. But that doesn't really prove anything. Microsoft might have decided, "OK, this is the standard ID, we'll report it". Again, I wasn't able to find any report that was able to nail Microsoft to the wall with taking the BSD IP stack. None. Nada. Nill. With the number of web pages out there, and with Google looking at them, and with lots of anti-Microsoft fanatics willing to spill their guts, and with the utter total failure of any of these pages to document Microsoft using BSD code, I need pretty damn good evidence that they used the Berkely IP. French Zombies are zapping me with lasers!
Post #5,628 by boxley 8/17/01 12:26:56 PM Reply	the source they released for their original winsock 89? 90? wasnt bad but rather bare bones. They released it as an after thought when they were trying to convince the world that tcpip wasnt going anywhere. The code used streams, bind and listen where streams implementation is Berkley based. This is where the BSD stuff prolly came in. thanx, bill Our bureaucracy and our laws have turned the world into a clean, safe work camp. We are raising a nation of slaves. Chuck Palahniuk

Welcome to IWETHEY!