From: "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Borland Pascal & CWSDPMI
Date: Tue,  7 Oct 1997 19:33:53
Organization: Aspen Technology, Inc.
Lines: 13
Message-ID: <343a8ea1.sandmann@clio.rice.edu>
References: <Pine DOT HPP DOT 3 DOT 96 DOT 971007152654 DOT 3659A-100000 AT coffee DOT geophysik DOT tu-freiberg DOT de>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: nboal2.dmccorp.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

> call "bp" = Borland Pascal with cwsdpmi resident in memory (e.g.
> from inside of dos-bash) there will be an error "16 Bit DPMI not
> allowed" (not literally). Do you know, what I can do about it? Some Option
> in CWSDPMI?

Your only hope is to get a copy of 386max and see if it works for you.  The
DPMI 0.9 spec specifically states you can't have 16-bit and 32-bit DPMI 
clients running in the same virtual machine. 

Borland products expect the DPMI to provide extension also, so just 
adding 16-bit support to CWSDPMI didn't solve the problem.  I had some
Borland products running under a hacked version of CWSDPMI a few years ago,
but the code was bloated, ugly and unmaintainable, so it was never migrated.