Quote:
Originally Posted by boggsie
Master Yoda, I pulled down the blast shield and managed to use my light sabre to ... break the Elecont Weather OEM that I was trying to update.
Help, please!
|
Use the force...Try this OEM and use it as a guide. It's an older version, if I remember right, this one has intensive registry entries in the hkey_classes_root...If you haven't got it by tonight, I'll look at it.
edit:
OEM_ElecontWeather_c_ARMv4.....................Elecont Weather v1.0.723 Today Screen Plugin
Quote:
Originally Posted by aceracer24
Thanks rstoyguy! I'll give that a shot tonight.
About Thumbcal, I have this already as an OEM. I can post when I get home if I don't get beat to the punch.
I had one problem with it however. If I used package creator, I get an error on my phone when I select the option to change the default calendar to Thumbcal. Actually, I don't get the error until I click on Calendar on the Home tab of TF3D. I get something to the effect that a cert is not valid ir something is missing. If I OEM it up using OEMizer, it functions perfectly. Also, when using package creater, it seems to include an extra setupDLL.dll....maybe that has something to do with it?
|
setupdll.dll...well...shouldn't be there. OEMizer adds a security setting for the file, check out the rgu you made with oemizer and copy the following key:
hklm\security\appinstall\??? ; and you should be good....
Quote:
Originally Posted by aceracer24
s4.cereg, is that being read by something? The edits in .cereg are also in the .rgu except for the deviceID. I am a bit confused. Also a little blurry on why i let UC copy the start up link.
|
The *.cereg files are ones I exported after installing the .cab to help me make the oem, they shouldn't be there...
and...
For More Info on UC, Click HERE!
With the startup .lnk that the OEM installs, well it's really not meant for a post-flash, it's definately a post-.cab install program. the lnk jumps right into setting up the program, and you can't do that when windows is trying to set up your rom. So delete the entry out of the initflashfiles.txt in the OEM and copy that .lnk file post-flash with usercustomization into the \windows\startup directory. It's the only way that I can think to get around it.