Posted By J.T. KimbellProgram Manager
A few years ago on our old blog, I posted to let everyone know about a PowerToy we released called CBS Package Inspector. With our new blog up and a new audience, I wanted to spend a bit of time highlighting that tool again.
CBS Package Inspector was created by Anup Vasudeva Rao, a software development engineer, and released shortly after the release of Windows Embedded Standard 7 with the purpose of allowing Windows Embedded developers to better understand the contents of the packages they are installing on the system. How does it do this? By providing the ability to crack open and peek inside .cab or .msu files, showing their contents.
“Great!” you may say, but what exactly does that mean? Good question, and luckily for you, I’m prepared to divulge some of those details.
Comments Windows Embedded Standard
Posted By Windows Embedded Team
On Windows Embedded 8 Standard, if you attempt to use WEDU to search for updates and the scan fails with the following error in the log (wedu.log):
Application Version: 126.96.36.199
=== EXCEPTION ===System.Runtime.InteropServices.COMException (0x8024002E): Exception from HRESULT: 0x8024002E at WUApiLib.IUpdateSearcher.BeginSearch(String criteria, Object onCompleted, Object state) at Microsoft.Wedu.Mu.UpdateTarget.CreateScanJob(IAsyncResult ar, Func`1& IsCompleted, Func`1& AsyncState, Func`1& CompletedSynchronously) at Microsoft.Wedu.Mu.AsyncResultAdapter..ctor(AsyncCallback outerCallback, Object outerState, JobCreateDelegate innerResultFunc, AsyncCallback innerCallback) at Microsoft.Wedu.Mu.UpdateTarget.<DoScan>d__3.MoveNext()
The most common cause of this error is the presence of the following registry key with a value other than 0:
The workaround for this error is to either delete this registry key or set the value to 0.
Comments Product Updates
Posted By Jeff WettlauferTechnical Program Manager
When we talk about Intelligent Systems, we speak about connecting sensors and smart devices through intuitive applications to cloud services. Whether this fabric is lowering the cost of manufacturing for your next car, helping your family doctor prescribe you the right medicine, or making your next shopping experience better, Microsoft technology is in the DNA of the effort. Sometimes, it even effects your day out at the ballpark.
Most of us think of pro sports stadium experiences from our childhood. Mine was in Edmonton watching the Oilers of the 80’s in mullets and tube skates. The arena was loud. We kept up with the game using a hard copy program in our laps and the few light bulb boards around the rink that showed the score, some out of town info every now and then but not much more. Not much technology in place. Anywhere.
Today’s kids have it a little different. With the kids back in school, those warm summer nights slowly disappearing into cooler evenings and the trees changing color, our thoughts turn to the autumn. Football coverage takes over the TV networks, and the baseball season heads for the playoffs.
Comments Intelligent Systems
The December 2013 Toolkit Update for Windows Embedded Standard 7 is now available on MyOEM.
This update includes bug fixes and improvements for the Image Configuration Tool (ICE).
If you have questions on accessing MyOEM, please email the OEM Customer Communications Care Team at OEM@microsoft.com.
One of the biggest changes between our Windows Embedded Standard 2009 (XP Embedded) and Windows Embedded Standard 2011 tools is the concept of image building. In Windows Embedded Standard 2009, components were selected in Target Designer and images assembled on the developer machine, after which it had to be transferred to the target device. In Windows Embedded Standard 2011, images are now built directly on the device using our Image Based Wizard (IBW) which can be configured “on the fly” using the wizard interface, or by using a preconfigured answer file. Each method has its own pros and cons, and while I won’t go into them, there certain applications and scenarios where it is still advantageous to be able to build images offline.
This article goes over the steps for assembling a Windows Embedded Standard 2011 image with the desired feature sets, using only the tools found on your developer machine. This method can save a lot of time and also utilize less memory on the target, if you have to build & deploy your images on a resource constrained devices. As an example, we found that the time taken for building and deploying a MaxBoot image on a target device with 2 Ghz machine w/ 1gig of ram can be cut from 30 minutes to 15 minutes. The time savings only get greater for target devices with more limited resources. Note: This does not include the time taken to offline-build the image as those times can vary significantly depending on the configuration of the developer machine.
Before I proceed further, please note that this method for building images is not a perfect substitute for building images using the IBW. Not all image configurations can be built using this method, and I’ll call out what developers should be aware of as we proceed through the steps.