Windows CE 6 Kernel Architecture Print E-mail
Written by Henrik Viklund   
Thursday, 14 August 2008 23:10

With CE 6's new kernel layout the file system, the bulk of the drivers and GWES have been moved into the kernel. The kernel has also been restructured to allow better encapsulation from the OAL, and a number of actions have been taken to make the kernel more secure and robust. According to MS, the kernel performance compared to CE 5 can be summarized:

  • size has increased less than 5%
  • some performance gain in process switching is expected
  • inter-process calls will have some overhead attached to it
  • Thread switching, memory allocations and system calls will have about the same performance

If you want to learn more aboutthe new kernel features, the new kernel layout and PQOAL, I think you'll find this article interesting.

Microsoft Windows Embedded CE 6 Resources Print E-mail
Written by Henrik Viklund   
Thursday, 05 June 2008 16:53
November 1:st 2006 Microsoft finally released Windows Embedded CE 6. With the release, of course, a whole bunch of information and documentation naturally started to appear across the internet. So, to wrap-up my CE 6 article series, I thought that rather than writing any more about the inner workings of CE 6, I’d point out where to find good, in-depth information about Windows Embedded CE 6.
Windows CE 6 Memory Architecture Print E-mail
Written by Henrik Viklund   
Saturday, 03 May 2008 19:58

In version 6 of Microsoft Windows CE, aka "Yamazaki",  Microsoft have done some pretty major changes. Among other things, CE 6 sports a redesigned kernel and a new memory model. While the new memory model makes a giant leap forward in terms of per-process memory and number of running processes, it is also fundamentally different from what we're used to from CE 5 and before. In this article I'll be taking a closer look at Microsoft Windows CE 6's virtual memory model.

Version Control Strategy for Windows CE Platform Environments Print E-mail
Written by Henrik Viklund   
Tuesday, 18 March 2008 21:27

Platform Builder is one of those environments that really resist being put under version control. Especially if you’re new to Platform Builder, it can be a very frustrating and time consuming experience to put the environment under version control. It’s not just the cheer number of files that a Windows CE image is built from that can be hard to cope with, but also the fact that some of the Platform Builder tools don’t cope well with some version control systems.

What this article aims for is not to describe some sort of divine methodology that will work for all situations, because I don't beleave such methodologies exist. Instead, I'll try to give you a starting point; I’ll describe what I consider the minimum amount of ceremony needed to effectively version control a Platform Builder environment –the least amount of complexity that still floats the boat, so to speak. Also, I’ll cover the most usual workarounds that are needed to get a version controlled Platform Builder Environment up and running.

This article targets Windows CE 5, but I believe that the general principles discussed here apply to most versions of the Windows CE source tree.


Microsoft Windows Embedded Partner