Thread: How To's For Developing Q & A
View Single Post
  #18 (permalink)  
Old 04-15-2008, 11:11 PM
dereknjenny04's Avatar
dereknjenny04
Regular 'Geeker
Offline
Location: Evansville, IN
  
Join Date: Dec 2007
Posts: 341
Reputation: 609
dereknjenny04 knows their stuffdereknjenny04 knows their stuffdereknjenny04 knows their stuffdereknjenny04 knows their stuffdereknjenny04 knows their stuffdereknjenny04 knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via MSN to dereknjenny04
Re: How To's For Developing Q & A
Quote:
Originally Posted by boggsie View Post
This might sound rediculous, but what if ...

I didn't want to mix and match between SYS and XIP ...

I only wanted to separate the OEMs out of the default Sprint OEM ROM ... and maybe create OEM folders for each of the components, so that when BuildOS.exe fired up, each of the OEM componenets (dialer, touchflo, biotouch, skins, etc.) were separately selectable via check-boxes ...

I have the Sprint OEM RUU_signed.nbh (OS Only) decomposed into the vogue_kitchen_tools directory structure.

Now I have OEMAPPS with about 350 items and a single *.rgu file with >3200 lines of registry entries.

Is the process as painstaking and manually sifting through the *.rgu file and moving files to their separate application folder, along with a new *.rgu file with the necessary registry entries?
That is exactly what I did on my v17 release.

Commented out the registry entries from components as I moved from OEMAPPS/OEMDRIVERS/OEM_Lang to OEMS and made a new .RGU file in the OEM with the appropriate keys.
__________________
Spread the rep! If someone helps, click the rep icon () to the right of the Post # .

 like my work: donate a buck
This post has been thanked 2 times.