Yeah, but the problem is most of us don't run unprotected partitions. What
is the sense in having an unprotected partition on CF?
You would figure that in embedded XP, the ability to turn off some of the
logging would be beneficial, or do something like in my application, limit
the size of the logs. Ie an circular log, only keep the 200 entries and
when 201 comes about it over writes the oldest data in space 1.
So basically, are you saying if my image is 100 megs and is sitting on a 128
meg CF and I have 256 megs of ram it won't ever be an issue? If I
understand it correctly, the OS thinks I only have 28 megs free, so after it
writes 28 megs of information to the EWF RAM, the os is going to start to
issue "out of drive space"
Richard
Slobodan Brcin (eMVP) said:
Hi Carl,
XPE Image size is not important, what is important is remaining available size on the disk.
For instance if defragmenter is disabled and your system files occupy
130/180 MB of protected partition for instance. Then work case
scenario would be 50 MB of EWF usage since you can't write more different data to that partition.
But this is not something that you should allow to happen since other
thing would complaint that you don't have enough empty space.
You should use filemon or some other file monitoring technique and
determine what files are written to your protected partition and