|
|
|
|
|
|
by haspok
1 day ago
|
|
|
Windows 3.1 was probably the first mainstream version of Windows, with significantly less memory requirements (and it ran no problem on a 286 IIRC). Windows 3.11 came almost 1.5 years later (despite the minor version bump), and mostly added networking, which _was_ memory hungry, but back then, people were happily running their computers isolated, especially at home. I guess my point is, 4MB was really a lot of memory around 1992, and fitting a windowing environment in 640K was more the norm, and not an especially outstanding feat. Just think about GEOS and how it ran on the C64... or the Amiga (with a preemptive OS running on 256KB), or the Atari ST... |
|
|
Careful. You are confusing Windows 3.11 with Windows for Workgroups 3.11. They were different products, at different times.
This is why version 3.11 of the Linux kernel was called Linux For Workgroups:
https://www.linuxfoundation.org/blog/blog/linux-kernel-3-11-...
That "for Workgroups" meant a whole different OS with a networking layer, protocol stacks, additional dialog boxes in File Manager to map and disconnect network drives and more.
WfWg was both a client and a server.
The first version was WfWg 3.1 which could run on a 286.
The one everyone deployed was WfWg 3.11 which despite its minor version bump was a 32-bit only OS needing 4MB of RAM because it only supported 386 Enhanced Mode. This was the version to contain some of the new tech from the forthcoming Windows 4.0, codenamed "Chicago" and later named "Windows 95".
WfWg 3.11 had 32-bit File Access as well as 3.1's 32-bit Disk Access. 32bFA was internally VFAT.VXD and that's why the Linux FAT16/FAT32 driver is called `VFAT.`
It had a 32-bit network stack in a VXD as well, which optionally supported a LAN-only 32-bit TCP/IP stack.
http://www.thenetworkencyclopedia.com/entry/tcp-ip-32-for-wi...
Here's the README. :-)
If you want it for some unimaginable reason, here is a download:
https://winworldpc.com/product/microsoft-tcp-ip-32/tcpip-32-...