I use the RAM-based EWF deploying to a 60 Gb HD. When fba is done the size
of the EWF partition is 0xfc00. You can see this in the fba log. Also,
Symantec gdisk shows the size as 0.1 Mb but XP's disk manager does not show
this partition. I deploy using Symantex Ghost. After imaging a new HD, the
EWF partition size using gdisk is 7.8 Mb, and in XP's disk manager the size
is 8 Mb. From discussions with Symantec, 7.8Mb is exactly one cylinder on a
60GB HD, and the EWF partition size changed since it's a primary partition.
If the EWF partition was a logical partition then ghost would not change
it's size (I think... I've never verified this).
So, I'm not sure what's going on in your case since I don't use CF but it
sounds like the same thing as what I see. It probably has nothing to do
with HD vs. CF, but with how the partitions are created, i.e. primary vs.
logical etc.
HTH... Doug
"Huang Sheng-Chi" <(E-Mail Removed)> wrote in message
news:925801c345dc$1626f780$(E-Mail Removed)...
> Hi all,
> Was anyone sucessfull to set EWF parition size to less
> than 1 MB? I searched GOOGLE and couldn't find anyone
> able to do this - many just said to make sure you have
> enough space in your Extended Partition.
>
> MS's documents said that EWF RAM minimum size is 32KB.
> But I was only sucessful to do this with 7~8MB EWF
> partition on the CF card (TD project set EWF size to
> 40KB). Is this a bug?
>
> Not sure if this is related or not, but the minimum
> partition size that can be created with W2K's disk manager
> is 7MB. Could this be the problem that EWF supports a
> minimum size of 32KB, but one must create 7MB or higher
> for a partition on their media within Windows OS (in my
> case, fixed NAND CF card)?
>
> Thanks.
|
Similar Threads
