EWF reenable when detecting new compact flash/Ide

  • Thread starter Thread starter jadeboy
  • Start date Start date
J

jadeboy

I have created Windows XPe image that need to be copied to other
Compact Flash/Disk On Chip device. Sometimes when we copy the image to
another Compact Flash/DOC, EWF reenable itself (I have an EWFTray icon
and it's green) after it detects a new hardware (it's detect the
Compact Flash), this is there a setting in registry to by default set
EWF to disable when it detect new hardware (ie.. new hard drive/compact
flash drive/disk on chip)?
 
RAM overlay. I haven't change anything in the default setting for
Enhanced Write Filter component.
 
jadeboy,

If you want to make it easy the process of transferring EWF protected image from one card to another, you may want to go with EWF
RAM *REG*. This will eliminate the need for EWF Config partition that may be the cause of the problem you are seeing.
 
Maybe I don't understand exactly. But by default, I have all the
setting on the MSDN page provided above except I don't have EWF writer
enable and overlay type RAM is setup as default. What do you mean by
*REG* ?

Thank you for your effort.
 
jadeboy,

If you followed the link, you'd see the exact description of the REG mode of EWF RAM.

It is basically a mode where EWF does not require a hidden config partition presence on the disk but rather keeps all EWF settings
in registry.
 
Thank, can I copy the files and import the registry to an existing
image after installation instead recompiling it using target designer.
 
You can use http://www.slobodanbrcin.com/xpe/ewf/regramewf.html component
to ease your work, i have use it in production quality images and so far it
works fine for me...

A big toast to Mr. Slobodan Brcin !
Click to expand...

This is a big help and it seems to work. But I'm having a problem with
the component reporting an error on dependency checking. I
disable/remove EWF has described in the readme and I try to do a
dependency check again, but I always get an error (although it will
compile fine) end after resolving/disabling EWF the problem. Is there a
way to fix this error?
 
jadeboy,

The error you are getting is there because Slobodan's EWF component has an explicit conflict with the "Enhanced Write Filter"
component. In other words, you better have one or another component in you build as they both will bring ewf.sys driver.

Perhaps in you build you also has EWFMGR component (or EWF NTDLR), do you? That component has a dependency on the "Enhanced Write
Filter" component and therefore dependency auto-resolver will bring the component back even if you remove or disable it.

Probably the only way for you to get a clean build is to remove all the components from your build that depends on the "Enhanced
Write Filter" one. If you need ewfmgr.exe in your image, just copy it over through your own component or TD Extra Files and resolve
(manually add components) all its dependencies (from original component) except the "Enhanced Write Filter".
 
Back
Top