Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!obelix.cs.uoregon.edu!akm
From: akm@obelix.cs.uoregon.edu (Anant Kartik Mithal)
Newsgroups: comp.windows.ms
Subject: Re: How to UnMinimize Program Manager
Message-ID: <1991May19.171249.1465@cs.uoregon.edu>
Date: 19 May 91 17:12:49 GMT
References: <47416@muvms3.bitnet> <1991May19.004750.8740@ux1.cso.uiuc.edu> <1991May19.011654.29323@leland.Stanford.EDU>
Sender: usenet@cs.uoregon.edu (Netnews Owner)
Organization: Department of Computer Science, University of Oregon
Lines: 29

In article <1991May19.011654.29323@leland.Stanford.EDU> elmanad@leland.Stanford.EDU (Adam Elman) writes:
>This thread is getting very confusing.  
>As far as I have experienced, here is what happens.
>If I have a program such as USHER.EXE in the "run=" line, Progman
>comes up minimized and the program runs in a window (or, in usher's
>case, it just runs.)
>[]
>I would guess that the way to run Progman and another program in a
>window is to specify Progman as the last program on the "run=" line.

My $0.02:

First I think that the suggestion above won't work. If you have
progman minimized, and issue a run progman (I did this through usher),
progman stays iconized. (A second copy does not run.)

One of my machines is set up with usher as the shell, and has progman
in the run line. This has the advantage of getting windows to start up
with progman as a window. The drawback is that on quitting windows,
the new things in progman are not saved (though I am not 100% sure of
this.) I suppose that the same effect would be obtained by making
winfile the shell, and setting run= to include progman.

kartik
-- 
Anant Kartik Mithal                                     akm@cs.uoregon.edu
Research Assistant, 					(503)346-4408 (msgs)
Department of Computer Science,                         (503)346-3989 (direct)
University of Oregon, Eugene, OR 97403-1202