Re: Wordstar?
> Huh? No, Microsoft offered an TCP/IP stack as well. You can create such a DOS-TCP/IP Disk from NT 4.0 Server CD, see directory \CLIENTS\MSCLIENT\.
One thing I find tiring about the retrocomputing web in general is that people take half-remembered stuff and then confidently assert that their partial recollections are official canonical Truth because They Were There and Don't You Dare Disagree.
Look, Mr Mxyzptlk, you have a tiny germ of truth here but it's not really correct, and the person that you are replying to was more correct than you are.
DOS did not really meaningfully support TCP/IP, no. Your assertion does not contradict this.
DOS didn't have networking. Very late on, 3rd party DOSes like Novell DR-DOS had network stacks, yes, but they were just as much bolted-on extras as Hummingbird, Wollongong, or the like, that @martinusher was talking about.
If you wanted to do Internet stuff on DOS, then you could. There were stacks like KA9Q:
https://www.ka9q.net/code/ka9qnos/
These were tiny and simple and offered a TCP/IP interface to DOS apps so that DOS code could access Internet services. Like Unix, there were lots of Internet protocols so each was small and simple: telnet, finger, ping, ftp, nfs, etc.
Result: a small stack you could run in your base 640kB and access selected services.
There were also DOS network requesters. THESE ARE NOT THE SAME THING BUT YOU ARE CONFLATING THEM. There were 2 dominant "standards" for these:
* Novell Netware (running NETX over the IPX/SPX protocol)
* LAN Manager, with clients from IBM, 3Com, Microsoft, and others
Later these were extended with configurable driver stacks. Two of them, mutually incompatible.
Novell invented ODI drivers.
Microsoft invented NDIS drivers.
In both cases, the stack got more open but a lot more complex. Now you could take a protocol driver and a network requester and run them on top of an arbitrary card driver. Woohoo, now instead of ~2 bits of software, you have ~6 to ~8 each with config files.
This also led to configurable protocols. Novell basically let you talk TCP/IP as well as IPX/SPX. An expensive addon for Netware let it act as an Internet border router and you could deploy intranet services. (Internal private Internet-protocol services, like an internal website, or internal Internet email.) Thus Netware was rebranded Intranetware
MS went deeper.
The MS and IBM client stacks defaulted to NetBEUI. (Ignore Wikipedia whose editors were not there and have edited the coverage into word salad.)
MS let you add IPX/SPX and even remove NetBEUI and if you had IPX/SPX on your server (LanMan, or Windows for Workgroups, or OS/2, or NT) then clients could still connect _over the same protocol they talked to Netware over_.
MS also let you add TCP/IP. Big woo.
It released a 16-bit TCP/IP stack that ran on DOS, and Windows for Workgroups 3.1, and Windows for Workgroups 3.11. Yes, really, those OSes shipped without TCP/IP. In 1993 or so it was not important in PC networks.
Later MS also added a 32-bit TCP/IP stack that could only run inside WfWg 3.11.
Here you go, have a look:
https://winworldpc.com/product/microsoft-tcp-ip-32/tcpip-32-3-11b
This let LanMan file/disk/print sharing operate over TCP/IP.
But that does _not_ mean "MS offered a TCP/IP stack for DOS."
This was a network requester operating over TCP/IP. It was big and complicated and hairy and quite slow.
See these benchmarks:
https://www.os2museum.com/wp/dos-smb-client-performance/
This anatomises the layers in case you think I'm making this stuff up.
Most DOS internet apps couldn't talk to it, so it was no use for Internet access. It was also something like 10x the size so when it was loaded you didn't have enough of your base 640kB to load a DOS web browser or something big like that.
_This is why WfWg took off._ DOS didn't have the room for this stuff.
So, while in a dictionary sense your claim that "MS offered free TCP/IP for DOS" is true, it is missing the point. It wasn't a free TCP/IP stack: it was a free network requester that could optionally and with some effort use TCP/IP.
The stacks that mattered were not from MS. Or IBM. Or Novell.
They were things like PC-TCP:
https://en.wikipedia.org/wiki/FTP_Software
Or Hummingbird:
https://www.proquest.com/docview/226865123?sourcetype=Trade%20Journals
You're mixing up faint memories of a free network requester with paid TCP/IP for DOS tools. The few DOS Internet apps didn't even work with these big fat requester stacks.
As an example, I spent ages getting DESQview/X running in a VM but I can't find a free TCP/IP stack it can talk to. The MS one doesn't work for this.
As another example, if you download *16-bit* Internet Explorer 3 or 4 for Windows 3.1 -- note, NOT Windows for Workgroups -- you will find that it includes its own freeware integrated-but-optional dial-up TCP/IP stack using WINSOCK which is entirely separate from and does not interoperate with the DOS or Windows 3.x network stack.
https://tangentsoft.com/wskfaq/articles/history.html
Always check your facts. Know when you're not sure. Now: Kltpzyxm!