Configuring EWF RAM Reg Mode

  • Article

5/10/2007

EWF RAM Reg mode stores overlay data in RAM and EWF configuration information in the registry. Because EWF RAM overlays store the data cache in RAM, your device may require additional RAM. Also, because the data cache is stored in volatile memory, the data cache is lost when the system reboots.

Additionally, because EWF configuration information is stored in the registry, which is typically protected by EWF, you must use the ewfmgr -commitanddisable command to apply any changes to EWF.

To configure EWF RAM Reg mode

  1. If you are using FAT16-formatted media, you must use BootPrep to prepare the media. BootPrep updates the boot sector that MS-DOS generated. This allows the media to boot the Windows XP boot-loader instead of the MS-DOS boot-loader. For more information, see BootPrep. If you are deploying to an NTFS-formatted or FAT32-formatted CompactFlash file system, you do not need to use BootPrep.

  2. Create a working configuration by using Target Designer. To create a configuration, follow the steps provided in Tutorial: Building and Deploying a Run-Time Image.

  3. Add the following components to your configuration:

    • Background Disk Defragmentation Disable
    • Enhanced Write Filter
    • EWF Manager Console Application
    • Registry Editor (optional)

    EWF RAM Reg mode does not require EWF NTLDR. You can add the standard NTLDR to your configuration.

  4. Expand the Enhanced Write Filter component node in the configuration browser pane and select Settings. The EWF Configuration Settings appear in the details pane.

  5. Add command-line support to your run-time image. If you are using the Explorer shell, enable support for the Run command on the Start menu:

    1. Expand the User Interface Core component in the configuration browser and choose Settings. The User Interface Core settings appear in the details pane.
    2. Select Show Run on Start Menu.

  6. Check dependencies and build the run-time image.

    1. Choose Check Dependencies from the Configuration menu. Resolve missing dependencies.
    2. Build the run-time image. Choose Build Target Image from the Configuration menu.
      The configuration settings for EWF are stored in the registry of the run-time image. When the run-time image is deployed, EWF will be disabled.

  7. Deploy the run-time image to your device, or to the intermediary hard disk where you want to run FBA.

    Note

    You can use an intermediary hard disk to configure FBA for write-sensitive devices such as CompactFlash. Using an intermediary hard disk facilitates the FBA process and reduces the amount of write operations that are made to the device.

  8. Boot the device and allow FBA to finish.

  9. Boot your run-time image.

  10. Verify that EWF is properly configured. From the Start menu, choose Run, then type cmd. Type the following command on the command prompt:

    ewfmgr c:

    Ewfmgr should report that EWF is enabled and provide a current status of the EWF RAM overlay.

Note

If you are using an intermediary hard disk, copy the run-time image to the CompactFlash device after verifying that EWF is properly configured.

  1. If you are using FAT16-formatted media, you must use BootPrep to prepare the media. BootPrep updates the boot sector that MS-DOS generated. This allows the media to boot the Windows XP boot-loader instead of the MS-DOS boot-loader. For more information, see BootPrep. If you are deploying to an NTFS-formatted or FAT32-formatted CompactFlash file system, you do not need to use BootPrep.

  2. Create a working configuration by using Target Designer. To create a configuration, follow the steps provided in Tutorial: Building and Deploying a Run-Time Image.

  3. Add the following components to your configuration:

    • Background Disk Defragmentation Disable
    • Enhanced Write Filter
    • EWF Manager Console Application
    • Registry Editor (optional)

    EWF RAM Reg mode does not require EWF NTLDR. You can add the standard NTLDR to your configuration.

  4. Expand the Enhanced Write Filter component node in the configuration browser pane and select Settings. The EWF Configuration Settings appear in the details pane.

  5. Add command-line support to your run-time image. If you are using the Explorer shell, enable support for the Run command on the Start menu:

    1. Expand the User Interface Core component in the configuration browser and choose Settings. The User Interface Core settings appear in the details pane.
    2. Select Show Run on Start Menu.

  6. Check dependencies and build the run-time image.

    1. Choose Check Dependencies from the Configuration menu. Resolve missing dependencies.
    2. Build the run-time image. Choose Build Target Image from the Configuration menu.
      The configuration settings for EWF are stored in the registry of the run-time image. When the run-time image is deployed, EWF will be disabled.

  7. Deploy the run-time image to your device, or to the intermediary hard disk where you want to run FBA.

    Note

    You can use an intermediary hard disk to configure FBA for write-sensitive devices such as CompactFlash. Using an intermediary hard disk facilitates the FBA process and reduces the amount of write operations that are made to the device.

  8. Boot the device and allow FBA to finish.

  9. Boot your run-time image.

  10. Verify that EWF is properly configured. From the Start menu, choose Run, then type cmd. Type the following command on the command prompt:

    ewfmgr c:

    Ewfmgr should report that EWF is enabled and provide a current status of the EWF RAM overlay.

Note

If you are using an intermediary hard disk, copy the run-time image to the CompactFlash device after verifying that EWF is properly configured.

See Also

Other Resources

EWF Modes
Troubleshooting Enhanced Write Filter
EWF Performance Considerations