Quote:
Originally Posted by rstoyguy
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....
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. |
Awesome info! Much appreciated! Ok, I will check out the security issue. I am assuming that when you say to copy that key that I would be pasting that same key into the .rgu created by package creater.
So those .cereg files are post install reg settings? I see then that you added them to the .rgu. For most other OEM's, is that needed? Does that make the app "more fully installed" versus just having the program files copied to the apps directory?
As for the UC, I get it now and you are right. When I install with the cab, and it freezes right after installing and I do a reset, the app kicks right back up where it left off. I now understand what you mean by letting UC copy the link. I'll certainly give this a shot aslo when I get home.
EDIT: While i am asking questions, when I cook ThumbCal into the rom, I also found the reg settings that allow ThumbCal to be the default calendar. On first start up after flashing, when I select Calendar on the Home tab, it still launches the stock calendar. When I go into Thumbcal's settings though, it does show that Thumbcal should be the default. If I deselect them, select ok, reselect the settings again and then try it, it works.