Registry Entry Restoration

  • Thread starter Thread starter Gereon
  • Start date Start date
G

Gereon

In general the EWF is a good thing, but there are cases where I want to be
able to keep changes to certain registry entries between boots (In
particular, I want to save touchscreen configuration data after a
recalibration). Does anyone have suggestions for any tools or methods I
could use to save off certain keys to alternate storage, then restore them
very early on after the next boot?
 
Gereon,

If you have access to the driver source code and willing to change it, you can easy move the calibration registry data to a profile
or a separate registry hive that you can store anywhere outside of EWF protected partitions. There are APIs to load and unload
registry hives. Or you can have them saved in a .reg file and being [re-]imported whenever you need.
If it is EWF/SP2 then you could even have a file on EWF protected partition where you could commit the changes after recalibration.
But this again requires some changes in the touchscreen driver.

If no source to the driver, then you can write your own driver that'd be loaded earlier than the touchscreen driver and prepare
(load up from an unprotected partition or committed file) the settings. Then if user recalibrates the screen you will just need to
update that data.
 
True, but that clashes with our particular project's reason for using the
EWF, which is to revert to a pristine XPE image at each boot. This image is
signatured by our BIOS before it'll actually boot.
 
Hi KM,
In this case, I don't have the ability to change the touchscreen driver.
The "earlybird driver" approach was what I was thinking I would have to do,
just thought that some generous soul might have already put something
together and shared it with the world already...

Still also looking into the possibility of disabling and enabling the
touchscreen to get it to re- up the config data too. If that works I'll be
able to restore the registry "late" from our main app.

KM said:
Gereon,

If you have access to the driver source code and willing to change it, you
can easy move the calibration registry data to a profile
or a separate registry hive that you can store anywhere outside of EWF
protected partitions. There are APIs to load and unload
registry hives. Or you can have them saved in a .reg file and being
[re-]imported whenever you need.
If it is EWF/SP2 then you could even have a file on EWF protected
partition where you could commit the changes after recalibration.
But this again requires some changes in the touchscreen driver.

If no source to the driver, then you can write your own driver that'd be
loaded earlier than the touchscreen driver and prepare
(load up from an unprotected partition or committed file) the settings.
Then if user recalibrates the screen you will just need to
update that data.

--
Regards,
KM, BSquare Corp.

In general the EWF is a good thing, but there are cases where I want to
be
able to keep changes to certain registry entries between boots (In
particular, I want to save touchscreen configuration data after a
recalibration). Does anyone have suggestions for any tools or methods I
could use to save off certain keys to alternate storage, then restore
them
very early on after the next boot?
Click to expand...
Click to expand...
 
Back
Top