Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
MSDN Library
Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Memory Architecture

Windows Mobile 6.5
A version of this page is also available for
4/8/2010

In any Windows phone, ROM stores the entire OS, in addition to the applications that come with the OS design. Windows Mobile supports a 32-bit (4-GB) address space.

When a process initializes, the OS maps the following DLLs and memory components:

  • Some execute-in-place (XIP) DLLs
  • Some read/write sections of other XIP DLLs
  • All non-XIP DLLs
  • The stack
  • The heap
  • A data section for each process

DLLs are controlled by the loader, which loads all the DLLs at the same address for each process. The stack, the heap, and the executable (.exe) file are created and mapped from the bottom of the address space. The bottom 64 KB of memory always remains free.

DLLs and ROM DLL read/write sections are loaded starting at the top of the address space.

Community Additions

Show:
© 2015 Microsoft