Menu
Home Explore People Places Arts History Plants & Animals Science Life & Culture Technology
On this page
Windows CE
Discontinued embedded operating system by Microsoft

Windows CE, later known as Windows Embedded Compact, is a discontinued operating system developed by Microsoft for mobile and embedded devices. Unlike other Windows IoT variants based on Windows NT, Windows CE used a unique hybrid kernel and was licensed to OEMs who could customize user interfaces. Initially supporting architectures like MIPS and SHx, from version 7.0 it dropped some support, focusing on MIPS II, while its final release in 2013 targeted x86 and ARM processors. Support ended by 2023, but OEM licensing continues until 2028.

We don't have any images related to Windows CE yet.
We don't have any YouTube videos related to Windows CE yet.
We don't have any PDF documents related to Windows CE yet.
We don't have any Books related to Windows CE yet.
We don't have any archived web articles related to Windows CE yet.

Features

Windows CE is optimized for devices that have minimal memory; a Windows CE kernel may run with one megabyte of memory.8 Devices are often configured without disk storage, and may be configured as a "closed" system that does not allow for end-user extension (for instance, it can be burned into ROM). Windows CE conforms to the definition of a real-time operating system, with a deterministic interrupt latency. From Version 3 and onward, the system supports 256 priority levels9 and uses priority inheritance for dealing with priority inversion. The fundamental unit of execution is the thread. This helps to simplify the interface and improve execution time.

The first version – known during development under the code name "Pegasus" – featured a Windows-like GUI and a number of Microsoft's popular apps, all trimmed down for smaller storage, memory, and speed of the palmtops of the day. Since then, Windows CE has evolved into a component-based, embedded, real-time operating system. It is no longer targeted solely at hand-held computers.10 Many platforms have been based on the core Windows CE operating system, including Microsoft's AutoPC, Pocket PC 2000, Pocket PC 2002, Windows Mobile 2003, Windows Mobile 2003 SE, Windows Mobile 5, Windows Mobile 6, Smartphone 2002, Smartphone 2003, Portable Media Center, Zune, Windows Phone 7 and many industrial devices and embedded systems. Windows CE even powered select games for the Sega Dreamcast and was the operating system of the Gizmondo handheld.

A distinctive feature of Windows CE compared to other Microsoft operating systems is that large parts of it are offered in source code form. First, source code was offered to several vendors, so they could adjust it to their hardware. Then products like Platform Builder (an integrated environment for Windows CE OS image creation and integration, or customized operating system designs based on CE) offered several components in source code form to the general public. However, a number of core components that do not need adaptation to specific hardware environments (other than the CPU family) are still distributed in binary only form.

Windows CE uses WCELDR as its second stage boot loader in x86 platforms; or uses EBOOT as its boot loader in ARM platforms. Windows CE uses manufacturer-prebuilt Registry to manage hardware devices.11 On the startup process, NK.BIN boot image or NK.EXE kernel is loaded by the WCELDR or EBOOT bootloader.1213

Windows CE 2.11 was the first embedded Windows release to support a console and a Windows CE version of cmd.exe.14

History

Windows Embedded Compact was formerly known as Windows CE. According to Microsoft, "CE" is not an explicit acronym for anything, although it implies a number of notions that Windows developers had in mind, such as "compact", "connectable", "compatible", "companion" and "efficient".1516 The name changed once in 2006, with the release of Windows Embedded CE 6.0, and again in 2011, with the release of Windows Embedded Compact 7.

Windows CE was originally announced by Microsoft at the Computer Dealers' Exhibition (COMDEX) in 1996 and was demonstrated on stage by Bill Gates and John McGill. Microsoft had been testing Pegasus in early 1995 and released a strict reference platform to several hardware partners. The devices had to have the following minimum hardware specifications:

  • SH3, MIPS 3000 or MIPS 4000 CPU
  • Minimum of 4 MB of ROM
  • Minimum of 2 MB of RAM with a backup power source, such as a CR2032 coin cell battery
  • Powered by two AA batteries
  • A physical QWERTY keyboard including Ctrl, Alt, and Shift keys
  • A LCD of 480×240 pixels with four shades of gray and two bits per pixel with touchscreen that could be operated by either stylus or finger
  • An IrDa transceiver
  • Serial port
  • PC Card socket
  • Built-in speaker

Devices of the time mainly had 480×240 pixel displays with the exception of the Hewlett-Packard 'Palmtop PC' which had a 640×240 display. Each window took over the full display. Navigation was done by tapping or double tapping on an item. A contextual menu was also available by the user pressing the ALT key and tapping on the screen. Windows CE 1.0 did not include a cascading Start menu, although Windows 95 and Windows NT 4.0 did. Microsoft released the Windows CE 1.0 Power Toys that included a cascading menu icon that appeared in the system tray. Also bundled were several other utilities, most notable were a sound applet for the system tray, enabling the user to quickly mute or unmute their device or adjust the volume and a 'pocket' version of Paint.

The release of Windows CE 2.0 was well received. Microsoft learned its lessons from consumer feedback of Windows CE 1.0 and made many improvements to the operating system. The Start menu was a cascading menu, identical to those found on Windows 95 and Windows NT 4.0. Color screens were also supported and manufacturers raced to release the first color H/PC. The first to market was Hewlett Packard with the HP 620LX. Windows CE 2.0 also supported a broader range of CPU architectures. Programs could be also installed directly in the OS by double clicking on CAB files. Due to the nature of the ROMs that contained the operating system, users were not able to flash their devices with the newer operating system. Instead manufacturers released upgrade ROMs that users had to physically install in their devices, after removing the previous version. This would usually wipe the data on the device and present the user with the setup wizard upon first boot.

In November 1999, it was reported that Microsoft was planning to rename Windows CE to Windows Powered.17 The name only appeared in brand in Handheld PC 2000 and a build of Windows 2000 Advanced Server for network-attached storage devices (which bears no relation to Windows CE). Various Windows CE 3.0 products announced at CES 2001 were marketed under a "Windows Powered" umbrella name.18

Development tools

Visual Studio

Microsoft Visual Studio 2012, 2013, and 2015 support apps and Platform Builder development for Windows Embedded Compact 2013.19

Microsoft Visual Studio 2008 and earlier support projects for older releases of Windows CE/Windows Mobile, producing executable programs and platform images either as an emulator or attached by cable to an actual mobile device. A mobile device is not necessary to develop a CE program. The .NET Compact Framework supports a subset of the .NET Framework with projects in C#, and Visual Basic (.NET), but not Managed C++. "Managed" apps employing the .NET Compact Framework also require devices with significantly larger memories (8 MB or more) while unmanaged apps can still run successfully on smaller devices. In Visual Studio 2010, the Windows Phone Developer Tools are used as an extension, allowing Windows Phone 7 apps to be designed and tested within Visual Studio.

Free Pascal and Lazarus

Free Pascal introduced the Windows CE port in Version 2.2.0, targeting ARM and x86 architectures. Later, the Windows CE header files were translated for use with Lazarus, a rapid application development (RAD) software package based on Free Pascal. Windows CE apps are designed and coded in the Lazarus integrated development environment (IDE) and compiled with an appropriate cross compiler.20

Platform Builder

This programming tool is used for building the platform (BSP + Kernel), device drivers (shared source or custom made) and also the apps. This is a one stop environment to get the system up and running. One can also use Platform Builder to export a software development kit (SDK) for the target microprocessor (SuperH, x86, MIPS, ARM etc.) to be used with another associated tool set named below.

Others

The Embedded Microsoft Visual C++ (eVC) – a tool for development of embedded apps for Windows CE. It can be used standalone using the SDK exported from Platform Builder or using the Platform Builder's Platform Manager connectivity setup.

CeGcc project provides GNU development tools, such as GNU C, GNU C++ and binutils that targeting Windows CE;21 2 SDKs are available to choose from – a standard Windows CE platform SDK based on MinGW, and a newlib-based SDK which may be easier for porting programs from POSIX systems.22

CodeGear Delphi Prism – runs in Visual Studio, also supports the .NET Compact Framework and thus can be used to develop mobile apps. It employs the Oxygene compiler created by RemObjects Software, which targets .NET, the .NET Compact Framework, and Mono. Its command-line compiler is available free of charge.

Basic4ppc – a programming language similar to Embedded Visual Basic, targets the .NET Compact Framework and supports Windows CE and Windows Mobile devices.

GLBasic – a very easy to learn and use BASIC dialect that compiles for many platforms, including Windows CE and Windows Mobile. It can be extended by writing inline C/C++ code.

LabVIEW – a graphical programming language, supporting many platforms, including Windows CE.

MortScript – is the semi-standard, extremely lightweight, automation SDK popular with the GPS enthusiasts. Uses the scripts written in its own language, with the syntax being aside to VBScript or JScript.

AutoHotkey – a port of the open source macro-creation and automation software utility available for Windows CE. It allows the construction of macros and simple GUI apps developed by systems analyst Jonathan Maxian Timkang.23

Relationship to Windows Mobile, Pocket PC, and Smartphone

Timeline of Windows CE development

Often Windows CE, Windows Mobile, and Pocket PC are used interchangeably, in part due to their common origin. This practice is not entirely accurate. Windows CE is a modular/componentized operating system that serves as the foundation of several classes of devices. Some of these modules provide subsets of other components' features (e.g. varying levels of windowing support; DCOM vs COM), others which are separate (bitmap or TrueType font support), and others which add additional features to another component. One can buy a kit (the Platform Builder) which contains all these components and the tools with which to develop a custom platform. Apps such as Excel Mobile (formerly Pocket Excel) are not part of this kit. The older Handheld PC version of Pocket Word and several other older apps are included as samples, however.

Windows Mobile is best described as a subset of platforms based on a Windows CE underpinning. Currently, Pocket PC (now called Windows Mobile Classic), Smartphone (Windows Mobile Standard), and Pocket PC Phone Edition (Windows Mobile Professional) are the three main platforms under the Windows Mobile umbrella. Each platform uses different components of Windows CE, plus supplemental features and apps suited for their respective devices.

Pocket PC and Windows Mobile are Microsoft-defined custom platforms for general PDA use, consisting of a Microsoft-defined set of minimum profiles (Professional Edition, Premium Edition) of software and hardware that is supported. The rules for manufacturing a Pocket PC device are stricter than those for producing a custom Windows CE-based platform. The defining characteristics of the Pocket PC are the touchscreen as the primary human interface device and its extremely portable size.

CE 3.0 is the basis for Pocket PC 2000 and Pocket PC 2002. A successor to CE 3.0 is CE.net.24 "PocketPC [is] a separate layer of code on top of the core Windows CE OS… Pocket PC is based on Windows CE, but it's a different offering." And licensees of Pocket PC are forbidden to modify the WinCE part.25

The Smartphone platform is a feature-rich OS and interface for cellular phone handsets. SmartPhone offers productivity features to business users, such as email, and multimedia abilities for consumers. The SmartPhone interface relies heavily on joystick navigation and PhonePad input. Devices running SmartPhone do not include a touchscreen interface. SmartPhone devices generally resemble other cellular handset form factors, whereas most Phone Edition devices use a PDA form factor with a larger display.

Releases

VersionNameReleasedSupport statusChanges
1.0Windows CE 1.0November 16, 199626Unsupported as of December 31, 2001.Codename "Pegasus" and "Alder".27
  • Devices named "handheld PC" (H/PC)28
  • 4 MB ROM minimum
  • 2 MB RAM minimum

1.01 version (1.0a) – added Japanese language support.

2.0Windows CE 2.0September 29, 199729Unsupported as of September 30, 2002 for Windows CE 2.11. Mainstream Support ended on September 30, 2003, and Extended Support ended on September 30, 2005, for Windows CE 2.12.Codenamed "Birch".30
  • Devices named "Palm-size PC" (PsPC)31
  • Real-time deterministic task scheduling
  • Architectures: ARM, MIPS, PowerPC, StrongARM, SuperH and x86
  • 32-bit color screens
  • SSL 2.0 and SSL 3.0

2.11 version (Palm-Size PC 1.1) – changed screen resolution to QVGA, added handwriting recognition.2.11 version (Palm-Size PC 1.2) – based on Windows CE H/PC 2.11 kernel, removed Pocket Office.HandeldPC 2.11 version (HandheldPC Professional) – added small versions of Microsoft Access, improved Microsoft Office documents formats support.

3.0Windows CE 3.0June 15, 200032Mainstream Support ended on September 30, 2005, and Extended Support ended on October 9, 2007.Codenamed "Cedar"33 and "Galileo".
  • Major recode that made CE hard real time down to the microsecond level
  • Base for the Pocket PC 2000, Handheld PC 2000, Pocket PC 2002 and Smartphone 200234
  • Priority levels were increased from 8 to 25635
  • Object store was increased from 65,536 to 4.19 million allowed objects36
  • Restricted access to critical APIs or restricting write access to parts of the registry37
4.xWindows CE 4.xJanuary 7, 200238Mainstream Support ended on July 10, 2007, and Extended Support ended on July 10, 2012, for Windows CE 4.0, Mainstream Support ended on January 8, 2008, and Extended Support ended on January 8, 2013, for Windows CE 4.1 and Mainstream Support ended on July 8, 2008, and Extended Support ended on July 9, 2013, for Windows CE 4.2.Codenamed "Talisker/Jameson/McKendric".39
5.0Windows CE 5.xAugust 2004.44Mainstream Support ended on October 13, 2009 and Extended Support ended on October 14, 2014.Adds many new features. Codenamed "Macallan"45
  • Added automatic reporting for manufacturers46
  • Direct3D Mobile, a COM-based version of Windows XP's DirectX multimedia API47
  • DirectDraw for 2D graphics and DirectShow for camera and video digitisation support48
  • Remote Desktop Protocol (RDP) support49
  • The "Pro" version contains the Internet Explorer browser and Windows Media Player 9
6.0Windows Embedded CE 6.0September 2006Mainstream Support ended on April 9, 2013, and Extended Support ended on April 10, 2018.Codenamed "Yamazaki".50
  • Process address space is increased from 32 MB to 2 GB;51 each process now has its own virtual memory map (all processes shared a VM map in CE 5.0)52
  • Number of processes has been increased from 32 to 32,76853
  • User mode and kernel mode device drivers are possible
  • 512 MB physically managed memory
  • Device.exe, filesys.exe, GWES.exe have been moved to Kernel mode
  • Cellcore
  • SetKMode and set process permissions no longer possible
  • System call performance improved54
  • the platform builder requires Microsoft Visual Studio 2005 with Service Pack 1 installed.
7.0Windows Embedded Compact 7March 2011Mainstream Support ended on April 12, 2016, and Extended Support ended on April 13, 2021.
  • Support for x86, SH (automotive only) and ARM.
  • Multi-core CPU support (SMP).
  • Wi-Fi Positioning System.
  • Bluetooth 3.0 + HS support.
  • Digital Living Network Alliance (DLNA).
  • DRM technology.
  • Media Transfer Protocol.
  • Windows Phone 7 IE with Flash 10.1 support.
  • NDIS 6.1 support.
  • UX C++ XAML API using technologies like Windows Presentation Foundation and Silverlight for attractive and functional user interfaces.
  • Modernized graphics based on OpenGL ES 2.0.
  • Advanced touch and gesture input.
  • Kernel support for 3 GB physical RAM and supports ARMv7 assembly.
  • the platform builder requires Microsoft Visual Studio 2008 with Service Pack 1 installed.
8.0Windows Embedded Compact 2013June 2013Mainstream Support ended on October 9, 2018, and Extended Support ended on October 10, 2023.
  • DHCPv6 client with stateful/stateless address configuration.55
  • L2TP/IPsec over IPv6 for VPN connectivity.56
  • Snapshot boot.57
  • Improved XAML data binding and Expression Blend support.58
  • OOM Model improvements from 7.59
  • HTML help viewer added.60
  • The previously default desktop shell has been eliminated.
  • the platform builder requires Microsoft Visual Studio 2012, 2013 or 2015 installed.

See also

References

  1. "Windows Embedded Homepage". Microsoft.com. Retrieved November 14, 2010. http://www.microsoft.com/windows/embedded/default.mspx ↩

  2. "How does Windows Embedded CE 6.0 Start?". Windows CE Base Team Blog. Microsoft. December 18, 2007. Archived from the original on July 8, 2010. Retrieved November 14, 2010. https://web.archive.org/web/20100708223127/http://blogs.msdn.com/b/ce_base/archive/2007/11/26/how-does-windows-embedded-ce-6.0-start_3f00_.aspx ↩

  3. "Board Support Package (Compact 2013)". MSDN. Microsoft. Retrieved July 15, 2013. http://msdn.microsoft.com/en-us/library/gg156127.aspx ↩

  4. "Product Lifecycles & Support for Windows Embedded Products". Microsoft. Archived from the original on April 10, 2015. https://web.archive.org/web/20150410235645/http://www.microsoft.com/windowsembedded/en-us/product-lifecycles.aspx ↩

  5. "Windows CE Migration FAQ". Microsoft. September 15, 2021. Archived from the original on October 22, 2021. https://learn.microsoft.com/windows/iot/windows_ce/windows-ce-migration-faq ↩

  6. Purdy, Kevin (October 30, 2023). "Windows CE, Microsoft's stunted middle child, reaches end of support at 26 years". Ars Technica. Retrieved January 10, 2024. https://arstechnica.com/gadgets/2023/10/windows-ce-microsofts-stunted-middle-child-reaches-end-of-support-at-26-years/2 ↩

  7. Proven, Liam (October 30, 2023). "Windows CE reaches end of life, if not end of sales". The Register. Retrieved January 10, 2024. https://www.theregister.com/2023/10/30/windows_ce_reaches_eol ↩

  8. "Create or Modify a BSP (Compact 2013)". Microsoft Developer Network. Microsoft. Retrieved June 11, 2014. http://msdn.microsoft.com/en-us/library/jj556177.aspx ↩

  9. "Priority Levels". Msdn.microsoft.com. April 8, 2010. Retrieved November 14, 2010. http://msdn.microsoft.com/en-us/library/bb202761.aspx ↩

  10. "Embedded Platform | Integrated Development Environment (IDE) | Windows CE". Microsoft.com. Retrieved November 14, 2010. http://www.microsoft.com/windowsembedded/en-us/products/windowsce/technical-specifications.mspx ↩

  11. https://download.microsoft.com/download/2/4/A/24A36661-A629-4CE6-A615-6B2910A1367A/BSP%20Porting%20Guide%20for%20Windows%20Embedded%20Compact%207.pdf https://download.microsoft.com/download/2/4/A/24A36661-A629-4CE6-A615-6B2910A1367A/BSP%20Porting%20Guide%20for%20Windows%20Embedded%20Compact%207.pdf ↩

  12. https://download.microsoft.com/download/F/D/D/FDDC7E09-3929-4E0D-B82F-1145D476ABB1/Webinar_Booting%20x86%20systems%20into%20Windows%20Embedded%20Compact%207.pdf https://download.microsoft.com/download/F/D/D/FDDC7E09-3929-4E0D-B82F-1145D476ABB1/Webinar_Booting%20x86%20systems%20into%20Windows%20Embedded%20Compact%207.pdf ↩

  13. https://download.microsoft.com/download/6/7/2/672327a4-cacd-4b9e-9c40-cb5223cb8f3d/wince_min_requirements_bsp.pdf https://download.microsoft.com/download/6/7/2/672327a4-cacd-4b9e-9c40-cb5223cb8f3d/wince_min_requirements_bsp.pdf ↩

  14. Douglas McConnaughey Boling (2001). Programming Microsoft Windows CE (2nd ed.). Microsoft Press. ISBN 978-0735614437. 978-0735614437 ↩

  15. "The Meaning of "CE" in Windows CE launch date". support.microsoft.com. February 14, 2015. Archived from the original on September 10, 2013. Retrieved February 14, 2015. https://web.archive.org/web/20130910113022/http://support.microsoft.com/kb/166915 ↩

  16. "Microsoft renames Windows CE, sets CE 6.0 launch date". windowsfordevices.com. September 22, 2006. Archived from the original on January 4, 2009. Retrieved July 20, 2011. https://web.archive.org/web/20090104153759/http://www.windowsfordevices.com/news/NS5452934855.html ↩

  17. "CNET: Windows CE to become 'Windows powered'". December 1999. https://www.itprotoday.com/windows-78/cnet-windows-ce-become-windows-powered ↩

  18. "IT Pro". Archived from the original on April 19, 2005. https://web.archive.org/web/20050419082235/http://www.windowsitpro.com/Article/ArticleID/19604/19604.html ↩

  19. "What's New (Compact 2013)". MSDN. Microsoft. Retrieved January 24, 2016. http://msdn.microsoft.com/en-us/library/gg154234.aspx#Anchor_0 ↩

  20. WinCE port Archived January 26, 2009, at the Wayback Machine - Lazarus wiki http://wiki.lazarus.freepascal.org/WinCE_port ↩

  21. "The CeGCC project: cross compile for Windows CE". Retrieved June 12, 2021. http://cegcc.sourceforge.net ↩

  22. "Choosing in which environment to develop". CeGcc. Retrieved June 12, 2021. http://cegcc.sourceforge.net/docs/choosing.html ↩

  23. Autohotkey build for CE devices http://www.autohotkey.net/~Micha/AutohotkeyCE/html/index.htm ↩

  24. Pöhls, Henrich C. (September 5, 2003), "Risk Analysis of Mobile Devices with Special Concern of Malware Contamination" (PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009 http://www.2000grad.com/papers/dpa_henrich_poehls.pdf ↩

  25. Smith, Tony (April 16, 2003). "Why Pocket PC isn't WinCE". The Register. Retrieved October 24, 2009. https://www.theregister.co.uk/2003/04/16/why_pocket_pc_isnt_wince ↩

  26. "Microsoft Announces Broad Availability of Handheld PCs With Windows CE". Microsoft News Center. November 18, 1996. Retrieved June 20, 2011. http://www.microsoft.com/presspass/press/1996/Nov96/wincepr.mspx ↩

  27. Hall, Mike (September 19, 2006). "Windows Embedded Blog: CE 6.0 - why the codename "Yamazaki" ?". MSDN Blogs. Retrieved October 24, 2009. http://blogs.msdn.com/mikehall/archive/2006/09/19/763146.aspx ↩

  28. Pöhls, Henrich C. (September 5, 2003), "Risk Analysis of Mobile Devices with Special Concern of Malware Contamination" (PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009 http://www.2000grad.com/papers/dpa_henrich_poehls.pdf ↩

  29. "Microsoft Announces Release of Windows CE 2.0". Microsoft News Center. September 29, 1997. Retrieved July 27, 2015. http://news.microsoft.com/1997/09/29/microsoft-announces-release-of-windows-ce-2-0 ↩

  30. Hall, Mike (September 19, 2006). "Windows Embedded Blog: CE 6.0 - why the codename "Yamazaki" ?". MSDN Blogs. Retrieved October 24, 2009. http://blogs.msdn.com/mikehall/archive/2006/09/19/763146.aspx ↩

  31. Pöhls, Henrich C. (September 5, 2003), "Risk Analysis of Mobile Devices with Special Concern of Malware Contamination" (PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009 http://www.2000grad.com/papers/dpa_henrich_poehls.pdf ↩

  32. "Microsoft Announces Availability of Windows CE 3.0". Microsoft News Center. June 15, 2000. Retrieved June 20, 2011. http://news.microsoft.com/2000/06/15/microsoft-announces-availability-of-windows-ce-3-0 ↩

  33. Hall, Mike (September 19, 2006). "Windows Embedded Blog: CE 6.0 - why the codename "Yamazaki" ?". MSDN Blogs. Retrieved October 24, 2009. http://blogs.msdn.com/mikehall/archive/2006/09/19/763146.aspx ↩

  34. Pöhls, Henrich C. (September 5, 2003), "Risk Analysis of Mobile Devices with Special Concern of Malware Contamination" (PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009 http://www.2000grad.com/papers/dpa_henrich_poehls.pdf ↩

  35. Pöhls, Henrich C. (September 5, 2003), "Risk Analysis of Mobile Devices with Special Concern of Malware Contamination" (PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009 http://www.2000grad.com/papers/dpa_henrich_poehls.pdf ↩

  36. Pöhls, Henrich C. (September 5, 2003), "Risk Analysis of Mobile Devices with Special Concern of Malware Contamination" (PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009 http://www.2000grad.com/papers/dpa_henrich_poehls.pdf ↩

  37. Pöhls, Henrich C. (September 5, 2003), "Risk Analysis of Mobile Devices with Special Concern of Malware Contamination" (PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009 http://www.2000grad.com/papers/dpa_henrich_poehls.pdf ↩

  38. "Microsoft Launches Windows CE .NET". Microsoft News Center. January 7, 2002. Retrieved June 20, 2011. http://www.microsoft.com/presspass/press/2002/jan02/01-07CENetLaunchPR.mspx ↩

  39. Hall, Mike (September 19, 2006). "Windows Embedded Blog: CE 6.0 - why the codename "Yamazaki" ?". MSDN Blogs. Retrieved October 24, 2009. http://blogs.msdn.com/mikehall/archive/2006/09/19/763146.aspx ↩

  40. Pöhls, Henrich C. (September 5, 2003), "Risk Analysis of Mobile Devices with Special Concern of Malware Contamination" (PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009 http://www.2000grad.com/papers/dpa_henrich_poehls.pdf ↩

  41. Pöhls, Henrich C. (September 5, 2003), "Risk Analysis of Mobile Devices with Special Concern of Malware Contamination" (PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009 http://www.2000grad.com/papers/dpa_henrich_poehls.pdf ↩

  42. Walker, Geoff (January 7, 2002). "Windows CE .Net: Microsoft's successor to Windows CE 3.0". Pen Computing Magazine. Retrieved October 24, 2009. http://www.pencomputing.com/WinCE/dotnet.html ↩

  43. Pöhls, Henrich C. (September 5, 2003), "Risk Analysis of Mobile Devices with Special Concern of Malware Contamination" (PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009 http://www.2000grad.com/papers/dpa_henrich_poehls.pdf ↩

  44. Hall, Mike (September 19, 2006). "Windows Embedded Blog: CE 6.0 - why the codename "Yamazaki" ?". MSDN Blogs. Retrieved October 24, 2009. http://blogs.msdn.com/mikehall/archive/2006/09/19/763146.aspx ↩

  45. Hall, Mike (September 19, 2006). "Windows Embedded Blog: CE 6.0 - why the codename "Yamazaki" ?". MSDN Blogs. Retrieved October 24, 2009. http://blogs.msdn.com/mikehall/archive/2006/09/19/763146.aspx ↩

  46. Smith, Tony (March 29, 2004). "MS readies WinCE 5.0 preview". The Register. Retrieved October 24, 2009. https://www.theregister.co.uk/2004/03/29/ms_readies_wince ↩

  47. Smith, Tony (March 29, 2004). "MS readies WinCE 5.0 preview". The Register. Retrieved October 24, 2009. https://www.theregister.co.uk/2004/03/29/ms_readies_wince ↩

  48. Smith, Tony (March 29, 2004). "MS readies WinCE 5.0 preview". The Register. Retrieved October 24, 2009. https://www.theregister.co.uk/2004/03/29/ms_readies_wince ↩

  49. "The History of the PDA". Archived from the original (DOC) on March 22, 2012. Retrieved May 17, 2009. 090517 seditaville.com https://web.archive.org/web/20120322204407/http://seditaville.com/academic/summary/The%20History%20of%20Microsoft%20Mobile%20OS(Ver%202).doc ↩

  50. Hall, Mike (September 19, 2006). "Windows Embedded Blog: CE 6.0 - why the codename "Yamazaki" ?". MSDN Blogs. Retrieved October 24, 2009. http://blogs.msdn.com/mikehall/archive/2006/09/19/763146.aspx ↩

  51. "Windows Embedded CE 6.0 Advanced Memory Management". October 10, 2013. Retrieved May 25, 2011 http://msdn.microsoft.com/en-us/library/bb331824.aspx ↩

  52. https://courses.washington.edu/cp105/_downloads/Windows_CE_Architecture.pdf; identical to https://download.microsoft.com/documents/australia/medc2006/windows_ce6_architecture_boling.ppt https://courses.washington.edu/cp105/_downloads/Windows_CE_Architecture.pdf ↩

  53. Leckie, Andrew (March 25, 2008). "Introduction to Microsoft embedded technologies - Session 1". New Zealand: Embedded .NET User Group. Archived from the original (PPT, 10 MB) on July 24, 2011. https://web.archive.org/web/20110724195514/http://www.embedded.net.nz/Presentations%20PPT%20%20PDF/Embedded%20Introduction%20-%20Session%201.ppt ↩

  54. Babu, K. Ashok (November 22, 2006). "Differences between Windows CE 5.0 and Windows CE 6.0". WindowsForDevices.com. Archived from the original on July 16, 2012. Retrieved October 24, 2009. https://web.archive.org/web/20120716194951/http://www.windowsfordevices.com/c/a/Windows-For-Devices-Articles/Differences-between-Windows-CE-50-and-Windows-CE-60 ↩

  55. "What's New (Compact 2013)". MSDN. Microsoft. Retrieved July 15, 2013. http://msdn.microsoft.com/en-us/library/gg154234.aspx ↩

  56. "What's New (Compact 2013)". MSDN. Microsoft. Retrieved July 15, 2013. http://msdn.microsoft.com/en-us/library/gg154234.aspx ↩

  57. "What's New (Compact 2013)". MSDN. Microsoft. Retrieved July 15, 2013. http://msdn.microsoft.com/en-us/library/gg154234.aspx ↩

  58. "What's New (Compact 2013)". MSDN. Microsoft. Retrieved July 15, 2013. http://msdn.microsoft.com/en-us/library/gg154234.aspx ↩

  59. "What's New (Compact 2013)". MSDN. Microsoft. Retrieved July 15, 2013. http://msdn.microsoft.com/en-us/library/gg154234.aspx ↩

  60. "What's New (Compact 2013)". MSDN. Microsoft. Retrieved July 15, 2013. http://msdn.microsoft.com/en-us/library/gg154234.aspx ↩