Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!samsung!sol.ctr.columbia.edu!bronze!copper!rschmidt From: rschmidt@copper.ucs.indiana.edu (roy schmidt) Newsgroups: comp.windows.ms Subject: Re: How to UnMinimize Program Manager Summary: Not in the manual! Message-ID: <1991May22.160301.9704@bronze.ucs.indiana.edu> Date: 22 May 91 16:03:01 GMT References: <1991May7.172619.14418@mccc.edu> Sender: news@bronze.ucs.indiana.edu (USENET News System) Organization: Indiana University, Bloomington Lines: 37 pjh@mccc.edu (Peter J. Holsberg) writes: >I don't know what I did but every time I enter WIN, PM comes up >minimized and I would like it to come up maximized. I've looked through >WINI.INI and SYSTEM.INI and come up with zilch. Can anyone suggest a >way to reverse this? > >Thanks, >Pete It is interesting that Microsoft failed to document this phenomenon in the manual, and also left the explanation out of the WININI.TXT supplement. I happened on this when I tried installing "SCREENPEACE" (SP). I followed the directions in the installation package for SP, adding the line run=SAVER.EXE to the WIN.INI file. The next time I started WIN3, PM was minimized. So, I deleted the above line from WIN.INI and tried load=SAVER.EXE in its stead. Poof! PM was no longer minimized on starting WIN3. So, it seems that these two WIN.INI commands have unique properties. "run=" is designed to hand over control to an application (thus putting PM in the background) while "load=" will put the application in the background. DISCLAIMER: The above observations are based on an empirical experiment with a sample size of one. Since statistical significance is lacking, your mileage may vary. -- -------------------------------------------------------------------------- Roy Schmidt | #include Indiana University | /* They are _my_ thoughts, and you can't Graduate School of Business | have them, so there! */