Advanced OEM tricks :D
 

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:
If I make a mxip_CeleDial_100.provxml file with
Then that entry will get re-overwritten on cold boot, and hey presto it works :D

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

Good work on the OEMs, thanks once again schett! Currently the celedial oem I have w/o the provxml is working after my minor RSSI_Icons.dll OEM mod, but it did require a soft reset after the contacts were loaded (note: with my current autoconfig settings the contacts synced from mail2web right at boot thanks to a provxml :wink: )

Looks like we have a pretty good solution for the smartdialer problem. This one doesn't break the left soft button either!!

I'm coming to the well of knowledge once more...:thumbright:

What if we just make one big .cab file with any necessary registry changes, and add it to our Ext_ROM....would that accomplish the same thing?

Also, based on the Kitchen method, is there a folder that gets processed first (eg. LOC, OEM, OS), or is it all just by UUID?

Thanks so much for your insight, schettj!!

Yes a cab in the EXT rom would accomplish this, but the way schett is doing this it will work as an OEM in the kitchen without and mods. The extrom would be a personal change which might be more advanced than desired for a first time kitchen user. Also this provxml method would be helpful for any additional wrapper programs like a web front etc.

Cool. Tks much Im....

Umm... I guess I'll finally say something, considering that I've been amused that nobody else has figured this out.

There is, in fact, a consistent way to guarantee your .rgu file gets resolved last.

And the way is...


...It's all alphabetical.

I have my own customizations in an OEM labelled "ZZZ Customizations ZZZ". Always goes last. You can look at the CreateOS.exe log when it's reading the .rgu files, and you'll notice that the last alphabetical folder is the last .rgu read.

I was going to wait until the forum ROM project had gotten underway before mentioning this, but if people are going to need to go through this much trouble to try and get around this, I might as well pipe up now. :)

Thanks Sogarth! Any new information is always welcome since what i lack in knowledge i've been trying to make up for with determination. I can't speak for others here, but i did have to take a break to avoid burning out from fighting things similar to this.

Taking a bit of the output of my own CreateOS.exe:

• 39a3d1ba-b75c-11db-8314-0800200c9a66: Trimmed VJCandela 0.3
• 4db083db-a1ab-4cab-b363-9727394b9d9a: wavedev.dll
• 23090ee4-ca47-4bc8-a93e-c53630662c12: WM5torage 1.7.3
• cab3a5d5-e09b-495d-8382-7f5136998f58: WModem
• 049762a0-b3ee-11db-abbd-0800200c9a66: zaTelnet 0.5.1
• 3dfb15ec-b94c-11db-8314-0800200c9a66: ZZZ Customizations ZZZ

Can anyone actually explain to me why the UUID's are necessary on this device?

Great find, Sogart!