Hi Folks,
if you are looking for some literature on Windows Embedded Compact 2013 (WEC2013), I would suggest you to read the online book version of Samuel Phung (eMVP).
Enjoy !
-Nicolas
Tuesday, July 9, 2013
Article: “What‘s new in Windows Embedded Compact 2013“ in the ECE Magazine
Hi folks,
check out the article I wrote “What‘s new in Windows Embedded Compact 2013”
in the current ECE Magazine.
Have fun!
Monday, July 8, 2013
“There is a problem with this Windows Installer package” error during QFE installation
Hi folks,
if you try to install QFEs for Windows Embedded CE/Compact versions
prior to Windows Embedded Compact 7 (*.msi files) on systems running a post Windows XP OS, you might
encounter the following error:
In my specific case I needed to install a Windows
Embedded CE 6.0 R3 QFE on a Windows 7 32-bit system.
To solve this issue simply right-click the *.msi installer file, and select “Run this program in compatibility mode for:
Previous version of Windows” in the “Compatibility”
tab.
In fact you will encounter this error for every *.msi file, not just QFEs.
Have fun!
Saturday, July 6, 2013
Add Firewall exceptions to WES7 answer file
Hi Folks
When building a Windows Embedded Standard 7 image you can configure the Firewall rules in order to be able to enable the Remote Desktop. The following article explain the steps to follow in Image Configuration Editor (ICE) : http://msdn.microsoft.com/en-us/library/ff794875(v=winembedded.60).aspx
The configuration of the Firewall require the identification of the functionality Identifier that is located in the FirewallAPI DLL. This identification can't be found on the internet, and some actions on your side must be performed in order to configure the Firewall to match your requirements. The identifier that should be use, is the resource identified in the library, and you can use Resource Hacker application (http://www.angusj.com/resourcehacker/) on the FirewallAPI.dll.mui file.
Example of IDs :
@FirewallAPI.dll,-28502 (File/Print Sharing)
@FirewallAPI.dll,-28752 (Remote Desktop)
-Nicolas
When building a Windows Embedded Standard 7 image you can configure the Firewall rules in order to be able to enable the Remote Desktop. The following article explain the steps to follow in Image Configuration Editor (ICE) : http://msdn.microsoft.com/en-us/library/ff794875(v=winembedded.60).aspx
The configuration of the Firewall require the identification of the functionality Identifier that is located in the FirewallAPI DLL. This identification can't be found on the internet, and some actions on your side must be performed in order to configure the Firewall to match your requirements. The identifier that should be use, is the resource identified in the library, and you can use Resource Hacker application (http://www.angusj.com/resourcehacker/) on the FirewallAPI.dll.mui file.
 |
| ResourceHacker in action for File and Printer Sharing |
Example of IDs :
@FirewallAPI.dll,-28502 (File/Print Sharing)
-Nicolas
Friday, July 5, 2013
Enable custom shell per user under WES7
Hi Folks,
We are going to change the default shell launched at user logon, the idea is to have a default shell like your product application to be executed when the default user is logged, and the explorer shell when an administrator starts a session.
http://msdn.microsoft.com/en-us/library/ms838576.aspx
The following registry value :
For security reason you can understand that we must set your application as the default user shell. And per user account configure different shell like the explorer shell for the administrator user. In case of user being able to create new user account on the system through a back door of the system or using malicious code, then this hacker will also have to configure the user account to set a different shell in order to be able to make more damages onto your device.
- Nicolas
We are going to change the default shell launched at user logon, the idea is to have a default shell like your product application to be executed when the default user is logged, and the explorer shell when an administrator starts a session.
Registry configuration
The following MSDN article describes the configuration required under Windows Embedded Standard 2009, but it require some adjustments under Windows Embedded Standard 7.http://msdn.microsoft.com/en-us/library/ms838576.aspx
The following registry value :
should be set to :Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\IniFileMapping\system.ini\boot\Shell
Value: USR:Microsoft\Windows NT\CurrentVersion\Winlogon
Security considerations
The explorer shell is more user friendly for platform maintenance but open the device to its settings. By launching your application for lambda users then you ensure that the user won't mess up the system, as your application will provide the minimal set of functionality required by your product.For security reason you can understand that we must set your application as the default user shell. And per user account configure different shell like the explorer shell for the administrator user. In case of user being able to create new user account on the system through a back door of the system or using malicious code, then this hacker will also have to configure the user account to set a different shell in order to be able to make more damages onto your device.
- Nicolas
Monday, July 1, 2013
Windows Embedded 8.1 Industry Pro Preview Release
Hi Folks,
Check out the new public pre-release of Windows
Embedded 8.1 Industry Pro here
on Connect. Windows Embedded 8 Industry is the successor of POS
Ready. On Connect, you can file suggestions and bugs.
There is also a MSDN
forum for the Windows Embedded 8.1 Industry Pro pre-release where you can
discuss features, etc.
Have fun!
Subscribe to:
Posts (Atom)