home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.apps
- Subject: Re: os/2-the user's view
- Message-ID: <1992Aug17.161628.28248@njitgw.njit.edu>
- Date: 17 Aug 92 16:16:28 GMT
- References: <1992Aug13.1479.4914@dosgate> <weinkam.713760866@sfu.ca>
- Sender: news@njit.edu
- Distribution: comp
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 30
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <weinkam.713760866@sfu.ca> weinkam@fraser.sfu.ca (James Lawrence Weinkam) writes:
- >"roger ramsey" <roger.ramsey@canrem.com> writes:
- >
- >>That's just one of my beefs. There are several ways you can run Windows
- >>apps under OS/2 2.0. the highlights are:
- >
- >>a) Run them in a separate screen group (as you do). This assigns all
- >>Windows apps to one VDM which runs modified Windows 3.0 code to implement
- >>the parameter checking of Windows 3.1. Unfortunately, the same old GDI of
- >>Windows 3.0 is employed to there is no performance enhancment and you get
- >>performance degradation based on OS/2 overhead to manage the VDM (thunking
- >>- 16-bit to 32-bit conversion).
- >
- >>c) Run Windows in an OS/2 DOS VDM (open a DOS VDM and start Windows).
- >>Not exactly recommended and certainly not a commonplace way of running
- >>Windows apps.
- >
- >It is my understanding that when you start win-os2 full screen that it
- >first opens a dos vdm and runs windows in the vdm. Thus a) and c) would
- >be identical.
-
- I think he means installing Microsoft Windows 3.0 and running it, not
- running WIN-OS2.
-
-
- --
- |) David Charlap "I don't even represent myself
- /|_ dic5340@hertz.njit.edu sometimes so NJIT is right out!.
- ((|,)
- ~|~ Hi! I am a .signature virus, copy me into your .signature file.
-