Posted By Kevin DallasGeneral Manager
Our growing enthusiasm over the last few months is undeniable. The convergence of cloud-based services, data centers, pervasive connectivity and specialized devices has led to the emergence of a new category within the traditional embedded market – a category that is exponentially greater than the sum of the parts.
We identified this emerging category as intelligent systems and together with IDC and Intel we’ve been talking about the impact it’s already having across industries, businesses, and ultimately, end users.
Microsoft laid out its roadmap for intelligent systems in the fall of last year. As we move forward, we want to engage with you to discuss how intelligent systems are taking shape and where the challenges and opportunities are for the market.
With this new blog we’re taking a more ‘intelligent’ approach to the conversation, providing you with one place to read about Microsoft’s evolving strategy for intelligent systems and to hear commentary and encourage discussion with members of our global engineer and marketing teams. You can expect to learn more about subjects ranging from our current products, to updates and those still in development. We’ll also discuss emerging trends, industry sectors and other timely topics. I’m especially excited to see some of the growth that’s taking place in the automotive space, as outlined by Ford technical fellow Jim Buczkowski. (And when you have a chance, take a look at these articles on the growth of intelligent systems and how we’re helping retailers transform the shopping experience.)
Comments Windows Embedded Standard
Posted By J.T. KimbellProgram Manager
Welcome to the new Approaching Embedded Intelligently blog! I’m J.T. Kimbell, a Program Manager in Windows Embedded, and I’ll be providing you with tips, insights, and cool projects related to the Windows Embedded Standard line of products. While at work I spend most of my time focused on enabling the servicing of Windows Embedded Standard 8 devices and the Embedded Core, but I’ll dabble in drivers and other areas from time-to-time. I’ve been on the Windows Embedded team for nearly 3 years after graduating from the University of Iowa. When not working I enjoy sports of all kind (but primarily football, soccer, and basketball), reading books, playing video & board games, and spending quality time with my wife and young daughter.
This first post is about some PowerToys made for Windows Embedded Standard 7, but I deserve none of the credit for making it happen. Package Mapper and Answer File Diff were made by Saravanan Somasundaram, a Software Development Engineering on the Windows Embedded team.
PowerToy is kind of a funny name, isn’t it? I’m still not completely sure why we call them that, but Wikipedia tells me that they are programs released by Microsoft that are “not under technical support because they do not undergo the same rigorous testing that the operating system components do.” These applications are officially unsupported, but they represent tools that we used internally to do our work and we wanted our customers to be able to reap the benefits of these tools as well.
We created the Package Mapper and Answer File Diff tools to help us create application templates. Package Mapper helps speed up development time, and Answer File Diff is very useful when testing a template. Because these tools were quite helpful to us, we felt that they would also help community members analyzing dependencies to their applications and we decided to share them as PowerToys.
Posted By David CampbellProgram Manager
Welcome to the “new and improved” :) Windows Embedded Compact blog! This is part of our new, consolidated Approaching Embedded Intelligently blog effort to provide updated content, consolidate existing content, feature guest bloggers and, most importantly, provide a common place to get updated information.
As a quick introduction, I’m David Campbell; I’m a Program Manager (PM) on the Windows Embedded Compact team. I’ve been involved with Windows Embedded Compact/Windows CE since Windows CE 1.0 as a PM. Over the years I’ve been responsible for a variety of technologies, and most recently I’ve been driving the overall releases.
The Windows Embedded Compact team’s mission has evolved over the years, but a large portion of our mission and goals remain the same. We continue to provide a Microsoft OS solution for high volume, small footprint, real-time devices. An OS that is stable & reliable, with a long support cycle and ideal for high availability devices. Windows Embedded Compact fits into Microsoft’s overall offerings with its APIs and tools aligning with Windows to provide a familiar development experience right out of the box.
There have been a number of great bloggers for Compact over the years and I encourage you to read them, including Olivier Bloch, Sue Loh, Steve Maillet, Mike Hall, and Doug Boling to name a few. While some of our bloggers haven’t posted in a while, much of the information remains relevant; this is a testament to the stability and longevity of the Compact product. It also shows how dispersed the information is, which is something we’ll try to improve with these articles.
Comments Windows Embedded Compact
Posted By Mark PendergrastSenior Product Manager
Let’s face reality. For our customers and partners, every day comes with lots of choices – from deciding on which component to use for their motherboard, to what application to build/deploy, to which markets and opportunities to pursue to build their business. It’s no different in picking which operating system to use for their specialized device. There’s a rich selection of alternatives from which to pick, including many flavors of Linux, Google’s Android, and of course our broad set of options in the Windows Embedded family. However, like many things in business, this preponderance of choice offers both opportunities and also challenges for the market. On the one hand, it gives customers and partners many options from which to pick and choose for their specific needs, but it can also be overwhelming. Making a poor choice could add cost, delays, and complications that hadn’t been anticipated.
It’s in this light that I hope to provide some value from The Compete Corner here on the Windows Embedded blog. As the compete lead for the organization, my role is to ensure that our customers, partners and internal teams have the full and accurate picture on the value of the Windows Embedded solutions and help them make good decisions with Windows Embedded as their OS choice. And of course all of this in interest of spurring healthy competition.
Posted By Pavel BanskyProgram Manager
Good morning [place your current location here] and welcome to Approaching Embedded Intelligently. My name is Pavel Bansky and I work as a Program Manager in Windows Embedded team. I will be writing posts not only about Windows Embedded Device Manager but also other cool stuff we are doing here in Windows Embedded. Let me start with this Q&A article and stay tuned for more.
Windows Embedded Device Manager 2011 has been available on the market for about a year now. As the number of potential or actual users is increasing, there is a set of frequently asked questions that I hear. Let me go through the top ten of these questions in this article.