No I'm fairly certain that berkley sockets were used as a foundation to integrate a full network stack under winsockets so people wouldn't have to go buy things like Trumpet (Windows 3.1) and you could coax out messages saying as much from the commandline but Google is failing me (I'm sure most of this stuff is on usenet which no one seems to care about these days)
That was Windows 2000.
The story with the Windows NT IP stack is nuanced, but it wasn't just lifted from BSD: https://web.archive.org/web/20051114154320/http://www.kuro5h...
No I'm fairly certain that berkley sockets were used as a foundation to integrate a full network stack under winsockets so people wouldn't have to go buy things like Trumpet (Windows 3.1) and you could coax out messages saying as much from the commandline but Google is failing me (I'm sure most of this stuff is on usenet which no one seems to care about these days)
The history of the Windows TCP/IP stack went most likely like this:
IBM (NetBEUI, no TCP/IP) -> Spider TCP/IP Stack + SysV STREAMS environment -> MS rewrite 1 (early NT, Winsock instead of STREAMS) -> MS rewrite 2 (make win2000 faster):
https://web.archive.org/web/20151229084950/http://www.kuro5h...
6 replies →
Win95 had its own stack, codenamed Wolverine