Posted By J.T. Kimbell Program Manager
Here on the Windows Embedded team, we try to do more than just build software, we also “eat our own dog food” and use our software for our everyday work and to emulate possible customer scenarios. Today I wanted to share with you the first post of a small series about how one of our testers is feasting on the dog food…and loving it.
This post was written by me (J.T.), but all the hard work was done by Tien Do, a Software Development Engineer in Test on the Windows Embedded team. Tien is currently working on the Embedded OEM Tools team, which focuses on the embedded developer’s end-to-end scenarios. Before joining the Windows Embedded team, he worked on the Windows Fundamentals team, and before working for Microsoft he worked as a firmware developer for a company in the San Francisco bay area. In his spare time, he enjoys hiking, sightseeing and driving on long trips.
Tien took up this work for the same reason that many of us take the time to build something on top of Windows Embedded: to put ourselves in the shoes of our customers and understand the end-to-end experience of creating a specialized device. Tien also hoped to find bugs in our product and to be able to create some guidance and a template for other people in our team and for you, the Windows Embedded customer.
To do this, Tien had to take several steps. Some of them may be familiar or the way that you would do things, and some of them may be new or different. However, we hope that showing this process to you will make development on Windows Embedded Standard easier.
For the purposes of this exercise, Tien chose to create a device running WinTV7, because it would be an interesting type of device to have running in his office.
Comments Windows Embedded Standard
Posted By The Embedded Ninja
More and more frequently corporate users are finding themselves in need of a robust management solution for their Intelligent Systems. For example, managing thin client devices to ensure the right VDI or Citrix experience is becoming paramount. In terms of POS devices or interactive kiosks that take payment, managing software updates is a bar of entry for doing business in the world of PCI. And for other devices like those in an industrial scenario, keeping track of the “shift and drift” of an intelligent system ensures quality across the board.
For all of those scenarios and more, the newest System Center release offers a brilliant upside: It does away with the need for extra software to manage all kinds of embedded devices. Ben Smith, one of our Embedded Ninjas, offers a quick overview embedded-specific enhancements coming in Service Pack 1.
Many of the large enterprises we work with have implemented Windows Embedded Device Manager 2011 on top of System Center Configuration Manager 2007 to manage embedded devices. As you may have seen in the earlier System Center 2012 SP1 blog, with Service Pack 1, the capabilities of System Center 2012 Configuration Manager will be extended to manage Windows Embedded-based thin clients, Point-of-Sale (POS) terminals, digital signage, kiosks, and others. This functionality means devices other than servers, desktops, and laptops can be managed by System Center 2012 Configuration Manager SP1 without requiring any additional software.
Comments Intelligent Systems
Remote Desktop Connection 8 Client update for Windows Embedded Standard 7 SP1 and Windows Embedded POSReady 7 is now available on ECE.
This update enables users using Windows Embedded Standard 7 SP1 and Windows Embedded POSReady 7 devices to connect to computers running Windows Server 2012 or Windows 8, and experience the rich user experience delivered by RemoteFX and RDP 8.0.
For more information on the RDP 8.0 update for Windows Embedded Standard 7 SP1, please visit the Remote Desktop Services blog.
Comments Product Updates
Posted By David CampbellProgram Manager
As the Windows Embedded Compact v.Next launch approaches, we will soon be posting detailed information about the Compact OS and tools, both Platform Builder (used for Board Support Packages (BSPs) as well as drivers) and the use of Visual Studio itself for developing applications on top of Compact OS images. I’m looking forward to making more of the technical details of the release available, probably in small bits until we can go fully public, which will happen very soon.
In the meantime let’s take a detailed look at the CEPC BSP. Here’s a guest post by Doug Boling again with a great overview based on his recent webcast. (More details on Doug’s webcast series are provided at the end of the article.)
The CEPC board support package (BSP) in Windows Embedded Compact 7 is one of the frequently used BSPs in Platform Builder. Unfortunately it is also one of the more difficult to customize. It may seem strange to customize a BSP that runs on a generic PC chassis but when used on a production embedded system, some form of customization such as splash screens or subtle changes in hardware is almost always necessary.
The difficulty in customizing the CEPC BSP comes from its file structure. Before I can explain the problem, I need to discuss the architecture of a standard Windows Embedded Compact BSP
Comments Windows Embedded Compact
The October 2012 Security Updates are now available on the ECE for Microsoft® Windows® XP Embedded with Service Pack 3 and Windows® Embedded Standard 2009.
The list below applies to both XPE SP3 and Standard 2009: