About EWF
Inchul Lee
The following is result of "ewfmgr".
-------------------
The Ewf Vloume is "\Device\HarddiskVolume4"
Ewf Volume Configuration
Volume Size 32256
Segments 0
Segment Size 0
Free Segments 0
Max Levels 1
Max Protected Volumes 1
Protected Volume 1
Ewf Volume percent full -1.#j
Protect Volumes
Device Name "\Device\HarddiskVlume2"
----------------
For reference,I used RAM based Ewf, and I divided Harddisk
as the following.
|----------------|
|XP Pro | <--- about 4G
|----------------|
|XPe | <--- about 4G
|----------------|
|Partition | <--- about 5G
|(Unformat) |
|----------------|
|raw disk space | <--- about 5G
|(Unpartition) |
|----------------|
--------------------------------------------
I have some question.
1. "Ewf Volume percent full -1.#j" <-- What mean?
2. To run RAM based Ewf (or Disk based Ewf),is it must
needed "raw disk space"?
Thnaks.
Huw Ford
"Inchul Lee" <li...@maxan.com> wrote in message
news:042501c31438$684a74e0$a301...@phx.gbl...
1. Sorry I have no idea what "Ewf Volume percent full -1.#j" means.
2. Yes for RAM based, EWF will create a small partition for it's own use.
I havn't used Disk based EWF yet but it will probably do the same as RAM
based and will need another partition to write the proteced data to.
Heidi Linda
>needed "raw disk space"?
Reports seem to vary on this. I'm running a RAM EWF on my
system, and the partition is created in some free space
within the extended partition, after my logical drive. It
doesn't seem to create if the logical drive takes up the
entire extended partition and there is unpartitioned disk
space, however.
Charles Tsai
I'm using RAM EWF, too. After FBA, I transfer the image (but
not the EWF partition) to a new disk and EWF still works
for the protected volume, and I can manage the volume
with commands like "ewfmgr c:" and "ewfmgr c: -commitanddisable"
without a problem. The only side-effect I notice is that when
I run ewfmgr without any arguments, it reports that an EWF
partition cannot be found.
Am I missing anything, or RAM-based EWF just can be used
in this way (without an EWF partition)?
"Heidi Linda" <h...@bts.co.uk> wrote in message
news:062d01c31475$230ed690$a301...@phx.gbl...
Doug Hoeffel
From my experience, the RAM-based EWF will be enabled if you deploy without
the EWF partition. So, if I understand your process: you deploy without
imaging the EWF partition but the EWF becomes enabled. You then disable the
EWF by doing the -commitanddisable. Is this correct? Can you then enable
and disable the EWF via the -enable and -disable commands? If this actually
works I would find it strange. Personally, I would come up with a
deployment scheme where you image the EWF partition even when you use the
RAM-based EWF.
... Doug
"Charles Tsai" <cha...@easyuse.com.tw> wrote in message
news:OvK8aKKF...@TK2MSFTNGP10.phx.gbl...
John Macintyre [MS]
partition. In this case EWF looks for the config partition (i.e. EWF
partition) and when it cannot be found the driver will default to settings
stored in the registry. This is particularly useful for media that cannot
be partitioned. HOWEVER - you need to be cautious when using EWF in a
RAM/registry configurations. EWF Manager has some limitations. For
instance - the only way to disable is to perform a commitanddisable. This
is because the only way EWF can change the registry configuration is by
committing the overlay. So as a general rule of thumb - it is always better
to use an EWF partition since you get more flexibility for enable/disable
and additional support for persisting data (through the EWF APIs). But EWF
with a RAM overlay does not require the config partition.
- John
This posting is provided *AS IS* with no warranties, and confers no rights
"Doug Hoeffel" <doug.ho...@SPAMcamtronics.com> wrote in message
news:OhBu25KF...@TK2MSFTNGP10.phx.gbl...
Charles Tsai
Hi, Doug,
Yes, your understanding is correct. When I transferred the image to
a
new disk without an EWF partition, the originally disabled EWF became
enabled. However, I could switch on/off EWF with "ewfmgr c: -enable" and
"ewfmgr c: -commitanddisable" several times, and every time (after a reboot)
ewfmgr reported the correct state as expected. I guess that EWF stores
the settings somewhere in the registry rather than in the EWF partition in
the
case of RAM-based overlay.
Such behavior was discovered totally by accident. Normally I
transferred
the EWF partition along with the image, but I just forgot to do so a couple
of
days ago. When I realized it today (by typing ewfmgr without any arguments
and seeing the complaint), I was really confused... I just want to make sure
whether such usage is correct and consistent with the documentation (if it
is
documented at all :p)
"Doug Hoeffel" <doug.ho...@SPAMcamtronics.com> wrote in message
news:OhBu25KF...@TK2MSFTNGP10.phx.gbl...
Charles Tsai
Hi, John,
Thanks... You have answered my questions. In addition to the
issue regarding "commitanddisable" command-line option, is there
any other known limitation with RAM/Registry configuration? I also
noticed that ewfmgr will not show "the command to execute on
next boot" without an EWF partition. Can I get this information via
any of the EWF APIs under such circumstances?
Is the distinction between RAM/Registry and RAM/Partition
relevant to us? Is there any way to know about current configuration
(RAM/Registry or RAM/Partition)?
Regards,
Charles
"John Macintyre [MS]" <joh...@online.microsoft.com> wrote in message
news:uKVyJdLF...@tk2msftngp13.phx.gbl...
John Macintyre [MS]
With RAM/Registry you cannot store persistent data through the
EwfMgrSetPersistentData API. There are also several other APIs that don't
apply to RAM/Reg. You should refer to the EWF API documentation for more
info.
This issue with EWF Manager not displaying the next boot command for RAM/Reg
is known. We are working on a fix for the APIs - so 'yes' as soon as we
release the next EWF QFE you will be able to get this through the APIs.
There are no plans to QFE EWF Manager.
The distinction between RAM/Reg and RAM/Partition is relevant. As I
mentioned you should use RAM/Reg as a last resort when you absolutely can't
find a way to partition the media. Look through the API documentation and
you'll see several APIs that don't apply to RAM/Reg. Disabling is the
biggest issue - you have to commit the entire overlay to disable EWF... it's
a bummer but that's why we have the overlay config partition.
Thanks,
John
This posting is provided *AS IS* with no warranties, and confers no rights
"Charles Tsai" <cha...@easyuse.com.tw> wrote in message
news:upqxRmLF...@TK2MSFTNGP12.phx.gbl...
Charles Tsai
Thanks for the information ^_^
"John Macintyre [MS]" <joh...@online.microsoft.com> wrote in message
news:%23uxqvMP...@tk2msftngp13.phx.gbl...