home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: Why I love OS/2. (Kids, try this at home!)
- Message-ID: <1992Sep14.193907.21906@njitgw.njit.edu>
- Date: 14 Sep 92 19:39:07 GMT
- References: <Yeg0ve_00WBMQ9W25r@andrew.cmu.edu> <1992Sep11.164048.10925@nmt.edu>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 30
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <1992Sep11.164048.10925@nmt.edu> jreynold@nmt.edu (John Reynolds) writes:
- >
- >Yes, this is *cool*, and shows OS/2's "stuff", but I have a burning
- >question. How did the WPS restart itself? I posted a question a while back
- >about the same topic and got no response. Is there a special parameter or
- >config.sys directive to add or what?
-
- It's part of the "PMSHELL.EXE" program. It is loaded twice in
- CONFIG.SYS. The first time, it's in the PROTSHELL= line. In this
- context, it loads PM, and initializes the session manager and lets you
- run multiple sessions.
-
- The second time is as in the RUNWORKPLACE= line. The program
- mentioned here will restart if it's terminated, I believe. Normally,
- PMSHELL.EXE is here again. So, if PMSHELL quits (when WPS dies), it
- gets restarted. I believe if you place CMD.EXE on this line, and you
- kill it (by typing "exit"), it'll restart as well.
-
- If you run PMSHELL as an app, you can kill it and it won't restart.
-
- >In addition, how/why did WPS crash?
-
- WPS has some bugs. Fortunately, they aren't fatal. They should be
- fixed with the CSD. Coming soon to an ftp site near you.
-
- --
- |) David Charlap "LECTURER, n. One with his hand in your pocket,
- /|_ dic5340@hertz.njit.edu his tongue in your ear, and his faith in your
- ((|,) patience."
- ~|~ --- Ambrose Bierce, The Devil's Dictionary
-