Understanding Windows CE's Memory Layout
Monday, 18 September 2006 by Michel Roth
While application developers can usually ignore issues of memory mapping in Windows CE, engineers writing board support packages (BSPs) need to understand how Windows CE's memory is mapped, and the tools that make that happen. This article by a developer on Microsoft's Windows CE Embedded BSP team sheds light on this topic.

The three principal tools that manage memory mapping, according to author Travis Hobrla, are the OEMAddressTable and the files config.bib and boot.bib (.bib stands for "binary image builder"). The OEMAddressTable specifies mappings between virtual address space and physical address space, while the two .bib files contain configuration information about the Windows CE OS image and the bootloader, espectively.

Read the entire article at WindowsForDevices.com.

Related Items:

What Is Virtual Memory (In WindowsCE) ? (7 November 2006)
One reason Why Windows Server 2008 Terminal Server Will Allow You To Get More Users On A Box (10 February 2008)
Online Videos And Labs Introduce Windows CE 6.0 (3 November 2006)
Windows XPe ImageDiff To Ease Windows XPe Migrations (6 March 2007)
Comments (0)add feed
password
 

busy