> The latter four digits could be the time that this build was compiled, which would correspond to 00:22
I'm curious how the Windows build lab was set up in those days. To me something like this says that daily build was started by automation at midnight and took 22 minutes.
> The build functions well on top of standard, standalone MS-DOS for the most part. However, the WinOldAp module that enables running MS-DOS applications under Windows depends on functionality that was implemented by Cougar, the 32-bit DOS kernel project, and is therefore broken under this copy of the build.
I remember building a circa 1.0 kernel for Linux on a 386 in the early 90s (would have been around 1995) and it took > 24 hours to compile - I'm sure someone could speed run this today, but that's what I remember :)
I mean, this basically is Windows 3.1 with some small changes; it doesn't have win32 and it's visually 3.1 with a theme added. Looks right to me for "Windows 3.1 with 3 months of development towards the next version".
I'm curious how the Windows build lab was set up in those days. To me something like this says that daily build was started by automation at midnight and took 22 minutes.
> The build functions well on top of standard, standalone MS-DOS for the most part. However, the WinOldAp module that enables running MS-DOS applications under Windows depends on functionality that was implemented by Cougar, the 32-bit DOS kernel project, and is therefore broken under this copy of the build.
Translation: identical outcome as with the explicit https://en.wikipedia.org/wiki/AARD_code but now with plausible legal deniability.