Microsoft
Windows Embedded Home
Intelligent Systems
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
Resources
[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.]
Componentizing drivers or applications is always a challenge in a Windows Embedded Standard 2009 project. In some cases components are created easily with the help of the import function in Component Designer, which enables the import of the hardware detection result file (.pmq) from Target Analyzer, setup information files (.inf) used for driver installations or registry export files (.reg) created by Regedit.exe.
Read More...
Comments Product Updates
**Updated 3/26/09 with preface
Quite often, achieving a desired network configuration can be challenging for Windows Embedded Standard 2009 devices. This is especially true if one is not using the default DHCP setting, which always works well.
Devices built with Windows Embedded Standard 2009 are able to offer sophisticated security mechanisms that integrate well in Enterprise scenarios, depending on the components that are included in the image. But, as always, more functionality means higher image footprint and so it is good to treat security considerations not as an afterthought, but as an important item on the requirements list, when designing the device architecture.
In a lot of usage scenarios the standard Windows authentication mechanism “Windows Logon” is not the appropriate way to handle user authentication. This may be due to the lack of input devices such as keyboard, or the fact that the device is running a custom shell, which never is logged off.