Note: Before remixing, please read the instructions. Doing so will give you a better understanding of how to remix. Also, if you have any spare time on your hands, go ahead and remix this project by improving something! (I'm not saying I should rush you or anything, though.) Hello, and welcome to a special Number Evolution! The rules are still the same as any IENE: evolve the number by no more than one and slightly increase the project's effort. This time, you have to make the project like Windows 3.1 with said program manager while still making the number evolution aspect present. Also, only elite Number Evolutionists can remix this project. This includes @Octo_NE56, @OisinFan62, @WindowsMeRules2000, their alts, and more. It's recommended to add only 1 feature to every remix. You do not need to change the effort as it's assigned to a formula: Number + 1000 effort. (Making mistakes will punish you, so try not to make one.) If you want to add sounds for the thumbnail, add startup/shutdown sounds from OS's from 1992 and minor versions after that with the same major version. (NROS sounds are accepted.) Please make the Program Manager more and more complete with every remix. (THIS IS THE PRIMARY GOAL, PLEASE FOCUS ON IT, NO EXCEPTIONS.) The minimum number of frames is 10. If that is deleted on purpose, we'll have to re-add it again. By -750, we need the Control Panel icon to be vectorized. (That was done at -775.) We'll also need to the project's minimum quality to be ( Information about the current program we're coding in: Program Manager is the shell of Windows 3.x and Windows NT 3.x operating systems. This shell exposed a task-oriented graphical user interface (GUI) consisting of icons (shortcuts for programs) arranged into program groups. It replaced MS-DOS Executive, a file manager, as the default Windows shell. OS/2 2.0 and later included the Program Manager as part of its Win-OS/2 compatibility layer. Win-OS/2, including the Program Manager, is still included in later derivatives of OS/2, such as ArcaOS. Program Manager originates from Desktop Manager, the shell for OS/2 1.2. Unlike Desktop Manager, Program Manager opens program groups in child windows using the new multiple document interface in Windows 3. Many of the icons in Windows 3.0 are carried over from OS/2 1.2. Windows 3.1 uses updated versions of these icons. When executables were dropped into Program Manager from File Manager, Program Manager automatically used the executable's default icon embedded as data inside the .EXE file. Additionally, the Windows Setup program, which populated the Program Manager with the standard icons, could also be used to add new icons in bulk after installation. Typing SETUP /P in the command prompt allows the user to install the standard layout on several computers in an enterprise using a single SETUP.INF configuration file. Beginning with Windows 3.1, the Program Manager contained a StartUp group. Programs and files placed into that group would be loaded when Windows starts. Holding down the shift key while selecting File then Exit Windows will save the current configuration of Program Manager to PROGMAN.INI. This also includes the position of all program group icons (assuming that auto-arrange has been disabled). This allowed Microsoft testers to try several different configurations, but the feature remained in the shipped version.
Credit to all. I guess since we've already vectorized 2 icons ahead of schedule, the next step will just be improving the project quality. #evolutionchains
