Microsoft

Introducing Microsoft
Azure Intelligent
Systems Service
How big data
creates new
marketing options
for retailers
Enabling productivity
with the
Internet of Things
Innovate data management
With Windows Server R2
for Embedded Systems

bloggers

discussions

  • Windows Embedded Blog

    Customizing Windows Embedded Standard 2011

    Introduction

    During the planning phases of Windows Embedded Standard 2011, we invested considerable effort to make Windows Embedded Standard 2011 customizable to the point where our customers will be able to create a custom experience – from the moment the machine boots up until it shuts down. To reach this goal we introduced several new packages and features.

    • Unbranded Startup Screens
    • Custom Logon Desktop Background Images
    • Message Box Auto Reply (also in Windows Embedded Standard 2009)
    • Dialog Filter
    • Shell Launcher
    • Credential provider samples that show how to customize the logon experience
    • Hide Boot Screens package
    • Dialog Filter configuration utility – A friendly GUI tool to configure dialog filter

    Read More...

    Comments Product Updates

    ...
  • Windows Embedded Blog

    EWF Overlay Limits on Windows Embedded Standard 2009 and 2011

    Introduction

    When using Enhanced Write Filter (EWF) in RAM or RAMREG mode several customers might assume the EWF overlay is limited solely by the availability of physical memory. Consequently, many assume they will be able to achieve an overlay twice as big on a system with 2 GB RAM than on a system with 1 GB RAM. This is not true by any means. This article explains the factors that limit the overlay size and the significant improvements seen on Windows Embedded Standard 2011.

    If you are interested more in the conclusion than the internals, skip the following sections and jump directly to the “Results and Conclusion” section.

    Read More...

    Comments Product Updates

    ...
  • 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

    Adding Custom Files And Creating an IBW Disk in Windows Embedded Standard 2011

    Note: The content in this blog is for users who are familiar with using Image Configuration Editor (ICE) to create a fully resolved answer file. If you would like to learn how to create a fully resolved answer file, please refer to this blog article.

    ICE provides easy ways to add custom files to your Windows Embedded Standard 2011 image and generate a bootable IBW Disk. This blog article explains how these are done in ICE.

    If you’ve chosen to install the Windows Embedded Standard toolkit with Typical option, you should find the DS in <Root Drive>\Program Files\Windows Embedded Standard Windows Embedded Standard 2011\DS. In the DS, there is a folder called “$OEM$ FOLDERS”. From Windows explorer, create a folder structure MyApps\$OEM$\$1\App1 as shown below.

    Read More...

    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

    ...
Page 65 of 77 (385 items) «6364656667»