Failed setting protected volume configuration with error 31

[kbodily]

I purchased an industrial PC with an XPe image running with EWF RAM. I
made some tweaks to it (changed the shell app, desktop wall paper,
user accounts etc.) and then ghosted the image (EWF was still working
before the ghost). After I deployed the ghosted image, the EWF volume
was not found, and after search the newsgroup I found that after
running "RUNDLL32 ewfdll.dll ConfigureEwf Start" EWF would start.
However, when I try to enable it I get the error in the subject line.
I don't have the original image any longer and would like to get the
ewf running properly from the point I am at now.

Here is the output from ewfmgr.....

C:\Documents and Settings\Administrator>ewfmgr c:
Protected Volume Configuration
Type RAM (REG)
State DISABLED
Boot Command NO_CMD
Param1 0
Param2 0
Volume ID AA 45 AB 45 00 7E 00 00 00 00 00 00 00 00 00 00
Device Name "\Device\HarddiskVolume1" [C:]
Max Levels 1
Clump Size 512
Current Level 1

Memory used for data 0 bytes
Memory used for mapping 0 bytes


C:\Documents and Settings\Administrator>ewfmgr c: -enable
*** Enabling overlay
Failed setting protected volume configuration with error 31.
A device attached to the system is not functioning.

Does anyone have any advice regarding what I need to do to make it
work?
thanks
kevin

 

[Stefan Klein]

If i remember correctly EWF relies on an additional partition. Seems
that Ghost didn't store that. I don't know if post-deployment EWF
maintenance tools are capable of doing this or if you could add this
partition manually. Try to look up the manual for EWF partition.

 

[kbodily]

If i remember correctly EWF relies on an additional partition. Seems
that Ghost didn't store that. I don't know if post-deployment EWF
maintenance tools are capable of doing this or if you could add this
partition manually. Try to look up the manual for EWF partition.

Its been my understanding that a RAM ewf partition is used for fba
only. After that it no longer used. If there are any other thoughts
please post.
thanks
kevin

 

[Stefan Klein]

I don't think so... use 'rundll32 ewfdll.dll ConfigureEwf' to recreate
the EWF volume.

If you want to clone/backup the system again be sure to save the whole
hdd (physically - with partition table) or at least with both partitions.

Quote from manual:

 

[kbodily]

I don't think so... use 'rundll32 ewfdll.dll ConfigureEwf' to recreate
the EWF volume.

If you want to clone/backup the system again be sure to save the whole
hdd (physically - with partition table) or at least with both partitions.

Quote from manual:

After the final FBA reboot, EWF searches for the EWF volume on the local computer.
If the EWF volume is detected, it is inspected by EWF. EWF then configures itself and executes any pending EWF commands in the volume, such as the commit command. If no EWF volume is found, EWF disables itself.
[...]
Because EWF creates an EWF volume during FBA, the EWF volume must be created on all of the devices to which you are deploying.
[...]
After you copy your run-time image to your device, you must enable EWF. If you are using EWF RAM or EWF Disk modes, you must create the EWF volume on the media. If you are using EWF RAM or Disk modes, create the EWF volume by booting the run-time image on the device and running the following command:

rundll32 ewfdll.dll ConfigureEwf

This command creates the EWF volume on the system and enables EWF. For more information, see ConfigureEwf.

Verify that EWF is enabled and running by using the EWF Manager command:

ewfmgr c:

thank you.... I ultimately needed to use etprep to delete the existing
ewf partition, then I was able to recreate it with rundll32...