← Back to context

Comment by masfuerte

18 hours ago

Yes, but like Windows for Workgroups before them, they didn't need to rely on DOS services once they had started. They were 32-bit multitasking OSes that could host multiple DOS VMs and (in the case of WfW) a 16-bit cooperatively multitasked GUI.

DOS basically acted as a bootloader. But all of those OSes had the very weird feature that they could switch back into a virtualised copy of their bootloader.

I do feel that Wikipedia understates the importance of Windows for Workgroups. Internally, it wasn't just Windows 3.1 with networking. It was a trial run for the fundamentals of the Windows 95 architecture.

In other words, they were bare-metal hypervisors which passed through the majority of the hardware, doing a minimum of virtualisation to allow sharing it between VMs. This is easy to see by comparing the responsiveness of a DOS box running something like EDIT in Win9x vs. NT/2K/XP's NTVDM; the latter is a full emulator of basically all the hardware except the CPU.

This is exactly why I come to HN, vs Wikishemedia... People here WERE THERE!

When I worked at C_ we used to load Some solitaire game (Freecell) to verify that Windows98SE was in 32-bit mode before installing the network stack, and Chief Legal Officer, and from what I understand CLO was $4,000 a seat.

Load Driver, Reboot, Solitare, CLO. and then onward to disk optimizing, and then virus scanning... Two people did 89 machines, in 4 days. an entire floor... Food was delivered, and we slept for 4 hours, in the floor below, and on Friday, The head of Legal called us into his office... we showed him the checklist, as complete, and He laughed... the whole department was both amazed and happy.

He really called us to change his desktop into a scene from JAWS.

It was Windows 98SE that got a 32-bit disk driver upgrade, and FreeCell verified that it was installed.