Xref: utzoo comp.os.msdos.programmer:3818 comp.windows.ms.programmer:1244
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!psuvax1!psuvm!cunyvm!byuvm!libcrn
From: LIBCRN@BYUVM.BITNET
Newsgroups: comp.os.msdos.programmer,comp.windows.ms.programmer
Subject: How can I get BCX to work inside of Windows?
Message-ID: <91066.163143LIBCRN@BYUVM.BITNET>
Date: 7 Mar 91 23:31:43 GMT
References: <ONEEL.91Mar2115359@heawk1.rosserv.gsfc.nasa.gov>
 <1991Mar4.150257.422@ccad.uiowa.edu> <1991Mar7.151918.21996@isis.cs.du
 <1991Mar7.180233.3362@aplcen.apl.jhu.edu>
Organization: Brigham Young University
Lines: 29


   I am trying to get the extended version of Borland's IDE (BCX.EXE)
to work from within Windows.  I have set up a .PIF file for this
purpose which specifies that BCX is to be given 800 Kbytes of extended
memory to work with (XMS does stand for extended memory, doesn't it?).
Unfortunately, when I invoke BCX, I always get an error message that
says that 0 Kbytes of extended memory is available when 706 Kbytes is
needed.  Is is possible to get BCX to work from within Windows?  BCX
works great outside of Windows but it is a REAL pain to have to get
out of Windows every time you want to recompile a program.

   To illustrate why I would rather use BCX.EXE instead of BC.EXE, here
are two comparisons of compile-and-link times between BCX and BC.  The
two programs are very simple.

PARTY.C      (from Petzold's book)
        BC   --  5.5 minutes.
        BCX  --  16 seconds.

WHELLO.CPP   (one of the example programs that comes with BC++)
        BC   --  8 minutes  (thats right EIGHT MINUTES !)
        BCX  --  40 seconds.


   My Hardware:  IBM PS/2  Model 55sx    with   4 Mbytes RAM.

Thanks for any help.

-- Cory  (libcrn@byuvm.bitnet)