Newsgroups: comp.windows.ms Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!bronze!copper!rschmidt From: rschmidt@copper.ucs.indiana.edu (roy schmidt) Subject: Re: How to UnMinimize Program Manager Message-ID: <1991May29.000906.12703@bronze.ucs.indiana.edu> Sender: news@bronze.ucs.indiana.edu (USENET News System) Organization: Indiana University, Bloomington References: <1991May7.172619.14418@mccc.edu> <47416@muvms3.bitnet> <1991May19.004750.8740@ux1.cso.uiuc.edu> Date: Wed, 29 May 91 00:09:06 GMT Lines: 28 This is simple, really. There isn't any bug, and there isn't any complicated routine to go through. 1. The "run=" command in win.ini is designed to run a program when Win3 starts. If you use this command, you are running the program outside of Program Manager, so naturally ProgMan is minimized because it is in the background and your other program has the floor. (If the program you run is something like ScreenPeace or Idlewild (screen savers), then that program will also be minimized waiting for its "trigger.") 2. The "load=" command runs a program through ProgMan, so here the performance varies. If you selected "Minimize on Run" for ProgMan, then it will be minimized because you are running an application. Otherwise, the application will come up on top of ProgMan just like usual. (Again, screen savers will be minimized waiting for the "trigger.") So, if you want ProgMan "UnMinimized" at the start, then use "load=" inst. I had sent this observation to Pete last week, but he obviously has not yet summarized any replies he received. For that reason, I am posting this to try to quell the wave of "me toos" :-) -- -------------------------------------------------------------------------- Roy Schmidt | #include Indiana University | /* They are _my_ thoughts, and you can't Graduate School of Business | have them, so there! */