Windows Embedded: FAQS
What is Microsoft Windows Embedded?
Windows Embedded is a family of operating system software and tool sets from Microsoft for use in computer devices such as cash registers, automated teller machines (ATMs), industrial controllers, gateways, Internet Protocol (IP) telephones, server appliances, Windows-based thin clients, advanced consumer electronics, and specialized handheld devices.
The Windows Embedded family of products includes leading operating systems Windows Embedded CE and Windows XP Embedded, which include technologies and tools that enable developers to create embedded devices for a broad range of demanding environments. Microsoft also provides Windows Embedded for Point of Service (WEPOS), to help developers of retail devices accelerate their time to market.
What is embedded computing?
Typically, embedded computing refers to any computer system or computing device that performs a dedicated function or is designed for use with a specific embedded software application. These are systems that the end user typically cannot modify.
What is distinct about an embedded operating system?
Embedded operating systems are usually highly customized for a specific task or function. They may be optimized for specialized hardware or a specific application. Since the configuration can be "locked down" and therefore rigorously tested, manufacturers of these systems can control costs and deliver highly reliable devices optimized for specialized tasks.
What are the differences between the Windows Embedded operating systems?
Windows Embedded CE integrates reliable real-time capabilities with advanced Windows technologies to help you rapidly build a wide range of innovative, small-footprint devices. Windows Embedded CE can run on multiple CPUs and is used in a broad range of device types including: mobile handhelds, thin clients, gateways, IP telephones, and automated industrial devices.
Windows XP Embedded delivers the complete power of Microsoft Windows in componentized form to rapidly build reliable and advanced embedded devices based on the x86 processor and PC architecture hardware. Examples of Windows XP Embedded devices include retail point-of-service (POS) devices, ATMs, Windows-based thin clients, and advanced set-top boxes. For more information, read How to Choose a Windows Embedded Operating System.
What is the difference between Windows, Windows XP, Windows XP Embedded, and Windows Embedded?
The term Windows includes a broad range of Microsoft technologies and products and is often used to refer to the desktop operating system. Windows XP is the latest desktop operating-system software and is available in multiple versions for business and home users. The term Windows Embedded refers to the Microsoft family of embedded operating systems for smart, connected, and small- or reduced-footprint devices. The Windows Embedded family includes a range of products all based on the Windows Embedded CE and Windows XP Embedded platforms.
Windows XP Embedded is a specialized operating system, consisting of componentized Windows XP Professional features and an end-to-end set of development tools, for use in non-personal computer (non-desktop) devices. Windows XP Embedded is typically used by embedded developers, system integrators, and Original Equipment Manufacturers (OEMs).
What is the difference between Windows Embedded CE and Windows Mobile-based Smartphone and Pocket PC software?
Windows Embedded CE is a customizable, embedded operating system for a variety of small-footprint devices. OEMs can use Windows Embedded CE to design platforms and customize applications to maximize the user experience for devices such as handhelds, thin clients, logic controllers, and advanced consumer electronics.
Windows Mobile is a complete software platform built on Windows Embedded CE. Unlike Windows Embedded CE, the Windows Mobile Smartphone and Pocket PC operating systems are specifically designed for devices that require a specialized hardware configuration. The software includes standardized interfaces and applications that ensure compatibility across hardware designs. For more information, visit the Windows Mobile Web site.
Windows Automotive is based on the Windows Embedded CE real-time embedded operating system. While it shares the rich platform and services of Windows Embedded CE, Windows Automotive enables features such as voice recognition technology, automotive power management, and other automotive-specific options. To learn more, visit the Windows Automotive Web site.
What is Windows Embedded for Point of Service?
In October 2004, Microsoft announced the development of a standard, retail-optimized operating system platform designed for retail point-of-service systems—Windows Embedded for Point of Service. Based on the technologies available in Windows XP Embedded with Service Pack 2, Windows Embedded for Point of Service enables the Microsoft Smarter Retail Initiative and is an easy-to-use point-of-service platform optimized for the retail industry.
What other vertical market solutions are based on Windows Embedded?
Windows Automotive is based on the Windows Embedded CE real-time embedded operating system. While it shares the rich platform for dynamic applications and services of the Windows Embedded CE operating system, Windows Automotive enables features such as voice recognition technology, automotive power management, and other automotive-specific options. To learn more, visit the Windows Automotive Web site.
The latest version of Windows Embedded CE includes an integrated, easy-to-use Telephony User Interface (TUI), a VoIP Application Interface Layer (VAIL) with extensive call control functionality, an interface to access contact and calendar data on Microsoft Exchange servers, advanced provisioning capabilities, and a complete network layer stack that facilitates VoIP-enabled device development and infrastructure integration. Learn more about the Windows Embedded CE VoIP device platform and other vertical markets; medical devices, gateways, and more at the MSDN Windows Embedded Developer Center.
How do I purchase the Windows Embedded operating systems?
There are two steps to licensing the Windows Embedded operating systems: purchasing the appropriate toolkit with a development license to begin building your device image, and purchasing a runtime license for each device that you will distribute or sell that contains that image. These licenses are typically sold through Microsoft Embedded Authorized Distributors who can give you more information about licensing.
How much does the Windows Embedded software cost?
The development tools with development license for any one of the Windows embedded operating systems are available for $995 U.S. The cost for each runtime license may vary, based on the volume of licenses that you purchase over a given period of time. For information about how to buy Windows Embedded products and licenses, please see the License and Ship page.
Can I try Windows Embedded software before I buy it?
Yes. You can download or order evaluation versions of Windows Embedded from the Windows Embedded OS Trial site. Software licenses are valid for 120 days from the date of installation.
How does Windows Embedded CE relate to .NET?
Microsoft .NET is a set of Microsoft software technologies for connecting your world of information, people, systems, and devices. It enables an unprecedented level of software integration through the use of XML Web services: small, discrete, building-block applications that connect to each other as well as to other, larger applications via the Internet. Windows Embedded CE includes components that use or enable .NET technologies, such as XML Web Services, Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL), and the .NET Compact Framework.
More information can be found here (https://www.microsoft.com/windows/embedded/plan_faq.mspx).
Comments
Anonymous
October 04, 2007
PingBack from http://msdnrss.thecoderblogs.com/2007/10/04/windows-embedded-faqs/Anonymous
October 04, 2007
PingBack from http://msdnrss.thecoderblogs.com/2007/10/04/windows-embedded-faqs/Anonymous
November 03, 2008
Our company, Medtronics, is developing a medical device on an i.MX31 processor based h/w platform with Windows embedded CE 6.0. The application/s are written primarily in C#. We are looking at deploying the CE 6.0 Core licensing model. My question is, if we use .NET CF 3.5 on the device as against .NET CF 2.0, would that make a differece to the CE licensing model? Thanks, Sebastian Nonis Medtronic MiniMed email: sebastian.nonis@medtronic.comAnonymous
November 30, 2008
Thanks for the post and really good job Vijay --PremalAnonymous
January 05, 2012
Is their a way to differentiate an MSDN installer with embedded license withouth having to install and test?Anonymous
October 22, 2012
All FAQs are for the developers and I Looked this for one of our product developement and seems to me that it was very attractive. I have convinced every body to develop an Instrument in WindowsCE. The cost was $3 per Instrument with .net and full microsoft Support. Now the instrument is in the customer site and time to updgrade the software. The fun begins here. We produce NK.BIN with application + OS and used custom loader, custom boards and our own bsp.
- We couldn't realy distribute the software because of the Microsoft licensing contracts. To produce a USB stick with Nk.BIN (which is consider to me is Firmware) needs a Microsoft duplicator and which we e cannot contact Microsoft Duplicator Directly. We have to Contact through the Distributor.
- We though we could produce interannly and service personal can do this by visiting the customer site- Cannot do this either. Neet to serialize and Microsoft approved art work with Readonly USB Sticks. The doesn't make sense part is Customer can download the image and create a usb with out breaking the licensing agreements, then customer can update the system by using this usb. Again customer cannot give this usb to service. Ours is Medical device and need to do meet all the standards and calibrations. The conclusion is Windows CE is good but pain the time of Update. So I will not ever consider another product with Microsoft embedded systems. So please read carefully about the licensing about how to update the system in Future. Looks like Microsoft trust end users and they can do what ever they want but not the Enterprise. It is been like this meetings and after meetings try to find a way to update our instruments in the fields. This is what Microsoft Blackbelt and Arrow Distributor says.