From: "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP TSR and C++'s new command
Date: Thu, 14 May 1998 13: 2: 6
Organization: Aspen Technology, Inc.
Lines: 12
Message-ID: <355aeb4e.sandmann@clio.rice.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980513131638 DOT 26491A-100000 AT is>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: dmcap2.aco.aspentech.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

> Since writing a TSR requires DPMI 1.0 calls, this would mean that you use 
> either CWSDPMI or 386Max, is it correct?

The current prot mode TSR example does not use any DPMI 1.0 calls, so 
should run under most DPMI providers.

> So I would advise to stay clear of memory allocation inside an interrupt.

This is good advice.  If you knew for sure what the maximum number of 
allocations was going to be, by malloc/free'ing that memory it would not
require a call back to sbrk() and might work.  Might, since the reentrancy
issues.