|
My solution has worked perfectly, though not "completely" ideal.
I tried so many versions of the placing the registry in the kitchen, and it still wouldn't work perfectly. I edited many times, but the program still wouldn't work well. Instead of wasting more time, I simply used 2 steps (these steps were outlined elsewhere, so I can't take credit for them). I used win ce cab manager. First I opened the Voice Command cab, then extracted all the files to my desktop. Then I placed the files into a newly created kitchen OEM. Next, in win CE cab manager, I deleted all the files (ignored the warning), changed the default install folder to \\windows (which you can change under cab properties option in the drop down menu of the program). I saved the cab and moved it to my device. The new cab was 87kb and has the setup.dll and the registry files.
Oddly, when I tried two versions of this approach, one worked well and one didn't work. If I tried to delete the setup.dll using win ce cab manager, the program wouldn't work. I had to include the setup.dll, and the program works normally.
Although this fix isn't perfect, it's good enough for me. I supposed it would be nice to have everything contained in the ROM OEM so I wouldn't have to load an extra cab from my device, but the time savings was worth it. I messed around for 8 hours trying to build an OEM with the rgu built in, but gave up and used the above method.
Good luck. I also used this for windows live because I couldn't get that to work no matter how I modified the rgu, and now that works, also.
Hope that helps.
|