home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!ira.uka.de!fauern!fauna!cip.informatik.uni-erlangen.de!hmkirchh
- From: hmkirchh@cip.informatik.uni-erlangen.de (Hans-Joachim Kirchhoff)
- Subject: Re: Borland C++ in OS2
- References: <1992Sep2.062046.28031@coe.montana.edu> <1992Sep2.144448.936@nmt.edu>
- Message-ID: <BtzxpG.JBL@immd4.informatik.uni-erlangen.de>
- Sender: news@immd4.informatik.uni-erlangen.de
- Organization: CSD., University of Erlangen
- Distribution: usa
- Date: Thu, 3 Sep 1992 09:44:04 GMT
- Lines: 27
-
- jreynold@nmt.edu (John Reynolds) writes:
- >>Does anyone have Borland C++ running under OS2 2.0? I was wondering what
- >>the dos settings are to make it work.
-
- >You must set the DPMI_API (note, I can't remember the exact names of these,
- >but there's not way to get them confused...) to "ENABLED". Then, set the
- >DPMI_MEMORY_LIMIT to around 6MB or what ever's comfortable. Then, set the
-
- Setting the memory limit does not do anything, UNLESS you also change
- Borlands own settings in O|ption, E|nvironment, S|tartup, to use 6Meg
- of extended memory. If you do this, you should also set EMS to 0.
- But I cannot imagine, why anyone would need 6 Meg with Borland? I still
- got a few hundred KByte left, when compilig a large App, so why bother
- OS/2 with this much RAM?
-
- >DOS_IDLE_DETECTION to '100' to _disable_ OS/2's idle detection of BC++.
-
- Also I don't think, IDLE_DETECTION is necc. I did not change any settings there
- and I don't have any trouble with that. BC seems to belong to the well
- behaved DOS applications, that don't eat up CPU time in an idle loop,
- just polling the keyboard, which is, what Idle Detection is for.
-
- -Hajo
- ---
- --------------------------------------------------------------------------
- Hans-Jochen Kirchhoff | hmkirchh@cip.informatik.uni-erlangen.de
- > No signature today | CompuServe 100024,712
-