Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!borland.com!sidney
From: sidney@borland.com (Sidney Markowitz)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Compiling/linking Windows Apps under Borland C++
Message-ID: <1991Apr25.171402.10333@borland.com>
Date: 25 Apr 91 17:14:02 GMT
References: <{G0&GB_@ads.com>
Organization: Borland International
Lines: 24

In article <{G0&GB_@ads.com> efulsang@ADS.COM (Ejner Fulsang) writes:
>
>I've been following the suggestions for efficient compiling and
>linking of C++ programs using Borland C++ while running under 
>Windows 3.0.  The consensus on the net seemed to be to load 
>tkernel first and then run Windows in the standard mode as follows:
>
>          tkernel hi=yes kilos=1024
>          win /s

One more step, which is actually the whole reason for doing the above:
run bcx instead of bc.

My results building whello.prj from the BC++ examples directory on a
Compaq Portable 386/20 with lots of memory:

 1) using bc.exe under DOS: ~16 seconds
 2) using bc.exe with tkernel loaded under win/s and no pif
    (which is a worst case - bc.exe doesn't make use of tkernel,
     which just takes memory away from it, and without a pif bc has
     no EMS memory available for fast swapping): ~5 minutes
 3) using bcx.exe with tkernel and win/s as above, no pif: ~12 seconds

 -- sidney markowitz <sidney@borland.com>