From: George Foot <mert0407 AT sable DOT ox DOT ac DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: overlaying
Date: 21 Feb 1998 23:29:21 GMT
Organization: Oxford University, England
Lines: 25
Message-ID: <6cno0h$9g5$1@news.ox.ac.uk>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980219202053 DOT 13131A-100000 AT is>
NNTP-Posting-Host: sable.ox.ac.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On Thu, 19 Feb 1998 20:24:09 +0200 (IST) in comp.os.msdos.djgpp Eli
Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:

: On Thu, 19 Feb 1998, Anthony.Appleyard wrote:

: > > ABC.CC reserves(_go32_dpmi_allocate_dos_memory() etc) some conventional
: > > memory, whose address it sends to XYZ.CC as hex chars as a call argument,
: > > and XYZ.CC can leave information in that area for ABC.CC to read.
: >   but I was told "no, ABC's conv mem is swopped out while XYZ.CC is running".

: Whoever told you that was dead wrong.  If ABC.CC allocates DOS memory, it
: stays allocated until ABC.CC exits.  DOS memory is almost *never* swapped
: out (because DOS lives there too, and you cannot swap DOS).  Even if it
: *is* swapped out, it will be swapped in when you try to access it. 

I think perhaps the person quoted in "" above was talking about
communicating between DOS boxes under Win95, for example, where each
really does have its own separate conventional memory.  Of course,
this is a different situation to the one A.Appleyard was asking
about.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk

ko tavla fo la lojban