Thread: How To Request: Cook your Own ROM
View Single Post
  #21 (permalink)  
Old 02-05-2008, 03:08 PM
OMJ's Avatar
OMJ
Retired Staff
Offline
Location: MN
  
Join Date: Jun 2007
Posts: 4,767
Reputation: 20305
OMJ can't get a higher reputation levelOMJ can't get a higher reputation levelOMJ can't get a higher reputation levelOMJ can't get a higher reputation levelOMJ can't get a higher reputation levelOMJ can't get a higher reputation levelOMJ can't get a higher reputation levelOMJ can't get a higher reputation levelOMJ can't get a higher reputation levelOMJ can't get a higher reputation levelOMJ can't get a higher reputation level
Mentioned: 11 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by mrgeoff View Post
I personally don't touch the registry files directly. I'm sure I would screw it up something fierce lol.

When you build a package, you can create a RGU file. That file can contain Registy entries that will be ran when the package is integrated. Also, you can build a option.xml file for each package. That XML file will allow you to use BuildOS to enable/disable a package.
I'm not talking about building a OEM package......most programs can be found already in an OEM.....but I know what you're saying about the OEM having the registry settings in the .rgu file.

I just wasn't clear what needed to be "updated" in the registry for that step in the process. btw, that was a cut/paste from Dogguys readme. Is it simply to make registry tweaks like you would do after flashing....ie battery tweaks?

this is the step I'm referring to:

-- Step 2 --
Step 2 involves adding, modifying and deleting packages and files. This is where the customizations really happen, and is the meat and potatoes of rom building.

During this stage you can:

1) Delete files and directories in OEM to remove them from the rom.

2) Edit the registry files (default.hv, user.hv). Under Tools\HV Tools\ are all the .bat’s necessary for converting to and from .txt files. I’ll give you a quick synopsis of how to modify these files, but it is up to you to finish the research for a full understanding. Under SYS\Metadata\ you will find the default.hv and user.hv files. Copy whichever one you need to modify to the Tools\HV Tools\ directory. Run the matching xxx_to_text.bat file. Open the resulting .txt file, and before doing ANYTHING else, add the line REGEDIT4 to the top, and have one blank line immediately following it, preceeding the rest of the file. Next, choose File --> Save As… and change the Encoding type to “Unicode”. Not Unicode Endian or Txt or anything else. Close the document and verify that your new .txt file is substantially larger than the original .hv file. If it is, you’re in good shape. Open it back up and edit to your hearts content.

When you’re finished, the steps to complete the process are: Delete the original .hv file in the Tools\HV Tools directory. Run the appropriate make_xx_hv.bat. Delete the resulting boot.rgu. Move the new xx.hv file back to SYS\Metadata and overwrite the original. Fin.
__________________