Xref: utzoo comp.os.msdos.programmer:3880 comp.windows.ms.programmer:1292
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!pacbell.com!pacbell!well!brent
From: brent@well.sf.ca.us (Brent Southard)
Newsgroups: comp.os.msdos.programmer,comp.windows.ms.programmer
Subject: Re: How can I get BCX to work inside of Windows?
Message-ID: <23555@well.sf.ca.us>
Date: 11 Mar 91 23:48:36 GMT
References: <1991Mar7.151918.21996@isis.cs.du <1991Mar7.180233.3362@aplcen.apl.jhu.edu> <91066.163143LIBCRN@BYUVM.BITNET>
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 26

In article <91066.163143LIBCRN@BYUVM.BITNET> LIBCRN@BYUVM.BITNET writes:
>
>   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.

Well, XMS stands for Extended Memory Specification, which defines extended
memory which is managed by an XMM (extended memory manager), such as
himem.sys.  Unfortunately, Borland didn't see fit to use this spec as far as
I can tell for their protected mode products.  I sure don't know why.

The point is moot in this case, since the Borland protected mode tools
(except for TASMX) are not DPMI-compliant and hence will not run in Enhanced
mode.  You can run BCX in Standard mode though, if you follow the
instructions in the User's Guide.

brent
-- 
brent southard  (313) 643-1971   |   usenet:  ...!well!brent
ImageTech Corp  (313) 353-7900   |   bix:     brent

"When frog licking is outlawed, only outlaws will lick frogs."