Article ID: 81821 - Last Review: July 19, 2005 - Revision: 2.2 Program Manager Does Not MaximizeThis article was previously published under Q81821 SYMPTOMS
When a program is started using the run= line in the WIN.INI file, or
by placing its name on the command line that starts Windows, Program
Manager starts minimized. When Program Manager is restored, Program
Manager does not come up maximized, even if it was maximized when you
last exited Windows and saved changes.
WORKAROUND
The only workaround at this time is to save the changes with Program
Manager in a non-maximized state, but with the borders pulled out as
far as possible.
STATUS
Microsoft has confirmed this to be a problem in Windows version 3.0. This
problem was corrected and does not occur in later versions of Windows.
MORE INFORMATION
The WIN.INI file has a run= line, on which program executable filenames
can be placed. For example:
win winword
This is as opposed to using the load= line in the WIN.INI file where the
programs start minimized as icons on the desktop. One consequence of
starting programs on the run= line or the command line is that Program
Manager is minimized regardless of whether or not Minimize On Use is
selected in the Options menu of Program Manager.
If the Program Manager is then restored by double-clicking its icon, it returns in a non-maximized state. This occurs even if, when the you last exited Windows, Program Manager was maximized and the changes were saved. The state of Program Manager, minimized, maximized, or restored (open as a Window but not maximized) is recorded in the PROGMAN.INI file in the [Settings] section. The line appears as follows When the program starts, Program Manager is minimized. When you double- click on its icon, Program Manager displays in a window but is not maximized. The value in the PROGMAN.INI file, however, is not changed. It is still 3. | Article Translations
|


Back to the top
