Another update...

I posted a newer version of the exe on the ftp. The only categories that will give you output to the RGU right now are Calibration, Owner Info, Sounds & Notifications, Bluetooth & Beam, and Phone & Data. When you press the "Text Only" button it will create (or overwrite) a PersonalOEM-RGU.txt file in the directory you're running it from that should reflect your choices in REGEDIT4 style.

The Today&Appearance panel is pretty non-functional right now, but nice to look at, hehe.

The "Additional Files & Shortcuts" panel is working too, so you can mess around with that and see how you like it. It just doesn't generate initflashfiles.txt yet. Filename is the file the original file will be copied to when it's moved to your OEM file, and destination is where it will end up on your PPC, so you can easily have it copy files to say "My Documents" or something after the flash. So all three of those filenames can be different, just like in initflashfiles. The file list also supports multi-select so you can change a bunch of files destinations at once if you need to.


Edit: Updated the file on the ftp again.
All panels except "Today" and "Map Buttons" work. I still have the "Create OEM" button disabled, but the "Text Only" button will now give you a "PersonalOEM-RGU.txt" "PersonalOEM-Config.txt" and "PersonalOEM-initflashfiles.txt" in it's current running directory, depending on which categories you have chosen.

Looks great. Just to keep in mind, and you may already have this in the works, but the .rgu must be in Unicode. Right now the text files are in ANSI. I really like where this is going.

Thanks, Yuma :)

I forgot to set the encoding for the file, but it's fixed here and will be in the first release.

how about a small mouse over pop up description for each selectable item?

Looks good 8)

Newer test version on the ftp, same place.
All panels work now, and it gives you a log on the OEM Info panel after you hit the "text only" button. Pretty useless info, but it tells you what file it outputs which info to anyway. That log will also contain the list of copied files, etc, once "Create OEM" is available.


Things left to do:
- Make it generate an option.xml
- Create a subfolder in your kitchen\OEM
- Place all generated files there as well as your added files.
- Run buildDSM


All those will be automated when I finish up. As it is, you can use this program, but you just have to do all the above stuff manually.

This looks pretty done. It's fully automated and does everything I wanted it to.
Other than that, give it a try. All of the "Things to do" in the above post are done ;)

OEMizer.exe MUST be placed in your Kitchen\Tools folder if you want to create an oem.

Things left to do:
- Add a check for duplicate file names in your "Files & Shortcuts" list. For now just take a look through and change the file name of any duplicates.


Other ideas I have for future versions:
- Importing cabs (if it has a _setup.xml) including any files and reg settings

OK I put it on the tools folder and ran the program. Then I cooked a ROM and it didn't have any of my settings.

What did I do wrong?

Double check kitchen\OEM\YourPersonalOEMfolder to make sure it generated everything.

When I run the app. I get this error


C:\
This application has requested the runtime to terminate it in an unusual way. Please contact the application's support team for more information..

buildDSM has encountered an problem and needs to be closed.

Is that right away when you run the program, or after hitting "Create OEM"?
BuildDSM shouldn't run until after you hit the button. Do you know if the error is coming from buildDSM itself, or OEMizer? Should be in the titlebar of the error.