Path: utzoo!utgpu!cunews!bnrgate!bwdls58!mlord
From: mlord@bwdls58.bnr.ca (Mark Lord)
Newsgroups: comp.windows.ms.programmer
Subject: Re: 386MAX and Borland C++ 2.0
Message-ID: <6039@bwdls58.bnr.ca>
Date: 14 Mar 91 17:12:40 GMT
References: <11880003@hpdmd48.boi.hp.com> <1545@tekig7.MAP.TEK.COM>
Sender: mlord@bwdls58.bnr.ca
Reply-To: mlord@bwdls58.bnr.ca (Mark Lord)
Organization: Bell-Northern Research, Ottawa, Canada
Lines: 26

<>Has anybody had any luck getting bcx and 386MAX 5.0 or 5.1 to work together.
<>
<>I run 386MAX 5.1 and when I run bcx my machine reboots!!
<
<I have tried this too, and while my machine doesn't do anything drastic like
<reboot, I do get an error message about an incompatible memory manager
<is installed.  I guess BCX incorporates its own DOS extender or memory manager
<that's incompatible with 386^max.

While my bcc BC++ upgrade has yet to arrive, the printed info I received from
Borland indicates that BCX uses the VCPI standard for DOS extenders.  This is
the one that was as close as anything to "industry standard" before MicroSnot
came out with "DPMI".

So the question is.. does 386MAX claim to be VCPI compliant?

Apparently QEMM 5.x is fully VCPI compliant, so I would imagine that QEMM
users ought to have no problems with BCX.  Since I use QEMM 5.11, I guess
I'll find out more as soon as BC++ arrives.
-- 
MLORD@BNR.CA  Ottawa, Ontario *** Personal views only ***
begin 644 NOTSHARE.COM ; Free MS-DOS utility - use instead of SHARE.EXE
MZQ.0@/P/=`J`_!9T!2[_+H``L/_/+HX&+`"T2<TAO@,!OX0`N1(`C,B.P/.DS
<^K@A-<TAB1Z``(P&@@"ZA`"X(27-(?NZE@#-)P#-5
``
end