C wince updating registry values
They will then be available during boot for the driver of thetouchscreen. Post by Roberto Waltman The project I'm working on, (like many others, judging from searchingthe group archives) has a volatile registry which means the touchscreen calibration is lost when cycling power.
Thanks, Roberto Waltman[ Please reply to the group,return address is invalid ] Roberto I had the same problem and found that was quite easy to create a driver thatsimply reads the calibration data and places it in the registry prior to thetouchscreen driver starting.
I would like to avoid this approach because it increases the timespent in an already lengthy boot process, and (from a post by Dean Ramsier in a 2002 thread) is not guaranteed to work, if the BSPsupplier did not make sure the RAM object store is preserved.
I am planning to modify the touch screen driver to load this data whenit is initialized.
Can anyone give me an alternative solution Autorun from registry and Create Process dont take parameters, so they wont work in this case.
Installing the CAB file once when the decive is assamblied, may cause the included driver to fail in future, when a customer resets the registry, since all the drivers registry settings will be deleted and the driver cant recover.
It can only start another application without parameters! It seems the calibration data was read and cached muchearlier.An older version of this project (on a different platform)accomplishes this by comparing the data in the registry with the EEPROM and, if they are different, load from EEPROM and perform a warmboot.Thanks, Roberto Waltman[ Please reply to the group,return address is invalid ] There's an IOCTL value passed to your OEM Io Control handler in the kernel,in CE4.x and 5.x, called IOCTL_HAL_INITREGISTRY.You can, when you processthat, set the values for the calibration constants that you recovered fromelsewhere.