home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!ucla-cs!ucla-se!edison!ygoland
- From: ygoland@edison.seas.ucla.edu (The Jester)
- Newsgroups: comp.os.os2.apps
- Subject: Re: Borland C++ 3.1 in a DOS Session
- Message-ID: <7707@lee.SEAS.UCLA.EDU>
- Date: 26 Jul 92 20:36:39 GMT
- References: <l73u8cINNev9@alnitak.usc.edu>
- Sender: news@SEAS.UCLA.EDU
- Organization: The Hacker Conference
- Lines: 28
-
- I program professionaly using borland c++ 3.1 IDE under
- os/2. I use the following settings with great success:
- DOS_BACKGROUND_EXECUTION - ON (for no particular reason)
- DOS_HIGH - On (every K counts)
- DPMI_DOS_API - ENABLED (THIS IS CRUCIAL)
- IDLE_SECONDS - 60
- IDLE_SENSITIVTY - 100 (The last two are a matter of taste. When I am
- working in BC I DO NOT want to have it
- premepted by ANYONE)
- To the best of my recolection those are the only settings which
- really matter. Actually only DPMI_DOS_API matters. The rest are just
- preference. I run bc alot and without problems. The only problem I
- do have, though, is with screen draws. I am using a trident card
- running their 800x600x16 mode (I want seamless windows) and when I
- initially boot bc I tend to do it in a window. But then after 10
- minutes I want full screen (eye strain =) and when I initially move
- over I get screen garble (Mostly because I run bc 3.1 in 43 (or
- whatever) line mode and I don't think os/2 is quite sure what to do
- with that) but pressing ctrl-esc to go to the window list and then
- double clicking on borland c++ to go back, takes care of the
- problem.
- The Jester
-
- --
- The Jester-President of The Hacker Conference
- "Never trust an oyster"-Super Chicken
- "You know the job was dangerous when you took it"-Super Chicken
- "Trust me, I know what I'm doing"-Sledge Hammer
-