From:	blp01 AT uow DOT edu DOT au (Brett Porter)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Sound libs 4 DJGPP
Date:	Sat, 25 Jul 1998 02:17:51 GMT
Organization:	University of Wollongong, Australia
Lines:	48
Message-ID:	<35b93e27.2422004@news.uow.edu.au>
References:	<35B58218 DOT BA040281 AT logic-gate DOT com> <35B5AAB0 DOT 459BF813 AT calderauk DOT com> <6p4btq$bre$1 AT star DOT cs DOT vu DOT nl> <35B5EB2A DOT 613262FD AT calderauk DOT com>
Reply-To:	blp01 AT uow DOT edu DOT au
NNTP-Posting-Host:	ceast15.uow.edu.au
NNTP-Posting-Date:	25 Jul 1998 02:22:04 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

>You must have a resident DPMI server that supports both 16 and 32 bit
>protected mode applications (CWSDPMI doesn't need to) without any bias
>towards certain applications (Borland RTM/32RTM does this).
>
>The Win95 DPMI system does this, but the windows 3.1 DPMI server will
>not function correctly.
>
Firstly, yes, the Borland RTM servers suck. This is a well-established
fact and is probably the reason they no longer exist in new Borland
products (AFAIK).

>If you don't have a DPMI server resident, then the process of compiling
>MIDAS will start with GNU make.  This will start CWSDPMI.
>Make will then shell out to 16-bit DPMI tools which will simply abort,

I can't understand why. I run pure DOS often with CWSDPMI resident
from running it in AUTOEXEC.BAT with the -p option. Everything runs
fine except stuff that uses DOS4GW: it doesn't sit happily with
CWSDPMI, mostly because DOS4GW isn't a strict extender.

>and if it survives that, it will run O2Cpack which will crash under
>CWSDPMI, plain and simple.  I don't know why yet.
>

I'll tell you why: whoever wrote O2Cpack (whatever that is) have been
playing with their pointers in a way they are not meant to, such as
dereferencing NULL's.

CWSDPMI is the best server to run at least for development of software
because it will make your program screw up if it does something it
wasn't meant to. But for this reason it is not great for running stuff
you haven't written yourself, because programmers are notoriously bad
at handling pointers (unless they've years of experience under Unix or
a variant which is nice and strict as well).

I hope this clears it up a little. Poor CWSDPMI gets bashed regularly
for being a bad server, where all it is doing is making sure that the
program isn't attempting to totally mess up the computer.

cya
Brett
---------------------------------------------------
        Brett Porter <blp01 AT uow DOT edu DOT au>
      http://members.xoom.com/brett_porter

"I always like to do a first draft before being
 spontaneous." -- The Sandman
---------------------------------------------------

- Raw text -