Windows Server 2016: End of One Era, Start of Another

Re:Windows Server 2016: End of One Era, Start of Another by jasode on Thursday September 29, 2016 @10:12AM (#12605326)

I don't think so because I remember in 1994 that many companies were running Microsoft NETBIOS. Microsoft was already winning the server war before TCPIP became the default choice in the late 1990s. At one time, I remember having to install extra software (Hummingbird?) to get a usable TCPIP stack on MS Windows. However, I don't remember exactly which version of Microsoft Windows I had to do that.

[ Parent | on HN ]

Re:Windows Server 2016: End of One Era, Start of Another by chiph on Thursday September 29, 2016 @10:28AM (#12605451)

Most people installed Trumpet Winsock on Windows 3.1 to get a TCP/IP stack (written by Peter Tattam, who never got much money out of it since few people paid the shareware fees).

I'm thinking that one reason Microsoft won was because of superior developer tools. I admin'd a small Netware 4.x machine back then and I couldn't even tell you what was needed to write an NLM.

[ Parent | on HN ]

Re:Windows Server 2016: End of One Era, Start of Another by okket on Thursday September 29, 2016 @10:29AM (#12605469)

AFAIK Hummingbird is/was an Windows implementation for the X11 display protocol (called 'server'). The TCP/IP protocol was added in Win98 by default IIRC, until then you had to use Trumpet Winsock (Win3.x) or something like that.

[ Parent | on HN ]

Re:Windows Server 2016: End of One Era, Start of Another by mhurron on Thursday September 29, 2016 @11:24AM (#12605979)

TCP was included by default with Windows 95 and NT 3.1.

[ Parent | on HN ]

Re:Windows Server 2016: End of One Era, Start of Another by IntelMiner on Thursday September 29, 2016 @06:04PM (#12609158)

NT 3.1 yes, Windows 3.1 however no

[ Parent | on HN ]