
11-07-2007, 08:29 PM
|
 |
Regular 'Geeker
Offline
Pocket PC: HTC Evo 4G Carrier: Sprint
|
|
Join Date: Jul 2007
Posts: 417
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
|
Quote:
Originally Posted by PRSPower
The way I am using OEM_Helper.exe is this:
(Taken from BigJ's Apache Kitchen Walkthrough + some blind stumbling on my part)
1. Use WinCE CAB Manger to Export Files to a properly named OEM folder (example Optional_YWReader_v2.51(11-6-07) )
2. Use WinCE CAB Manager to File>Export>Export to Reg... the Registry entries (I export the REG file to a folder other than the properly named folder stated above.
3. Fire up OEM_Helper.exe
4. Browse to the properly named OEM folder that you created. This is for the "Exsiting OEM Folder:" area.
5. Paste the contents of the REG file you Exported in step 2 into the "RGU File" area
6. Map the executable in the "InitFlash File" area
7. Fill in the "OEM Name:" area and the "OEM Description:" area
8. Click Generate
Now your OEM folder will have a .dsm, .rgu, initflashfiles.txt, and option.xml files, in addition to the files you exported in step 1
At this point copy your OEM folder into the C:\BuildOS\USER_OEM folder
Run BuildOS and you should see your OEM listed.
I may be way off on how all this works, but the above process has worked like a champ for me on two CAB files that I wanted as OEM's. It did not however work on the threading app that must not be named, so I decided to just keep that CAB on my miniSD and install it after the flash.
|
hmmm very cool.. so where does one get this oemhelper program =]
|