home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!bogus.sura.net!opusc!tbone.biol.scarolina.edu!dean2
- From: dean2@tbone.biol.scarolina.edu (Dean Pentcheff)
- Newsgroups: comp.os.os2.misc
- Subject: Minimization flakiness??
- Followup-To: comp.os.os2.misc
- Date: 29 Jan 1993 02:33:34 GMT
- Organization: Department of Biology, University of South Carolina, Columbia
- Lines: 28
- Sender: Dean Pentcheff
- Message-ID: <1ka51uINNdf9@bigbird.csd.scarolina.edu>
- Reply-To: dean2@tbone.biol.scarolina.edu (Dean Pentcheff)
- NNTP-Posting-Host: tbone.biol.scarolina.edu
-
- I've been running the TCP/IP package, which puts lots of windows on the
- desktop as it boots (one for each of the control or daemon programs).
- Our users were not really able to figure out how to minimize them when
- they booted, so I figured I'd do us all a favor and have them come up
- minimized from the start. So... I edited the ".cmd" files that kick
- them off so that each "start ...." command was changed to "start /min
- ....".
-
- Worked fine on one machine.
-
- Went to the other machine, made the same changes, but on this machine,
- minimization seems to quit halfway through the boot process. The first
- few networking processes are properly minimized, but after that, other
- network processes come up as regular windows. Running a command
- explicitly as "start /min some_command_name" from an OS/2 window causes
- a non-minimized command to run.
-
- Apparently, "start /min" begins to fail to minimize early on in my boot
- sequence (and never heals).
-
- Any ideas on what might cause minimization to cease?
-
- Thanks!
-
- -Dean
- --
- Dean Pentcheff (Internet: dean2@tbone.biol.scarolina.edu) (803) 777-8998
- Department of Biology, University of South Carolina, Columbia SC 29205
-