D
David Harris
The system I am developing requires frequent updates to the XP Embedded
application and only has a very small hard drive. To make life easy I network
boot from an SDI file loaded as a ramdisk (memory use and boot times are not a
problem). This system works well and is flexible enough to allow me to quickly
modify the images to fix any problems that arise on a particular client.
However you cannot make any system updates on a particular client device that
will be persistent across reboots because the ramdisk image cannot be modified
on the server.
What I would like to do is to set-up a disk-based EWF so that it provides
persistent storage of data across boot operations. If I read the documentation
correctly this is not possible because the EWF can only protect physical
devices. Can anyone think of a way that the EWF can be used to 'protect' a
ramdisk-based drive.
David A. Harris
application and only has a very small hard drive. To make life easy I network
boot from an SDI file loaded as a ramdisk (memory use and boot times are not a
problem). This system works well and is flexible enough to allow me to quickly
modify the images to fix any problems that arise on a particular client.
However you cannot make any system updates on a particular client device that
will be persistent across reboots because the ramdisk image cannot be modified
on the server.
What I would like to do is to set-up a disk-based EWF so that it provides
persistent storage of data across boot operations. If I read the documentation
correctly this is not possible because the EWF can only protect physical
devices. Can anyone think of a way that the EWF can be used to 'protect' a
ramdisk-based drive.
David A. Harris