Converting CAB to OEM when there is no Registry entries

[PRSPower]

I have a CAB file I am trying to convert to an OEM. I am following the "Apache Kitchen Walkthrough r1.0.pdf included in the latest Kitchen.

My question is this: The CAB I am trying to convert does not have any Registry entries and therefore I can not create a .REG file, change it to and RGU file per the instructions. There fore at the end of the process I do not have an RGU file in my OEM folder to rename with the UUID. Will this cause problems? or Should I make a blank RGU file?

Oh, ya, and a big thanks to everyone on the Kitchen team and to BigJ for writing up the "Walkthrough"

[JBabey]

Originally Posted by PRSPower

I have a CAB file I am trying to convert to an OEM. I am following the "Apache Kitchen Walkthrough r1.0.pdf included in the latest Kitchen.

My question is this: The CAB I am trying to convert does not have any Registry entries and therefore I can not create a .REG file, change it to and RGU file per the instructions. There fore at the end of the process I do not have an RGU file in my OEM folder to rename with the UUID. Will this cause problems? or Should I make a blank RGU file?

Oh, ya, and a big thanks to everyone on the Kitchen team and to BigJ for writing up the "Walkthrough"

no problem, and thanks!

anyways, if there are no entries whatsoever (even after you install the program.. for exporting) then yes, make a blank .rgu file with the same name as the UID you are using for that package and it will build fine.

Good luck!

[Perasite]

If it has no REG entries, I often just leave the .rgu out. That hasn't caused problems either. The .dsm must be there, though.

[PRSPower]

Thanks Yuma and BigJ. Got a couple of OEMs of my own to work. Also figured out the "OEM_Helper.exe" that was right under my nose. That thing makes it a breeze. Glad I did it the long manual way first because now I understand what the OEM_Helper is doing for me automatically.

[GaMedic]

How does the OEM helper work? Do your just drag your cab over and drop or what?

[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.

[superevilllama]

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 =]

[Kolano]

Originally Posted by superevilllama

hmmm very cool.. so where does one get this oemhelper program =]

It can be found in the OEMizer thread.

[gguruusa]

Originally Posted by 6700Yuma

If it has no REG entries, I often just leave the .rgu out. That hasn't caused problems either. The .dsm must be there, though.

Correct. An .rgu file is not required if there are no reg entries to be created/changed.

You will get build warnings/errors if the .dsm is not present or is incorrect (ie, copied from another module without builddsm having been run).

[PRSPower]

Originally Posted by superevilllama

hmmm very cool.. so where does one get this oemhelper program =]

C:\BuildOS\Help & Support Files\OEM_Helper.exe

It is installed by default when you install the WM6 kitchen.