Posted By Chris ElliottSenior Marketing Communications Manager
This week, we joined Ford at gdgt Live New York where more than 1,500 gadget geeks streamed into Chelsea’s Altman Building to see the latest and greatest consumer technology. Many of them ended up planted in one of the brand-new Ford Focus Electrics to get a hands-on demo of Ford SYNC with MyFord Touch.
Many of the new gadgets I saw were designed for mobile devices. Phone covers, portable hard drives and headphones seemed to get the most attention. But what was really noticeable during the conversations I had was that people are still actively looking for ways to efficiently consume media. The portable consumption of news, video and other content appears to be a significant trend for a long time.
One key statement we heard over and over again was that people just want their device to work in the vehicle. Since SYNC is developed on the Windows Embedded Automotive software platform, there’s no need to worry about a specific device pairing with SYNC or it seamlessly integrating with the car. Part of what makes SYNC so great is that it welcomes most mobile devices into the vehicle—whether it’s today’s newest smartphone or that flip-phone from years past that some folks just can’t live without. Once you’ve paired your mobile device, Ford SYNC will remember that device. Every time you enter the car, it automatically connects. So even if you’ve left the phone in the trunk, it can still pair up.
Comments Windows Embedded Automotive
Posted By J.T. KimbellProgram Manager
As you may have noticed from our Community Technology Previews for Windows Embedded Standard 8, there have been some tweaks to how various technologies are represented and grouped in our toolkits, and they are not just cosmetic changes. Windows Embedded Standard 8 introduces the concept of modules, replacing the packages that were in Windows Embedded Standard 7 and providing more flexibility and enhanced functionality. In this post, Dave Massy gives an overview of modules and how they will change your development experience in Windows Embedded Standard 8. Dave is a Program Manager working on the componentization team of Windows Embedded. When not spending time with his young son and daughter, he enjoys driving his 1958 Jaguar XK 150 around the Puget Sound area. Additionally, Dave derives great pleasure from replacing any Z he finds with the letter S to properly conform to the Queen’s English.
In Windows Embedded Standard 8 there are subtle changes from Windows Embedded Standard 7 in how we expose individual technologies as building blocks for creating your OS These building blocks allow you to create an OS image that matches your needs and not include functionality you do not need.
In Windows Embedded Standard 7 we referred to the building blocks of the OS as packages. In Windows Embedded Standard 8, they are modules. Packages and modules may seem similar because you use them to build up a functional image. However, under the hood there are technical differences that allow us to improve the overall experience of using the catalog and defining an image that meets your needs. For instance, one of the key advantages is that third-party modules can be in the catalog alongside OS modules. You can even create your own modules using the Module Designer tool that is included in the Windows Embedded Standard 8 toolkit.
Comments Windows Embedded Standard
This is the last entry in this week’s series about the lockdown features found in Windows Embedded Standard 8. In this post Brendan Rempel goes into more depth about how to manage your lockdown features. Brendan is a Software Development Engineer who works on a variety of Windows Embedded device lockdown features. Outside of Embedded, Brendan spends all remaining time with his family, fueling two boys’ obsessions with loud toys, especially the Washington State’s steam trains and model rockets.
But before Brendan gets into the meat of this article, he’s got a story to share.
A while back I had nifty a car alarm. It had all the typical features for preventing theft and even had an engine starter. But the best part was the remote. It had a little picture of a car and realistic LCD indicators to represent its state. I could press a button to see if the doors were locked and lock them if they weren’t. It could tell me if the engine was started correctly. It would also beep loudly if someone tried to break in. Best of all, it had a ¼ mile range and worked even when in deep underground parking. While it didn’t stop break-in attempts, I was able to respond fast when someone did and never worried about the car being secure.
Windows Embedded Standard 8 introduces many new and improved features related to securing devices and maintaining their primary purpose. We’ve also added consistent user interface through the MMC and a consistent set of WMI providers for easy scripting. This was all meant to help administrators manage devices, regardless of how that’s done.
Using history as our teacher, we learned that many Lockdown related problems in devices go undetected. It’s easy to remember being at an airport, freeway, or game and see a digital sign showing a Windows error message or logon screen. This is as embarrassing to us as it is for the person who made the device, but often only the public knows when this happens. This is why we’ve done our best to stop these problems, but we’ve added several new features to help administrators detect when problems sneak through and record when we succeed.
All our features use the Event Tracing for Windows (ETW) to report problems in their typical scenarios. This includes:
Posted By Robert Peterson Sr. Product Manager
Welcome to the ‘new’ Windows Embedded Products and Services section of the Windows Embedded team blog.
As a quick introduction, I’m Robert Peterson, Sr. Product Manager in the Windows Embedded team. My team focuses on bringing new products and services to market around the world. This blog will cover the many ways our products and services are in the market.
Air travel can be great, well I am told it can be, and most of us have favorite stories about going through airports. Like you I often get frustrated at long lines and delays and try to avoid them. I thought about how I could have less hassle and realized there are lots of devices that make getting in and out of the airport so much smoother that we don’t even think about. On my last trip I decided to calculate how much time all those devices could save me:
I needed to check in (yes, I could have done this online but that would ruin the story); I used a Kiosk to check in at the entry of the airport as the lines were longer with the agents. If this Kiosk wasn’t working it would have taken me another 10 minutes to check in. Time saved: 10 min
Today I’m going to share a demo of something pretty awesome with you guys. Not as awesome as the recently announced Microsoft Surface tablet, but it’s still pretty cool. On Monday, we gave an overview of all the lockdown features on Windows Embedded Standard 8, and today I’m going to be showing you how you can easily manage those lockdown features by using the Unified Configuration Tool (UCT), a Microsoft Management Console (MMC) snap-in.
UCT comes as part of the Windows Embedded Standard 8 toolkit and can be installed by running emblockSetup_amd64.msi or embblockSetup_x86.msi (depending on your developer machine’s architecture). Download our second Community Technology Preview (CTP2) to try it out. With the tool, the lockdown features on your Windows Embedded devices can be remotely or locally managed by graphical user interface. From changing your custom shell for Shell Launcher to selecting what processes to block with Dialog Filter, there is a lot that UCT lets you configure.
With some help from Brendan Rempel, a developer working on UCT, I created the following video that shows you UCT in action and teaches you more about it.