GL,
1) EWF is a filter to disk driver. It doesn't know anything about files (FS used).
Basically if you preallocate a fixed number of blocks and don't allow to extend it, your EWF usage won't grow beyond the allocated
size.
If you create a file (do not delete/create it again) and file pointer is always within the inial file size, FS usually do not use
blocks outside of the pre-allocated.
It certainly depends on the FS implementation, but for FAT and NTFS this scenerio is usualy true. For some flash wear-out saving
OSes, it wouldn't be true - they will try to not write to the same block twice if possible and therefore EWF usage will always grow.
2) The EWF Partition size mentioned on the EWF component settings page is related to the EWF COnfig Volume size.
As you can imagine, it doesn't make sense for EWF RAM Reg mode.
For EWF RAM the size will be constant (32K/64K) and EWF Volume will contain the persistent config structure about protected
partitions, EWF states on each protected volume, EWF boot commands, etc.
For EWF Disk the size of EWF Volume is really a limit to how big the EWF Disk overlay can grow. The EWF volume size here should be
large enough to accommodate the total size of all protected volumes in the system.