Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Core OS Migration (Windows CE 5.0)

Windows CE 5.0
Send Feedback

This topic contains information about migrating this functionality from earlier versions of Windows CE.

For general migration information, see Migrating a Board Support Package and Migrating from an Earlier Version of Windows CE.

Migrating from Windows CE 2.12 and Windows CE 3.0

Windows CE .NET 4.0 introduced new functionality to reduce the burden of execute in place (XIP) dynamic-link libraries (DLLs) on the 32-MB virtual address space.

In earlier versions of Windows CE, all XIP DLLs had address regions permanently reserved in every process address space (slot). These reserved regions could not be used for operating system-managed heap memory or for other DLLs.

Because processes never use all ROM DLLs, this unnecessarily consumed valuable address space in every process slot.

In Windows CE .NET 4.0 and later, you can load XIP DLLs into process slot 1 and access them from any other process slot. Thus, each process has an additional 32-MB XIP region, and the standard 32-MB process space is free for use by heap and RAM-loaded modules.

During build time, the ROM image tool uses the following criteria to determine whether a particular module is placed in the slot 1 address space:

  • The module is an XIP module; that is, the module is in the MODULES section of its respective .bib file, and no compression has been specified.
  • The module has a valid .rel file of the same name in the same folder as the .bib file during the ROM image build.

See Also

Core OS Services

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
© 2014 Microsoft. All rights reserved.