Edit - Retrocomputing Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3

See also How did Microsoft take over Winsocks?
– Stephen Kitt
Commented Mar 6 at 5:41
I remember those days. Windows wasn't the only OS that did not ship with TCP/IP. Unix almost always had TCP/IP since that was where it evolved but even then there was disagreement on how the API to use TCP/IP should be: sockets or streams. TCP/IP and sockets won.
– slebetman
Commented Mar 7 at 8:26
Did Windows 3.11 (for networks) change anything substantial for TCP?
– Captain Giraffe
Commented Mar 7 at 23:04
@CaptainGiraffe Windows for Workgroups (WfWg) 3.11 had it's own TCP/IP stack and WINSOCK.DLL so it basically eliminated the need for any of the third party stacks like Trumpet. I developed network software in the 90's and prior to that it was really a hodge podge on Windows 3.x until WfWg and then later Windows 95.
– mannaggia
Commented Mar 12 at 21:57

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »