64
OPEraTING SySTEMS
This function is not available at all for the volume C:\ which holds the registry,
because the change in the registry for the new state of EWF cannot become
persistent. Use ‘CommitDisable live’ instead to disable EWF for C:\
•
Commit:
Commits all current level data in the overlay to the EWF-protected vol-
ume. This function requires a reboot. After the reboot the EWF status of the volume
is still “ENABLED”.
•
CommitDisable live:
Immediately commits all current level data to the EWF-pro-
tected volume and then disabled EWF. This function does NOT require a reboot.
WarNING
all changes on the volume since the last reboot become effec-
tive. Do not execute this if you are not sure about the extent of the
changes.
WarNING
The changes become effective immediately with reboot. It is not
possible to undo this command with “Clear Command”.
•
Clear Command:
Clears a pending command for the volume that would have oc-
curred on the next restart.
4.4.7 Dependent Volumes (typically E:\)
As mentioned above, other volumes (in the following, typically E:\ which is the CFast
on KEB devices) are dependent from volume C:\ to change their configuration because
they are stored in the registry located on C:\ and thus the registry is protected against
any changes, if EWF is activated for C:\
If EWF is deactivated for C:\ all commands for the dependent volumes can be used
independently.
Otherwise, if EWF for C:\ is enabled, the following rules are effective:
•
Enable and Disable:
if one of these commands is used the following message
box asks if the Commit command for C:\ should also be set. It is recommended
to confirm with “Yes” because otherwise the Enable or Disable has no effect. The
message is not displayed if the boot command for C:\ "Commit" is already present.
