X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Authentication-Warning: mcomail01.maxtor.com: iscan owned process doing -bs
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Obtaining the physical address of a pointer using PMODE
Date: Mon, 21 Nov 2005 17:30:52 -0700
Message-ID: <71078E41DDE3E541B024832F34BC3D0DA3082C@cowexc03.corp.mxtr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: djgpp weekly digest for 19 Nov 2005
Thread-Index: AcXtkD9bZvj16bORTpqtg5AsElwUegBYHuyA
From: "Schumacher, Gordon" <gordon_schumacher AT maxtor DOT com>
To: "DJGPP List \(E-mail\)" <djgpp AT delorie DOT com>
X-OriginalArrivalTime: 22 Nov 2005 00:30:52.0573 (UTC) FILETIME=[FE9B74D0:01C5EEFB]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id jAM0Utv8000502

# From: "Roland Zitzke" <NZEONTQYRAHL AT spammotel DOT com>
# Subject: Re: Obtaining the physical address of a pointer using PMODE
# Date: Wed, 16 Nov 2005 19:45:18 +0100
# Message-ID: <dlfunv$2ta4$1 AT ulysses DOT news DOT tiscali DOT de>
# X-Trace: ulysses.news.tiscali.de 1132166719 95556 
# 
# Hello and thanks for the links.
# as far as I can tell people were discussing to allocate mory 
# in a fassion suitable for different extenders. However if I use
# pmode/dj, isn't there a way to malloc a chunk of memory and somehow
# detect the physical address of this chunk?

I'm not sure about this, actually.  We're running using CWSDPMI,
not PMODE, and that's been working for us.

# DOS with himem.sys installed and WITHOUT EMM386 is the only 
# environment I am really interested in.

That's how we're running too.  We *can* run with EMM386 - but only
poorly.  It allocates memory from the top down, which is the worst
thing possible for building scatter/gather tables.

# and I have no idea what that is good for i.e. what I need the 
# physical_map function for.
# Any hints?

I'm afraid that I personally wasn't the person on our team working
on this code; the main guy who was is no longer at the company (but
he may be reading this list anyway *ping*).  My life is spent up in
app-space :)

Charles Sandmann would probably be the right person to talk to about
this for details.