M
Mart
Hello,
I am interested in booting an embedded device every time from the same
hibernate file in order to cut down on boot time. it can not be a
regenerated hiberfil.sys file, but the same one from the initial boot
of the unit. I have seen scattered responces to this, but i am
interested in not only an answer to this question, but also a one stop
thread where this might be answered along with how to do it. I
understand this can be done through EWF, but what would the
configuration look like? is it good enough to just put the hibernate
file on disk and then subsequent attempts by the OS to delete the
hiberfil.sys file will be caught by EWF? I have played around with
this (without EWF, simply manually recopying the hiberfil.sys file
into the root directory), but the main problem i have run into is that
changes to disks (such as file changes) are lost.
we are intersted in deploying this with EWF on the main partition,
then having a non ewf partition with configuration data that must be
written to and kept permanently. is the windows file system cache what
is messing up the file system in this scenerio? is it possible to
achieve this while still having a partition where data can be
permanently kept?
Thank you in advance,
-Jeremy
I am interested in booting an embedded device every time from the same
hibernate file in order to cut down on boot time. it can not be a
regenerated hiberfil.sys file, but the same one from the initial boot
of the unit. I have seen scattered responces to this, but i am
interested in not only an answer to this question, but also a one stop
thread where this might be answered along with how to do it. I
understand this can be done through EWF, but what would the
configuration look like? is it good enough to just put the hibernate
file on disk and then subsequent attempts by the OS to delete the
hiberfil.sys file will be caught by EWF? I have played around with
this (without EWF, simply manually recopying the hiberfil.sys file
into the root directory), but the main problem i have run into is that
changes to disks (such as file changes) are lost.
we are intersted in deploying this with EWF on the main partition,
then having a non ewf partition with configuration data that must be
written to and kept permanently. is the windows file system cache what
is messing up the file system in this scenerio? is it possible to
achieve this while still having a partition where data can be
permanently kept?
Thank you in advance,
-Jeremy