Hi,
we currently use the hive mechanism to keep registry settings on a disk
(compact flash card).
Actually only a few registry keys need to be persistent . For example the
touch calibration settings of a
touch screen driver.
It works ... but I see that the hive files are not only saving what we want
to save.
After reboot from a CF card that was in an identical hardware before,
(maybe with the exception of the network adapters MAC address)
the DHCP often doesn't work any more. I just don't get a valid address.
After deleting the hive files and restart it works fine again.
If a DHCP server gives me an IP address and other nework config data, is it
going to the registry hive ?
I think so, all delta is saved according to the documentation. Does that
cause our problems ?
Another strange effect: A USB keyboard plugged in ... works.
Then: boot without the usb keyboard.
When I then boot with the keyboard attached it doesn't work until I unplug
and replug it.
Also... removing hive files solves the problem.
The same with PC card slot. CE behaves slightly different if there was a
card in the slot last time
or not or never since the hive file was created.
Some things are just dynamic in our CE system.
I came to the conclusion that it is safer not to use hive but to save the
settings in my known reg keys
in my own binary file and to register our ocx Controls every boot time again
with a call to DllRegisterServer.
The system also boots faster without hive based registry.
Has anyone observed the same ? Maybe I can exclude registry keys from
persistence ?
Is there a better solution to the problem ?
Stephan