Advanced OEM tricks :D - Page 2

**schettj** · #1 (**permalink**) 02-22-2007, 10:11 PM

Ok, so ImCokeMan and I have just about wrapped up the celedial OEM, and we ran into something that's cropping up more and more...

If you have a .rgu file, and it's overriding some default OS or OEM registry entry, it's a crap shoot if yours goes in last or not (last one wins!) - it seems like the order the .rgu files are processed is by uuid, sorted lowest to highest.

So... you either fudge your uuid, remove the offending registry entry from some other kitchen OEM or OS file, or...

use the .proxml file!

I'm testing that now. The .xml files also are processed alphabetically, but they are done at cold boot time, not build time, so they take a tiny bit of storage memory, but they're able to override anything in a .rgu file since they're processed after the hive is built.

So for celedial, this registry entry is getting overridden:

Code:

 
[HKEY_LOCAL_MACHINE\Security\Phone\Skin] 
"Ext"="\\Windows\\CeleDial.dll"

If I make a mxip_CeleDial_100.provxml file with

Code:

 
<wap-provisioningdoc> 
  <characteristic type="Registry">		 
		<characteristic type="HKLM\Security\Phone\Skin" translation="filesystem"> 
			<parm name="Ext" datatype="string" value="\Windows\CeleDial.dll"/> 
		</characteristic> 
</wap-provisioningdoc>

Then that entry will get re-overwritten on cold boot, and hey presto it works

Anywhoo, that's one way around the registry override issue.