Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
**Updated 3/26/09 with preface
[The following article is authored by one of the Windows Embedded MVPs (Most Valuable Professionals). Our MVPs have a heavy background in Embedded systems and are a great repository of information on Windows Embedded products. We’re providing this space on our team blog as a service to our readers by allowing MVPs to share some of their knowledge with the rest of the community.]
Windows Embedded Standard does not normally require too much troubleshooting, because the boot process is exactly the same as in XP Professional. But, according to Murphy’s Law, something will go wrong, no matter how the small the chance is. This post will try to give an overview of the most common reasons for failure and the ways to resolve them.
Posted By Barb EdsonGeneral Manager, Marketing and Business Development
This week in New York, we’re rolling out the newest member of our Windows Embedded family, and it’s a complete re-imagining of what an enterprise mobile device should be. D’Arcy Salzmann, senior product manager for Windows Embedded 8 Handheld, has details.
At the end of 2011, Kevin Dallas, general manager of Windows Embedded, shared with our customers and partners that the next generation of Windows Embedded Handheld would be based on Windows 8 technology. This past October, we provided more details when we published our updated Windows Embedded road map, noting that the new platform is built on Windows Phone 8 and would be called Windows Embedded 8 Handheld, and we promised that more details would be available in January.
Today at the National Retail Federation (NRF) Annual Convention & EXPO, our team is taking the covers off of Windows Embedded 8 Handheld, introducing our device hardware partners, and showcasing the next generation of mobile line-of-business application experiences with one of our launch customers, showing how Windows Embedded 8 Handheld devices help them deliver on the promise of intelligent systems.
Microsoft and mobile devices for industry have a long and successful history together. Starting with Windows CE, Windows Mobile and Windows Embedded Handheld 6.5, Microsoft mobile platforms today power mobile devices in all industries, helping businesses and governments deliver secure mobile productivity in stores, warehouses, delivery fleets, ports, hospitals, and airplanes. Devices from Microsoft’s hardware partners ensure customers have durable, secure, and reliable connectivity to enterprise systems, allowing them focus on their business, whether inside their showrooms, on the road, at the jobsite or at their customers.
Comments Intelligent Systems
Posted By David CampbellProgram Manager
At the recent Visual Studio launch event, it was confirmed that Visual Studio 2012 will once again include support for Windows Embedded Compact. Included in that support we’re targeting much of the newest compiler and tools functionality, most notable of which includes new compiler features such as C++11 language standards, faster more efficient code generated, an updated CRT, auto-parallelization and auto-vectorization (Wow, that’s a mouthful.), range based loops, RValue references, and more. Also included will be an updated version of .net CF which has greatly improved performance, particularly around memory allocation and garbage collection - using the “generational” garbage collector. This not only provides more performance, but more predictability in the execution of applications.
More information about the new Visual Studio, including support for Compact, can be found at the Visual Studio Launch site. (Yes, I’m in the video and no, I’m not going to be able to make a living in front of the camera. But it’s the message that’s important here.)
Be sure to check back in the future as we release more information on the upcoming Windows Embedded Compact release.
Comments Windows Embedded Compact
Posted By Jeff WettlauferSr. Technical Product Marketing Manager
Hi everyone. Last week, we achieved a major milestone within the Windows teams: the RTM of Windows 8.1 for both Windows and Windows Embedded platforms. In this post, I would like to share with you some technical highlights with the new release of Windows Embedded 8.1 Industry, and talk about some of the key elements that are new from a technical perspective.
It is important to first note a big change for Windows Embedded: In the past, the Embedded versions of Windows, right up to the 8 wave, were released a short period of time after the RTM of Windows Client. With the release of 8.1, Windows Embedded is aligned at an engineering level that not only effects timing of release, but the code base. Windows Embedded 8.1 is now built fully on Windows Client with Embedded features added (think of Embedded as a superset of capabilities over Client), and also on the same dates.
This alignment spans several levels of the stack. The hardware and OS stack are much more closely aligned than ever before, bringing better consistency for drivers and chipsets. Above the OS stack, we have integration with other infrastructure, such as identity (think AD) and development, deployment and management tools (Visual Studio x, System Center, Windows ADK and more) and at an app layer (with some API support for modern apps and industry specific peripherals). Finally, this alignment is more cloud-enabled than ever before, supporting smart, connected scenarios and services for edge devices.
Comments Product Updates
Posted By J.T. KimbellProgram Manager
Over the next week we’re going to have a small series highlighting various Lockdown features on Windows Embedded Standard 8. In this first post Kevin Asgari gives us an overview of the Lockdown and Branding features found in Windows Embedded Standard 8. Kevin is a Writer for the Windows Embedded team and in his spare time enjoys reading, skiing, visiting wineries, and spending time with family.
Windows Embedded Standard provides a building block version of the Windows operating system, enabling you to create a smaller, customized version of Windows by removing functionality that your device does not need. In addition, Windows Embedded Standard provides additional functionality for embedded devices that is not available in the full Windows OS. In Windows Embedded Standard 7 and earlier, we called these new features “embedded enabling features”, or EEFs for short.
However, “embedded enabling features” is not a very descriptive term. In Windows Embedded Standard 8, we now call these features lockdown and branding features.
Lockdown features enable you to provide a controlled device experience, mainly by limiting the ways in which an end user can interact with the device. For example, your device may be a dedicated cashier device that runs a full screen cashier application, and you may want to prevent users from being able to use Windows shortcut keys like Alt+Tab to switch out of the application, or Alt+4 to close the application.
Branding features enable you to hide or change many of the parts of the OS that identify it as a Windows product. You may want the devices your company produces to show only your company’s branding to your customers for better brand recognition, or you may want to hide the underlying OS so that end users are less likely to try to break out of the tailored device experience.
Comments Windows Embedded Standard