S
Slobodan Brcin
I think that it is possible to implement RAM based EWF so that during FBA
EWF doesn't need partition.
Correct me if I'm wrong but let us consider following two scenarios:
First:
XPE passes all FBA phases without EWF installed. In last FBA step EWF get
installed and working from next restart.
Second:
EWF is installed like currently implemented. But instead of creating EWF
partition, every info you need could be stored in registry, or in some file
on XPE disk.
And EWF could be committed during all FBA restarts, so information's you
need could be preserved.
I don't know what info you need to save but previous scenario probably can
be done with very little modification to EWF.
I guessing that need for partition support during FBA is inherited from disk
based overlay support, so only thing you should do is to separate those two
cases
This would ease use of EWF during development and would avoid all problems
with strange cases when EWF wont install.
Hope that this feedback is useful,
Slobodan
EWF doesn't need partition.
Correct me if I'm wrong but let us consider following two scenarios:
First:
XPE passes all FBA phases without EWF installed. In last FBA step EWF get
installed and working from next restart.
Second:
EWF is installed like currently implemented. But instead of creating EWF
partition, every info you need could be stored in registry, or in some file
on XPE disk.
And EWF could be committed during all FBA restarts, so information's you
need could be preserved.
I don't know what info you need to save but previous scenario probably can
be done with very little modification to EWF.
I guessing that need for partition support during FBA is inherited from disk
based overlay support, so only thing you should do is to separate those two
cases
This would ease use of EWF during development and would avoid all problems
with strange cases when EWF wont install.
Hope that this feedback is useful,
Slobodan