Hi Eddy,

 you wrote at 09.01.99  12:01 to me:

HR>> The space from 512 to 448 MB contains system code, data and
HR>> the callgate. 

 ET> Denis said that the system uses memory starting at the top and
 ET> allocating memory below when needed, and applications use memory
 ET> from the bottom up. Only OS/2 v2.xx and Warp 3 GA have a reserved
 ET> area. That's what Denis told me.

During bootup the system is loaded at end of virtual memory. Occupying the
highest available RAM. System data is reserved beginning with 0. 

User addressspace is reserved beginning at hex 10000 to end of memory.
There is no significant change in that since OS/2 2.0. 

HR>> No. No for ALL loaded *.exe they will link to, 

 ET> What do you mean by this?

If a DLL is loaded it becomes its own addressspaces for its memory
segments. A memory segment is described in the binary loaded and has
nothing to do with the paging mechanism except that it describes how many
pages of a kind of memory type is needed and contains many relative
addresses with fixup data for binding and its data (code, constant/variable
data).

So if a new program request the linkage to a already loaded dll it becomes
in it s page descriptors links to the shared memory pages of that
particular DLL and new pages created and assigned to that DLL for nonshared
data.


Tschau/Bye

Herbert


--- Sqed/32 1.14/development  13: