Retro Potato: Longtime Microsoft software program engineer Raymond Chen lately responded to an intriguing retro-tech query posed by a sport developer on X. The developer inquired in regards to the three distinct consumer interfaces used in the course of the Home windows 95 setup course of, which transitioned from DOS to Home windows 3.x, and eventually to the traditional Win9x GUI. Chen explaining that it was a deliberate design selection to attenuate the quantity of code required for the Home windows 95 configuration expertise.
Skilled PC customers could also be effectively conscious of the peculiar relationship between MS-DOS code and the GUI setting throughout the Win9x ecosystem. Nonetheless, in keeping with Chen, the multi-OS help constructed into the Home windows 95 setup program was way more subtle than it would initially appear.
With over 30 years of expertise shaping the evolution of Home windows, Chen holds deep insights into the hidden intricacies of one of many world’s most generally used software program platforms. Writing The Outdated New Factor weblog, he mentioned Home windows 95 setup was designed to improve programs from three potential beginning factors – MS-DOS, Home windows 3.1, and Home windows 95 itself. This necessity dictated the necessity for compatibility with three distinct computing environments.
The setup program was primarily written as an MS-DOS utility however was designed to run on three totally different working programs to carry out distinct duties. The DOS portion was crucial when setup was launched from the MS-DOS immediate, as accessing the Win9x setting would have been not possible with out first putting in it on the onerous drive.
Additionally see: Who wrote the BSOD display screen? Former Home windows developer lastly has a solution
The MS-DOS setup part put in a minimal model of Home windows 3.1 – simply sufficient to help the 16-bit portion of the setup device. After booting into this miniature Home windows 3.1 setting, the 16-bit GUI setup program would launch. This utility might additionally run in a full Home windows 3.x setting and even inside an already put in Home windows 95 OS, enabling customers to restore a corrupted system if crucial.
The 16-bit Home windows utility was the centerpiece of the method, Chen defined, because it dealt with the vast majority of duties required for the “actual” Home windows 95 set up. This graphical interface managed consumer interplay, collected configuration information, decided which OS parts to put in, and carried out {hardware} detection to pick out the suitable drivers.
After copying the Home windows 95 information and drivers to the system, the 16-bit setup booted into the Win9x setting. The third and ultimate setup stage concerned a real Win32 utility, which finalized the set up by dealing with duties akin to putting in printers and configuring different peripherals.
By chaining collectively these three setup packages, Microsoft was capable of streamline growth by reusing a single codebase throughout all three predominant set up situations. “Every program takes you one step nearer to the objective. And every thing bought applied solely as soon as,” the developer mentioned.
