G
Guest
Hi All~
I am hoping someone out there will have time to answer a couple newbie
questions for me about EWF / FBWF from a conceptual standpoint. I am new to
XPe coming from the WINCE world.
In Windows CE, I worked on a number of flash based OS devices. These used
3rd party utilities to manage the flash RAM. In one case I used Intel's PSM
and in another a similar tool from Datalight. The idea was two fold. The
first was protection. We had a protected area of flash for a base OS image,
plus a semi-protected area for the registry (required explicit flushing to go
from RAM to the solid state media), and finally, a completely read/write
enabled area for user and application data.
I sort of see how EWF and especially FBWF can fill the bill here so to
speak. Though I am a little fuzzy on both the usage of a page file, and, the
RAM requirements for EWF (sounds like maybe you must have the same amount of
RAM as you do EWF protected flash space?). What I don't see is the second
purpose of the flash management in WinCE. By that I am talking about
low-level wear leveling on the media. What component or driver in XPe
prevents us from prematurely wearing out the flash, besides simply trying to
minimize writes to it? I don't see any "scatter write" functionality unless
I am missing something.
Thanks in advance to anyone who takes the time to answer my query. I know I
am probably asking very elementry questions at this point, but we all have to
start somewhere right? I did read the MSDN intros on both EWF and FBWF so
while I am all for links to other docs, unless I missed something I did not
see the answers to my questions there specifically.
~Bill
I am hoping someone out there will have time to answer a couple newbie
questions for me about EWF / FBWF from a conceptual standpoint. I am new to
XPe coming from the WINCE world.
In Windows CE, I worked on a number of flash based OS devices. These used
3rd party utilities to manage the flash RAM. In one case I used Intel's PSM
and in another a similar tool from Datalight. The idea was two fold. The
first was protection. We had a protected area of flash for a base OS image,
plus a semi-protected area for the registry (required explicit flushing to go
from RAM to the solid state media), and finally, a completely read/write
enabled area for user and application data.
I sort of see how EWF and especially FBWF can fill the bill here so to
speak. Though I am a little fuzzy on both the usage of a page file, and, the
RAM requirements for EWF (sounds like maybe you must have the same amount of
RAM as you do EWF protected flash space?). What I don't see is the second
purpose of the flash management in WinCE. By that I am talking about
low-level wear leveling on the media. What component or driver in XPe
prevents us from prematurely wearing out the flash, besides simply trying to
minimize writes to it? I don't see any "scatter write" functionality unless
I am missing something.
Thanks in advance to anyone who takes the time to answer my query. I know I
am probably asking very elementry questions at this point, but we all have to
start somewhere right? I did read the MSDN intros on both EWF and FBWF so
while I am all for links to other docs, unless I missed something I did not
see the answers to my questions there specifically.
~Bill