I remember setting this up in the Xerox offices. Many rewrites of the Network.ini and Protocol.ini files to get it to work with different network cards. The NE1000 was the most common NIC.
I grew up with 3.11 for workgroups, my uncle worked in IT and bought spare cards around and help us set it up. Blew my mind I didn’t need a floppy to transfer stuff. Also grew up with the nice choice of background music
WfWg 3.1 was a game=changer on the desktop. It made networking easy for the first time on a MS Client OS, and it simplified the entire config.sys mess that was created by forcing drivers to be loaded into the lower 640K under DOS/Windows 3.1. Interestingly it was the first version of windows where everything was virtualized (windows itself ran in a VM), and the underpinnings of this version became Windows 95. BTW, we referred to it as "Windows for Rockgroups" for reasons that I can't remember.
Pretty much. Windows for Workgroups 3.11 is actually much closer to Windows 95 than to base 3.1. This is pretty evident after you pop the hood and hook up the debugger.
Remember clearly how we built a little office network including a "file server" and a shared printer using WfWg. The coolest part was how easy we could share files between computers. Not only on the file server. No routers, no Internet, no tcp/ip, just simple non-routable NetBEUI. Loved it. And yes, this was prior to Ethernet so we used coax NICs.
Oh, I remember the era. 10-baseT Ethernet ring networks, LANtastic for DOS, … crikey. If you forgot the little green resistor cap, you'd let the bits fall out the end of the cable.
i remember 3.11 wfw at school. and boxes without hard drives. and the fun of winpopup. :D got myself in trouble there.. but it was fun messaging and broadcasting.
As I found out after the production of this video, Windows for Workgroups 3.1 (not 3.11) is actually quite a bit different. I didn't really dig into Windows networking until 95 although I did use Trumpet Winsock on these versions.
@@NCommander Windows for Workgroups 3.1 used a DOS based network stack.....not fun to deal with. WfW 3.11 was light years better. All the networking was protected mode VXDs, so no DOS memory management horrors. Also, MS backported their VFAT driver from Windows 95 in the form of 32-bit File Access. Overall it was pretty darned fast if you could also get 32-bit disk access working since it eliminates a ton of thunking between protected and real mode.
@@NJRoadfan I need to actually look at WfW 3.1 a bit more closely because it's actually somewhat distinct from WfW 3.11. The technical writeup for this article is still in progress, but the version of winsock in 3.1 has different UIs instead of the NT ones seen here. It also shipped on 10 disks in total, two more than WfW 3.11 so I want to see what justified another 2-3 megabytes of storage. WfW 3.11 did have 32-bit disk access (I ended clipping that out of this video) but didn't have VFAT, so it was still limited to 8.3 path names like DOS. A lot of what would become Windows 95 actually started here since the operating system kernel is very close to the Chicago builds. I had to spend a lot of time with the kernel debugger to try and resolve a crash without much success. The writeup should go up by Tuesday, and I'll pin a comment here when it does.
Windows for Workgroups is actually much closer to Windows 95. In the technical write-up for this video (which I just realize I didn't link), I actually go into this more in detail since WfW 3.11 runs into the same timing glitches Windows 95 does with NDIS.SYS I'll post a new comment with the technical write-up pinned.
That's because WIndows for Workgroups's core kernel is much closer to what would become WIndows 95 than Windows 3.1 RTM was. Basically Windows for Workgroups was the start of the 32-bit driver model, disk access and winsock, and it also dies on fast machines. I cut it from this video, but when I was trying to get this all working, it suffered a NDIS.SYS crash (which I needed a debugger to find) just like WIn95 does on faster hardware.
My grandfather used WfWg 3.11 as a desktop (no network, though he did have more than enough computers that it would have been worth connecting them). What I mostly remember is how unstable it was. I didn't use it a lot, but every single time it would just freeze randomly. "Why is the mouse not moving any more? Oh right, it's Windows 3.11" Looking at the comments, that was uncommon? Based on that experience, I always thought WfWg was the worst of the 3.x Windows.
we used this at school, and i have set it up with an NT 3.51 server ( which supports this more than NT4) i am sure there is a 3.1 version that will not support TCPIP at all, which could be what we used at school. but then again we are going back to 1997 to 2000, when i changed schools, The year 2000, windows 3.x machines were been scrapped off ready for windows 2000.
hey man, loved the video, however some criticism, if you could look at the camera more while talking, it would make the irl segments less awkward, but i still loved this a lot.
![[MV] A leap of faith...ความเชื่อใจครั้งสุดท้าย (From "Petrichor the series")](http://i.ytimg.com/vi/U1piZH2CNXA/mqdefault.jpg)
The technical write-up for this video is now available: soylentnews.org/article.pl?sid=20/05/14/1731231
פפ
I remember setting this up in the Xerox offices. Many rewrites of the Network.ini and Protocol.ini files to get it to work with different network cards. The NE1000 was the most common NIC.
I grew up with 3.11 for workgroups, my uncle worked in IT and bought spare cards around and help us set it up. Blew my mind I didn’t need a floppy to transfer stuff. Also grew up with the nice choice of background music
There was not much to play back then, and even just clicking the icons was very excited
WfWg 3.1 was a game=changer on the desktop. It made networking easy for the first time on a MS Client OS, and it simplified the entire config.sys mess that was created by forcing drivers to be loaded into the lower 640K under DOS/Windows 3.1. Interestingly it was the first version of windows where everything was virtualized (windows itself ran in a VM), and the underpinnings of this version became Windows 95. BTW, we referred to it as "Windows for Rockgroups" for reasons that I can't remember.
Pretty much. Windows for Workgroups 3.11 is actually much closer to Windows 95 than to base 3.1. This is pretty evident after you pop the hood and hook up the debugger.
Remember clearly how we built a little office network including a "file server" and a shared printer using WfWg. The coolest part was how easy we could share files between computers. Not only on the file server. No routers, no Internet, no tcp/ip, just simple non-routable NetBEUI. Loved it. And yes, this was prior to Ethernet so we used coax NICs.
Oh, I remember the era. 10-baseT Ethernet ring networks, LANtastic for DOS, … crikey.
If you forgot the little green resistor cap, you'd let the bits fall out the end of the cable.
Nice FF7 Theme Piano version
Also Aerith's theme
i remember 3.11 wfw at school. and boxes without hard drives. and the fun of winpopup. :D got myself in trouble there.. but it was fun messaging and broadcasting.
i love the aerith theme in this video
Oooo Packard Bell! I remember those!
Huh. Back then I only ever ran WFWG, but never used the network features... so I really had no idea about any of this!
As I found out after the production of this video, Windows for Workgroups 3.1 (not 3.11) is actually quite a bit different. I didn't really dig into Windows networking until 95 although I did use Trumpet Winsock on these versions.
@@NCommander Windows for Workgroups 3.1 used a DOS based network stack.....not fun to deal with. WfW 3.11 was light years better. All the networking was protected mode VXDs, so no DOS memory management horrors. Also, MS backported their VFAT driver from Windows 95 in the form of 32-bit File Access. Overall it was pretty darned fast if you could also get 32-bit disk access working since it eliminates a ton of thunking between protected and real mode.
@@NJRoadfan I need to actually look at WfW 3.1 a bit more closely because it's actually somewhat distinct from WfW 3.11. The technical writeup for this article is still in progress, but the version of winsock in 3.1 has different UIs instead of the NT ones seen here. It also shipped on 10 disks in total, two more than WfW 3.11 so I want to see what justified another 2-3 megabytes of storage.
WfW 3.11 did have 32-bit disk access (I ended clipping that out of this video) but didn't have VFAT, so it was still limited to 8.3 path names like DOS. A lot of what would become Windows 95 actually started here since the operating system kernel is very close to the Chicago builds. I had to spend a lot of time with the kernel debugger to try and resolve a crash without much success. The writeup should go up by Tuesday, and I'll pin a comment here when it does.
@@NCommander VFAT the protected mode installable file system driver, not VFAT the long file name extensions.
this is amazingly in-depth. great video!
I’m not sure if it’s already been done but I’d be interested in seeing a slightly more in-depth version of this video!
Actually, just reading your blog post now. Definitely much more in-depth.
It's interesting because it reminds me of Windows 95 network features. And after that it hasn't changed much.
Windows for Workgroups is actually much closer to Windows 95. In the technical write-up for this video (which I just realize I didn't link), I actually go into this more in detail since WfW 3.11 runs into the same timing glitches Windows 95 does with NDIS.SYS
I'll post a new comment with the technical write-up pinned.
That's because WIndows for Workgroups's core kernel is much closer to what would become WIndows 95 than Windows 3.1 RTM was. Basically Windows for Workgroups was the start of the 32-bit driver model, disk access and winsock, and it also dies on fast machines. I cut it from this video, but when I was trying to get this all working, it suffered a NDIS.SYS crash (which I needed a debugger to find) just like WIn95 does on faster hardware.
Fascinating content!
Great video. Thanks. Could you show us how you used the kernel debugger?
maan, online games at windows 3.11 thats amazing
I hear that background music every day, from Keith jarret though 😂
Windows for Workgroups, the POSReady 2009 of Windows 3.1x.
My grandfather used WfWg 3.11 as a desktop (no network, though he did have more than enough computers that it would have been worth connecting them). What I mostly remember is how unstable it was. I didn't use it a lot, but every single time it would just freeze randomly. "Why is the mouse not moving any more? Oh right, it's Windows 3.11"
Looking at the comments, that was uncommon? Based on that experience, I always thought WfWg was the worst of the 3.x Windows.
4:04 - Office Space
we used this at school, and i have set it up with an NT 3.51 server ( which supports this more than NT4) i am sure there is a 3.1 version that will not support TCPIP at all, which could be what we used at school. but then again we are going back to 1997 to 2000, when i changed schools, The year 2000, windows 3.x machines were been scrapped off ready for windows 2000.
Time for a Ruby weapon play through
Funfact: 3.11 for workgroups embedded ended its support in 2008
My ISP gave me a program called trumpet winsock that I had to run to connect.
Actually the windows for workgroups tune is used as announcement tune even today
hey man, loved the video, however some criticism, if you could look at the camera more while talking, it would make the irl segments less awkward, but i still loved this a lot.
I actually stopped showing myself when doing VOs, my SLS Linux video being the last one in which I do so.