How to Modify Program Properties in Windows 3.11

In Microsoft Windows 3.11, the primary system utility used to configure and modify program execution properties was the PIF Editor (Program Information File Editor). While Windows-native executables relied on simple settings configured through Program Manager, DOS-based applications required precise memory, video, and processor allocations to run properly inside the graphical environment. This article covers how the PIF Editor operated, the specific execution properties it controlled, and the role of Program Manager's property dialogs in Windows 3.11.

The PIF Editor (PIFEDIT.EXE)

The PIF Editor was an administrative utility located in the Main program group of Windows 3.11. It created and modified files with a .PIF extension. Rather than launching a .BAT, .COM, or .EXE file directly, users ran the associated .PIF file, which instructed Windows on how to allocate resources for that specific program.

When operating in 386 Enhanced Mode, the PIF Editor allowed users to fine-tune several critical execution parameters:

  • Memory Requirements: Users could set minimum and maximum allocations for conventional memory (KB required and KB desired), Expanded Memory (EMS), and Extended Memory (XMS). This prevented DOS programs from starving Windows or other tasks of system RAM.
  • Display Usage: The tool allowed users to define whether the application launched in Full Screen mode or inside a Window. It also allowed locking video memory to prevent display corruption when switching tasks.
  • Multitasking Options: Users could assign background and foreground processor priorities. Enabling "Background" allowed the program to continue executing tasks (such as downloading files or compiling code) when the user switched to another window. Checking "Exclusive" suspended all other background tasks to dedicate the CPU entirely to the active program.
  • System Shortcut Trapping: The editor let users reserve shortcut keys (such as Alt+Tab, Alt+Esc, or Ctrl+Esc) so that the application, rather than the Windows shell, intercepted those commands.

Program Manager Properties

For native 16-bit Windows applications, execution settings did not require a .PIF file. Instead, users modified properties directly inside Program Manager:

  1. Select the program icon.
  2. Open the File menu and choose Properties (or press Alt+Enter).
  3. In the Program Item Properties dialog, users could modify:
    • Command Line: Path to the executable file and optional startup switches.
    • Working Directory: The default folder the application used when saving or opening files.
    • Shortcut Key: A custom key combination to quickly switch to or launch the application.
    • Run Minimized: A checkbox to launch the software directly into an icon on the desktop rather than opening an active window.

The PIF Editor and Program Manager properties together provided the necessary execution controls to bridge legacy MS-DOS software with the multitasking graphical environment of Windows 3.11.