Design Considerations for Using EWF with Hibernation

5/10/2007

The following list shows the design considerations that you should be aware of when you design a run-time image that uses EWF with hibernation:

Performance Considerations for using Hibernate Once/Resume Many

Using Hibernate Once/Resume Many can significantly improve boot time. To make additional improvements to the boot performance of your device, consider the following list of options:
- Eliminate any non-essential device drivers.
- Eliminate any non-essential services.
- If possible, use Minlogon.
- Review the BIOS settings on your device. If possible, reduce or eliminate items such as memory scanning or auto detection.
  For more information, see How to Improve the Boot Performance of a Run-Time Image.
When you boot from a hibernation file, you can press F8 during the Resuming Windows screen to display the boot options screen. You can select Continue for a system restart, which causes the boot process to resume from the hibernation file, or you can select Delete restoration data and proceed to the system boot menu, which starts Windows normally. Alternately, you can use the EWF Manager or EWF API functions to activate and deactivate HORM to reduce the number of required reboots.
If your system has more than one fixed volume, all of the fixed volumes on your system must be protected by EWF. This is because the file system holds cached information about each volume in memory, and that cached information is saved within the hibernation file. For more information, see Creating an Unprotected Volume in a Hibernate Once/Resume Many Environment.