Technically, having EWF and FBWF protecting the same partition is an
unsupported scenario, and as such it hasn't received a lot of testing. I'll
try to answer the operation question, though:

EWF RAM (Reg) mode does store its configuration info in the registry, but it
may not function properly if there is also an EWF configuration partition on
the hard drive. You can't always see that partition through Diskpart or
Disk Management tools - in all the tests I've run, it's been hit-or-miss as
to where I can see the extra partition, if one exists at all. The EWF
config partition is for Disk and RAM modes only.

When you set up EWF in Target Designer, having the EWF mode set to RAM (Reg)
automatically disables a step in FBA that initializes the config partition
(this step is enabled in RAM and Disk modes), so the partition should never
be created in this scenario. As such, the "OVSize" value actually doesn't
matter in this scenario - it really only matters in Disk mode, since it
specifies the size of the disk overlay, and neither RAM mode will use it.

I believe the problem lies in some low-level configuration info in the
registry that both EWF and FBWF rely on for their functions. Both filters
need to know what partitions they're protecting, in what modes, and whether
they're enabled or not. My suspicion is that when FBWF writes its config
info, it's overwriting a key used by EWF, and EWF "loses track" of that
partition. Then EWF tries to get its configuration info from the config
partition (which doesn't exist), and thus gives you the error message you
mentioned.

This right now is speculation on my part, since I don't currently have the
ability to verify this, but it makes sense given that EWF and FBWF *can*
coexist on the same system protecting different partitions.

--
Matt Kellner
SDET, Microsoft Windows Embedded Team

This message is posted AS-IS, without any warranty, and confers no rights.


"Mike Warren" <miwa-not-this-bit@or-this-csas.net.au> wrote in message
news:xn0fra0i179dvx000@news.microsoft.com...
> crus wrote:
>
>> EWF RAM REG has its config in registry, so no extra partition is created.
>> Perhaps FBWF conflicts with its registry use.
>> Also check at the end of FBALOG ( in windows\fba ) if EWF setup is
>> correct.
>
> Thanks for the reply Raffaele.
>
> I'm trying to get some more information about how EWF works. I was
> wondering about a possible conflict between EWF and FBWF. It's really
> puzzling that I can restore this image to the same hard drive I created
> it on and it will work fine.
>
> --
> - Mike