EWF Api usage

[=?ISO-8859-1?Q?Ulf_Jaenicke-R=F6=DFler?=]

Hi,

we want to put an image on a CF card which is protected by EWF.
Sometimes it should be possible to update the configuration by
EWFcommit or even to disable EWF temporarily.
I have read Slobodans article on XPefiles. Has anyone experience
with using the EWF Api after installing an image that way?

Best regards
Ulf

 

[KM]

Ulf,

And what is the problem using EWF API?
I guess many of us used the API previously. Could you be more specific about your concerns?

With the EWF (RAM Overlay) without EWF Config partition you won't be able to use "commit" command as well as the related API
function.

 

[Slobodan Brcin \(eMVP\)]

Konstantin,

You mean he won't be able to use "disable" command, right?

commit, commitanddisable are supported by both API and ewfmgr.exe

Best regards,
Slobodan

 

[KM]

Slobodan,

You are absolutely correct. The only "disable" command would be a problem.
Thanks for watching out!

 

[=?ISO-8859-1?Q?Ulf_Jaenicke-R=F6=DFler?=]

Ulf,

And what is the problem using EWF API?
I guess many of us used the API previously. Could you be more specific about your concerns?

The code snippets from the EWF Api related .chm gave a lot of errors 87 while executing
EWF commands.

With the EWF (RAM Overlay) without EWF Config partition you won't be able to use "commit" command
as well as the related API function.

No "commit"?
Ah well - I see Slobodans post about being it "disable".

BTW, it seems that persistent data does not work without the EWF partition as well.

Thank you
Ulf

 

[Slobodan Brcin \(eMVP\)]

Hi Ulf,

For persistent data and RAM EWF you must commit and then gracefully reboot. This is the only way for data to be written from overlay
to disk.
Overlay is not written when you call commit but rather when you shutdown.

Best regards,
Slobodan

 

[=?ISO-8859-1?Q?Ulf_Jaenicke-R=F6=DFler?=]

Hi Ulf,

For persistent data and RAM EWF you must commit and then gracefully reboot. This is the only way for data to be written from overlay
to disk.
Overlay is not written when you call commit but rather when you shutdown.

Best regards,
Slobodan

Thank you another time for your valuable help!
Ulf

 

[KM]

Ulf,

The code snippets from the EWF Api related .chm gave a lot of errors 87 while executing
EWF commands.

Perhaps, EWF partitioin did not get created when you used API. Have you
checked?

Or, if you use registry based EWF, you tried "disable" command or APIs.

No "commit"?
Ah well - I see Slobodans post about being it "disable".

Sorry, that was a typo from me.
No "disable", of course.

BTW, it seems that persistent data does not work without the EWF partition

as well.

Hope you do a reboot to commit the EWF cache.

KM

 

[=?ISO-8859-1?Q?Ulf_Jaenicke-R=F6=DFler?=]

The code snippets from the EWF Api related .chm gave a lot of errors 87

while executing



Perhaps, EWF partitioin did not get created when you used API. Have you
checked?

Or, if you use registry based EWF, you tried "disable" command or APIs.

Hmmm, I believe I did not run etprep /delete before copying the image to a CF...

Sorry, that was a typo from me.
No "disable", of course.



as well.

Hope you do a reboot to commit the EWF cache.

Of course.

All works fine now - Commit, CommitAndDisable, Enable - from inside my
program by calling the API.

Thanks for your help!
Ulf

 

[KM]

Ulf,

I am glad it works for you now and I couldn't muddle you with the wrong info in my previous post