Microsoft

Creating cloud-connected
"intelligent" elevators
with Microsoft Azure services
Introducing Microsoft
Azure Intelligent
Systems Service
How big data
creates new
marketing options
for retailers
Enabling productivity
with the
Internet of Things

bloggers

discussions

  • Windows Embedded Blog

    WMI Command-line Tool is not Completely Localized in Std 2009

    The Windows Management Instrumentation Command-line tool is not completely localized because the file CLIEGALI.MFL for the appropriate MUI language is not brought into the runtime when it is built in Target Designer. This is the file that defines the localized WMI namespace root\cli\MS_xxx, where xxx is the LCID for a language (e.g. 411 for Japanese). This file, for every language, does exist in the repositories but is not owned by any component.

    To solve this problem copy the file (for the specific language you need) from the embedded repositories to the runtime, and place it under %Windows%\MUI\Fallback\<LCID>.

    If wmic.exe has been run at least once it gets a little more complicated. When you run wmic for the first time, it compiles its MOF and MFL files (Cli.mof, Cliegaliases.mof, and Clialiases.mfl, etc), which get written into the WBEM repository (%WINDOWS%\system32\wbem\Repository) along with MOF/MFL files from other WMI providers. To resolve the problem in this case:

    1. Copy the file over to the XPe device and then

    2. Compile CLIEGALI.MFL after copying it to the runtime as follows:

    Open a command window and run the following command:

    mofcomp %Windows%\MUI\Fallback\<LCID>\CLIEGALI.MFL

    Comments Product Updates

    ...
  • Windows Embedded Blog

    Installing VS2005 or VS2008 redistributable files on Windows Embedded Standard 2009

    There have been several forum posts about including the redistributable files for Visual studio 2005 or Visual Studio 2008 in a runtime image so that applications built using these versions can run. Windows Embedded Standard 2009 database does not have componentized versions of the redistributable files for these versions of VS. The easiest way is to include the redist files as part of the application during development. If you are not the developer of the application then there are a few options.

    • You could create a new component with an FBA Generic Command that calls the redistributable package installer during FBA. You should set the FBA phase to between 8500 and 12,000 so that it runs later in the FBA sequence. If the redist package supports a quiet flag, and a silent install is desired, specify the appropriate switches in the Arguments property of the FBA Generic Command, such as

    “%11%\cmd.exe” for FilePath and

    “/c <path>\vcredist_x86.exe /q” for Arguments property.

    • Calling the redist executable directly will fail. You could just as easily do a RunOnce command in a new component, but an FBA Generic Command provides more control over the order that this command will run, especially if you have other components that are also doing custom actions during FBA.
    • You could also componentize the redist installer, which requires breaking the setup apart into the associated files and registry data and creating a component containing those resources.

    Comments Product Updates

    ...
  • Windows Embedded Blog

    Fine-tuning Embedded Device Experiences

    **Updated 3/26/09 with preface

    [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.] 

    An embedded device has to look like an embedded device! This means that the system and its user interface needs to be optimized according to the device purpose and should not behave like a PC. In some cases, the systems should not even give a hint about the platform they are running on. This does not only lead to a better usability experience, but also can be the first security barrier if systems are designed to operate in places where neither network nor physical access can be controlled very well. Gaming consoles, for example, are very often a target for fraud and designers try to set up many intrusion barriers to guard against this.

    Read More...

    Comments Product Updates

    ...
  • Windows Embedded Blog

    New Boot Configuration Component for Standard 2009

    In Feb 09 a new component was released as part of the Optional Update package (available from the ECE Site) called the Boot Configuration component. This component was created in response to requests from customers to be able to set various boot options offline in Target Designer.

    The new component is unusual in that it contains no resources <grin> but only configurable UI. Once added to a configuration you can select an number of options to add to the boot.ini that is created when that configuration is built.

    clip_image001

    Read More...

    Comments Product Updates

    ...
  • Windows Embedded Blog

    Custom authentication mechanisms

    **Updated 3/26/09 with preface

    [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.] 

    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.

    Read More...

    Comments Product Updates

    ...
Page 75 of 80 (396 items) «7374757677»