J
jj3000
Hi all, I have successfully setup disk overlay on my CF (thanks to
Sandisk utility), but I am still not sure which type of EWF is right
for me.
At first I wanted a robust copy of XP that is like XPE but the users
may slam off the power at anytime. But at the same time I also wanted
the data to persist, so I tried out the disk overlay.
But it just occured to me that unless the user know how to run ewfmgr
-commit at strategic times to flush the disk overlay to the ewf
protected volume, the disk overlay will eventually fill up with
changes and blow up.. and I don't really want users to mess with the
ewf anyway. (for changes, I am talking about things like setting your
color scheme etc. and not encouraging user to copy files to the
protected volume)
My decision would be so simple if the device had NO explorer shell,
i.e. just task manager shell and launch the application to get a
somewhat embedded feel of the device. But this is not the case; the
marketing dept want to expose the other windows stuff to the users so
they can maybe later use outlook, internet explorer, and other 3rd
party XP apps, and use the device like a general XP computer.
I need to learn about the RAM overlay, if I call commit (in a shutdown
script), it actually writes to the disk at that moment, and not during
restart, right? (how can it because the changes are stored in the
RAM).
I am leaning towards RAM based with a shutdown commit. Please let me
know what you guys are doing for your devices!
Sandisk utility), but I am still not sure which type of EWF is right
for me.
At first I wanted a robust copy of XP that is like XPE but the users
may slam off the power at anytime. But at the same time I also wanted
the data to persist, so I tried out the disk overlay.
But it just occured to me that unless the user know how to run ewfmgr
-commit at strategic times to flush the disk overlay to the ewf
protected volume, the disk overlay will eventually fill up with
changes and blow up.. and I don't really want users to mess with the
ewf anyway. (for changes, I am talking about things like setting your
color scheme etc. and not encouraging user to copy files to the
protected volume)
My decision would be so simple if the device had NO explorer shell,
i.e. just task manager shell and launch the application to get a
somewhat embedded feel of the device. But this is not the case; the
marketing dept want to expose the other windows stuff to the users so
they can maybe later use outlook, internet explorer, and other 3rd
party XP apps, and use the device like a general XP computer.
I need to learn about the RAM overlay, if I call commit (in a shutdown
script), it actually writes to the disk at that moment, and not during
restart, right? (how can it because the changes are stored in the
RAM).
I am leaning towards RAM based with a shutdown commit. Please let me
know what you guys are doing for your devices!