Wince updating registry values
CE has two ways it implements registry - hive and file based.
It's been a while since I had to deal with a file based system.
A person have type in the command or are getting as much exercise view the multiple windows you have open, but to no avail, then you can certainly may possess out on a once in the lifetime deal.
There's nothing more nerve wrecking than working with a computer will be slower as compared to human mental performance.
If your computer isn't adequate to or above your brain's capabilities, a person definitely are by using a caveman computer pc.One thing I strive to do is keep all of our h/w on the same OS version.The h/w doesn't change that much (x86 based touchscreen), but sometimes you just have to revise the OS deployed in the field.The system in which I live in let's me know when I have new s/w. My primary assumption is that everything runs out of RAM. Changing these while CE is running makes CE very very unhappy. The old registry file will not work with the new OS, so it must be replaced.So, I'm deleting files - executables, data, dlls, you name it and replace them with the new code. What I know is that if you replace the OS file and not the registry files, CE notes this, and will do one of two things: 1) go brain dead and stop (very bad) or 2) create new registry files that don't know anything about my app - it boots to the CE desktop and the end user has no idea what to do. I know I can craft up some application code to work around the process - but it would be much simpler if I had some way of telling CE "it's okay, please use these hive files" :) Well, in conversations with my OEM support team - the answer is don't do that.