Compartir a través de


IMG Environment Variables (Windows CE 5.0)

IMG environment variables remove modules from your OS design. These variables leave the associated registry entries in your OS design intact.

These variables are available for your convenience. Do not use them in a shipped product.

If you set or unset an IMG environment variable in your OS design, you do not have to perform a full rebuild of your run-time image. Instead, you can simply run the Make Binary Image tool to create the new run-time image.

The following table shows all IMG environment variables.

Environment variable Description
IMGAUTH Enables run-time images to be keyed to a specific device, ensuring that the images are flashed only on the selected device.

When the device is booted, it validates the run-time image signature by ensuring that the signature matches the hardware device ID.

IMGAUTOFLUSH Enables automatic flushing of events to the release directory.

This must be used with IMGCELOGENABLE. For more information, see CeLog Tools.

IMGCELOGENABLE Adds CELog.dll to the OS design and initializes event logging when the run-time image boots.
IMGEBOOT Reserves space for the boot loader in ROM.
IMGFLASH Enables flashing the run-time image into ROM.
IMGHDSTUB Adds OS awareness for hardware-assisted debugging.
IMGKCOVER Enables code coverage.
IMGMULTIBIN Enables multi-XIP regions in the run-time image.
IMGNODEBUGGER Excludes debugger support from the OS design.

When set to 0, the OS design must also contain these files for the debugger to run: Hd.dll, Kd.dll, OsAxsT0.dll, and OsAxsT1.dll.

IMGNOKITL Selects a kernel that is not KITL-enabled.
IMGNOLOC Excludes localization functionality from the run-time image.
IMGNORDPINGWE Enables the RDP core, Mstscax.dlll, to be hosted in the same process as the container application, Cetsc.exe, for debugging and testing.
IMGNOREDIR Excludes redir from the OS design.
IMGNOSHAREETH Excludes VMINI support from the OS design.

Setting this environment variable might require you to perform a rebuild of the BSP. To do this, perform the following action:

  • From a command prompt build window, Navigate to the root directory for the BSP and enter the following command:
    build -c
  • From the Build OS menu in the IDE, verify that Clean Before Building, Make Run-Time Image After Build, and Copy Files to Release Directory After Build are selected.

    Then, from the Build OS menu, choose Sysgen.

IMGNOTAHOMA Excludes the Tahoma true-type font from the OS design.
IMGNOTALLKMODE Disables kernel mode, which is used to set ROMFLAGS in Config.bib.

For more information, see ROMFLAGS.

Note   Do not unset this environment variable in your OS design.
IMGOSCAPTURE Adds OSCapture.exe to the OS design. It starts buffering events in RAM when the run-time image boots.

For more information, see CeLog Tools.

IMGPROFILER Selects a profiling-enabled kernel.
IMGRAM16 Configures the run-time image for 16 MB of RAM.
IMGRAM32 Configures the run-time image for 32 MB of RAM.
IMGRAM64 Configures the run-time image for 64 MB of RAM.
IMGRAM128 Configures the run-time image for 128 MB of RAM.
IMGRAM256 Configures the run-time image for 256 MB of RAM.
IMGRAM512 Configures the run-time image for 512 MB of RAM.
IMGSIGN Includes the signature extension block in the ROM header.
IMGSHIMENABLE Includes the kernel-side portion of the Application Verifier Tool in the run-time image.

If this is included in the run-time image, it loads at boot time.

For more information, see Application Verifier Tool.

IMGTINYFSRAM Sets FSRAMPERCENT, which minimizes the amount of RAM allocated for the file system.

For more information, see Binary Image Builder File and FSRAMPERCENT.

IMGTRUSTROMONLY Sets ROMFLAGS, which configures the run-time image to trust only modules in ROM.

For more information, see Binary Image Builder File and ROMFLAGS.

See Also

Environment Variables | BSP Environment Variables | BSP_NO Environment Variables | PRJ Environment Variables | Miscellaneous Environment Variables

Last updated on Thursday, February 02, 2006

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.