Program Manageris theshellofWindows 3.xandWindows NT3.xoperating systems.This shell exposed a task-orientedgraphical user interface(GUI), consisting oficons(shortcutsfor programs) arranged intoprogram groups.It replacedMS-DOS Executive,afile manager,as the default Windows shell.

Program Manager
Developer(s)Microsoft
Operating systemMicrosoft Windows,OS/2
PredecessorMS-DOS Executive
SuccessorWindows Explorer
TypeShell

OS/22.0 and later included the Program Manager as part of its Win-OS/2 compatibility layer.[1]Win-OS/2, including the Program Manager, are still included in later derivatives of OS/2 such asArcaOS.[2]

Overview

edit

Program Manager descends fromDesktop Manager(also known asPresentation Manager), the shell forOS/21.2.[3]Unlike Desktop Manager, which presents its program groups in a simple list, and opens each group in a separate window, Program Manager opens program groups in child windows using the newmultiple document interfacein Windows 3.x. The icons used to represent Program Manager itself, program groups, and DOS applications inWindows 3.0are carried over from OS/2 1.2.Windows 3.1uses updated versions of these icons.

When executables were dropped into Program Manager fromFile Manager,Program Manager automatically used the executable's default icon embedded as data inside the.EXE file. Additionally, the Windows Setup program, which populated Program Manager with the standard icons of a fresh install, could also be used to add new icons in bulk after installation. Using SETUP /P from thecommand line,a standard layout could be installed on many machines in an enterprise using a single SETUP.INF configuration file.[4]

Beginning with Windows 3.1, 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, including the position of all program group icons, assuming that auto-arrange has been disabled. This allowed Microsoft testers to try many different configurations, but the feature remained in the shipped version.[5]

In later versions ofMicrosoft Windows,starting withWindows 95andWindows NT 4.0,Program Manager was replaced byWindows Exploreras the default shell. Specifically, theStart Menutook over program organization and launching duties. However, Windows 95 still gave the user the option to start Program Manager at boot.

Program Manager was still included in later versions of Windows, and could be accessed by executingPROGMAN.EXEfrom the command line orRundialog. It could be used as the default shell by specifying theShellvalue in theregistryat eitherHKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon(per machine) orHKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon(per user).

Microsoft replaced Program Manager inWindows XP Service Pack 2with acompatibility stubthat simply redirects to Windows Explorer. InWindows Vistaand later,PROGMAN.EXEwas permanently removed from the operating system.

See also

edit

References

edit
  1. ^Timothy F. Sipples (20 February 1995)."OS/2 Warp Frequently Asked Questions List".
  2. ^"Getting the most out of DOS and Win-OS/2 sessions".Retrieved2020-09-03.
  3. ^OS/2 1.2
  4. ^Livingston 1993,p. 38
  5. ^Livingston 1993,p. 33

Cited works

edit

Livingston, Brian (1993).More Windows 3.1 Secrets.San Matao, CA: UDG Books Worldwide, Inc.ISBN1-56884-019-5.