home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!mips!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!PKSMRVM.VNET.IBM.COM!KENKAHN
- From: KENKAHN@PKSMRVM.VNET.IBM.COM ("Kenneth A. Kahn")
- Newsgroups: comp.os.os2.misc
- Subject: Re: Using CMD.EXE instead of PMSHELL.EXE
- Message-ID: <9208131529.AA00624@ucbvax.Berkeley.EDU>
- Date: 13 Aug 92 14:14:23 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Lines: 18
-
- Organization: Staff of IBM Fellow - NetWork Computing
- Disclaimer: This posting represents the poster's views, not those of IBM
- News-Software: UReply 3.0
- X-X-From: KENKAHN@PKSMRVM.VNET.IBM.COM (Ken Kahn)
- References: <1992Aug12.155015.14039@kakwa.ucs.ualberta.ca>
-
- In <1992Aug12.155015.14039@kakwa.ucs.ualberta.ca> Kurt Klingbeil writes:
- >Could someone please explain what core functionality PMSHELL provides;
- >i.e. apart from GUIness... ?
-
- As you suggested in your original post, the 2 biggest things you lose when
- you run CMD instead of PMSHELL are support for Multiple Processes and PM
- applications. If all your applications are full screen, and you don't intend
- on runningmore than one at a time, then you can use this environment. You
- might ask what u can gain from this; well you are still running OS/2 V2 so you
- can run any 16 or 32-bit application. You can run Full Screen DOS with the
- right Device Drivers and such set up.
-
-