EWF Commit not working

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm using XPE SP1 and EWF Ram component. However, when I execute a commit
(ewfmgr c: -commit) it says it successfully committed but after a graceful
shutdown and reboot, the changes I made are gone as if commit did not work.
Anyone?

Thanks
 
Tim,

Can you give a bit more info about your image?
Minlogon/Winlogon?
How you do the reboot exactly? (what command)
 
Tim,

This is first time I hear EWF doesn't do its job fine on Winlogon image.

When you do "ewfmgr c: -commit", can you check what the boot command set for ewf by launching "ewfmgr c:" command?
Also, when you shutdown "committed" image, check offline if the files you changed are really changed. The same with the registry
entries you added and committed.
Then you would know whether it is EWF or something.
 
Konstantin,

I had problems very long time ago with RAM EWF on minlogon images when using
commit and gracefull reboot.
So Tim what EWF version of QFE do you use?

Regards,
Slobodan
 
Slobodan,
I had problems very long time ago with RAM EWF on minlogon images when using
commit and gracefull reboot.
Click to expand...

Me too but that was with Minlogon only.
On Winlogon images I never had problems with EWF commit.
 
KM,

The boot command is "COMMIT" after i issue a "ewfmgr c: -commit" before I
shutdow gracefully.

I simply copy some files to the protected volume, issue the comitt, and
reboot. On restart they are gone.
 
Slobodan -

I'm using "EWF RAM Registry - Based on hotfix Q823025". I had this image
commiting successfully then added some things such as EWF Tray icon,
additional language support and changed the disk configuration slightly.
Thats about it.

Tim
 
Tim,
The boot command is "COMMIT" after i issue a "ewfmgr c: -commit" before I
shutdow gracefully.
Good.

I simply copy some files to the protected volume, issue the comitt, and
reboot. On restart they are gone.
Click to expand...

Commit your changes. Shutdown the unit. Explore the storage offline (if it is HDD - plug in in another machine or boot to another OS
if dual boot setup, etc.) - do you see the new files there?
 
KM,

I copied files to the protected drive, commited, shutdown gracefully. Booted
the drive on another OS and files were not there.
 
Tim,

Ok. Now we know it is EWF that exposes the issue on your image.

I'd suggest you to try (in the order):
- Install Q832662 (http://msdn.microsoft.com/embedded/downloads/xp/impqfe/q832662/default.aspx). See if it helps.
- Instead of "commit" try "commitanddisable" command and see if the files really get committed.
- Verify that you have EWF Config volume on your drive.
- switch to EWF RAM registry mode. For SP1 you would need to use Slobodan's EWFRAM component from www.xpefiles.com.
- Grab EWF binaries from SP2. See if it helps.
- Upgrade your Dev ToolKit and the Configuration to SP2. See if it helps.

Btw, what is the target storage on your device? Fixed, Removable?

Just in case, can you post here the output of "ewfmgr c:" command you did right after the "commit" command?
 
I'll get you the ewfmgr output after commit. Do I need an EWF config Volume
if I'm using Slobodans EWF RAM registry mode?
 
Tim,

No, you won't need the EWF Volume at all (that is the beauty of EWF RAM Reg mode).
Moreover, you have to delete the volume before you re-deploy the image. You can use diskpart or etprep /delete to accomplish that.
 
Back
Top