Official Personal OEMizer Thread
 

Personal OEMizer is a windows desktop application for use with Apache kitchens.
With OEMizer you can create an OEM with personal settings to include in your custom ROM builds, like your owner info, inbox settings, etc.

Aside from being able to add registry tweaks, you can also import cab files for quick cab to OEM conversion.

Usage:
1. Download and unzip OEMizer.exe to your kitchen\Tools folder.
2. Run OEMizer and set any options you want to include in your OEM.
3. Hit the "Create OEM" button to build the OEM straight to your kitchen.
4. Run buildOS and include your new OEM in your ROM.

Any other questions or problems, please post here and we'll troubleshoot.
You may want to check this thread first as your question may have been answered in earlier deveopment.

Download OEMizer

I also have other applications available on my website: http://tiermann.net

You may also be interested in Tier Autoinstall which is a front-end for autorun.exe customizations. All links can be found in my signature.

Reminder: Please look through your rgu files and initflashfile.txt before using a generated OEM. Importing cabs is not perfect yet, but it will give you a good starting point.

http://img258.imageshack.us/img258/1888/oemizeret0.png
Changes

--1.3.8
-Fixed the problem with spaces in the folder name during buildDSM.
--1.3.7
-Fixed cab importing that I broke in the last release.
--1.3.6
-Added Tasks to exchange settings. This will only work if the server supports tasks.
--1.3.5
-No longer uses cabLib.dll. It shells to expand.exe to extract/import cab files. This should fix 64bit compatibility.
--1.3.4
-Fixes autoloading of settings.
--1.3.3
-Added Help to dropdown menu in menubar.
-Added help file. Also mirrored at http://tiermann.net/OEMizerHelp
-Removed speeddial from Phone & Data section until I have a chance to look it over.
--1.3.1
-Added option in Files&Shortcuts to add a Security\AppInstall RGU entry for each exe and dll on the list. Should fix "not signed with a valid certificate" problems some people may have had when running apps.
-Fixed RGU errors when a reg entry has quotes inside of quotes. It now uses the proper \" for escape character.
--1.3.0
-Fixed button mapping.
--1.2.9
-Added speeddial to the Phone&Data section. (saves in oemizer settings and uses provxml)
-Cleaned up "save" code to more easily add new items.
--1.2.8
-Cleaned up the navPanel code to make it easier for me to add new sections.
-Added "Provxml" section to the OEM Info group. You can add extra provxml entries there or drag n' drop a provxml into the textbox.
-Drag n' Drop also supported for reg and rgu files in the "Additional Registry Entries" box.
--1.2.7
-Fixed data disabling and added all the current carriers. (Uses provxml now)
-Fixed today theme not setting on first boot for the most part. Still may not set sometimes but that's due to windows having a sloppy method of startup.
-Added the ability to set sounds for events in Sounds & Notifications. (and yes, they save in your oemizer settings too.)
--1.2.6
-Fixed error when importing a cab that has a "type" in it's setup.xml with fewer than 5 characters.
--1.2.5
-Added Mail2Web/Exchange option for mail size.
-Added Mail2Web/Exchange option for mail attachment size.
-Added Mail2Web/Exchange options for note size (in contacts and calendar).
-Added Mail2Web/Exchange option for sync frequency.
-Fixed PIE homepage setting.


Known Issues I'm Working On:
--Not all settings are saved for the next time you run OEMizer. It's not a bug, it just hasn't been written yet. (most settings and even multi-line textboxes save now, so it's getting there)
--Some registry settings converted from cabs are set as dword instead of hex.
--Adding speeddial #'s doesn't seem to stick for first boot.

Future additions:
--Ability to set duration, enable/disable, etc for each sound
--Alternate DNS settings for data connection.

Thanks, perfect time to try it out gotta re-flash this weekend. sounds like just what the doctor ordered to make the job a little easier! I'll let you know how it goes.

First report.....Tres' cool. Great app!

Awesome thanks.

Can't wait to try this out, thanks for your work!

Got the first bug report. I set it to skip the digitiser calibration, and it did skip it. Totally.
Had to nav with the joystick to the screen calibration and do it manually. For some reason it also went straight to add contact and wouldn't close the contatcts app till I made a bogus contact. Everything else that I've set with it works like it should. I must always add the disclaimer that it could have been some bonehead thing that I did....

Here is a hint if you ever need to recalibrate--push in the joystick while tapping the Windows key and it will bring the calibration screen right up.

And calibration values should be roughly the same between Apaches but they can and do vary. Your best bet to get very accurate calibration data is to perform a careful manual calibration and then export that data from the registry:

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"CalibrationData"=

It will be a string of ten numbers. You can then put that in the rgu file that tiermann's app creates.

Thanks luv2chill for the help and the great hint! I didn't know you could go to calibrate that way. I'll probably have to redo anyway, getting an error when yagoo go! starts...

Nice work buddy. Thanks for putting the time into this for everyone.

I might have to take that calibration option out because the default I put there doesn't work for everyone. Sorry about that. It was more experimental to see if you could actually skip the entire calibration and time sections. What you could do though is after you've calibrated, look in your registry for the same key...

... export it and replace the one in the rgu file of your OEM. That should give you correct calibration. I think over time/wear/usage the calibration will change though.

(as Luv already said :))
------

And you're welcome all. Glad you're finding it useful. Thanks for the feedback.

I just set it to not skip the digitiser, and all else works for me. It's nice to have personal info, today settings, and timezone preset. It still saves a lot of time of re-setup after flashing. I plan to test it some more -w- my guinea pig 6700.

I'm gonna look into this, looks like a lifesaver!

Bump
 

My personal OEM is working just find on the new WM6 kitchen

Kitchen Version 1 or 2? What settings are you using?
I couldn't get it past the second bootscreen (version 1) until I eliminated my personal OEM from the build...
I'm not sure if it was Oemizer, or the Kitchen at this point. Gonna try the latest version with both kitchens, and post with my results.

Kitchen V1
MSVC was giving me the white screen.

I wasn't getting the white screen. It never got that far the first couple times. Just to test I let it sit for at least 30 minutes. When I did get it to boot all the way MSVC was installed (as an OEM) and worked fine.

A question that I think is stupid, but I'll ask anyway.
I was lazy and didn't read the directions where it said to unzip the file into the Tools folder of the kitchen. I just ran it from the folder that it got unzipped to and it created two files. Neither of which looks like an OEM file. :disgust:
Am I just going to have to go through the process correctly or is there a way to just drag those two files into the appropriate folder?

Thanks for your patience and hard work with a cool idea.

It saves your OEM to "..\OEM\YourOEMNAME" so look one folder up from where you have oemizer.exe and there should be a folder called OEM now, hehe. Your new OEM is inside there. I would just save your settings, move oemizer.exe, cab10.dll, and the OEMizer.ini to the Tools folder of your kitchen and rebuild it though because it couldn't have possibly run buildDSM on the finished OEM since it wasn't in the tools folder.

Ahhh, ya beat me to it! I did the same thing the first time I used it......

Thanks. I got it working and it seemed to work properly, but I got the following error when using the v0.4 Kitchen...
Quote:
Originally Posted by Trident http://forum.ppcgeeks.com/images/sty...s/viewpost.gif
Error building default.hv and user.hv.
Goes away when I unselect my customized setting OEM created using OEMizer.


That's not the kitchen, that's your RGU file in your oem...
3 rules to making rgu files:
1) use notepad, not wordpad, and save as unicode.
2) Put Regedit4 as the first line of the file
3) leave 1-2 lines empty at the end of the file.
__________________

If you could find the bad lines (the line number that gave the problem should be at the bottom of kitchen\temp\log.txt) and post them here I can fix that up.

All of the rules are used, but most likey the syntax is like 1 character off on one of the reg keys that oemizer is trying to add, which is a lot to sort through, hehe.

I ran into the same problem. Here is the error I get at the end of temp\log.txt:

Failed to parse value name HKEY_CURRENT_USER\init!!!
InitRegistry FAILED in file ".\Registry\ffffffff-a5d4-4471-857c-d3efe40b1acc.rgu" within a few lines of line 111.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\ffffffff-a5d4-4471-857c-d3efe40b1acc.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives

k. that looks like the new code I put in for today theme. I'll fix it up and update this post when the download is updated.

For now, you can remove that [HKEY_CURRENT_USER\Init] entry and the line below it from the rgu and you _should_ be good to go.


Updated and fixed. Link is in my sig.

Yes, I took that line out and it works. Thanks for your work on this - it is going to save loads of time for us frequent ROM-upgraders!

You're welcome. And thanks for posting the log.txt :) Makes finding the problem a lot easier.

I've downloaded & ran the .exe just to check it out briefly........is there a way to build/populate your pop3 accounts? That's my biggest gripe when frequently flashing.....having to setup multiple pop3 accounts.

thx & nice program!

I'm still having the same issue.
Is there a log or something that I can show you?
All I am seeing is the error message (which disappears when I don't include that OEM in BuildOS).

There seems to be a problem with the today settings. every time I include that in an OEM It fails at the build registry and I get unable to build rgu errors. This is with the latest version, downloaded today.
this is part of the log:
importing registry file ".\Registry\ffffffff-a6c3-4268-8212-e7038bfcccdd.rgu"...
Failed to parse value name HKEY_LOCAL_MACHINE\init!!!
InitRegistry FAILED in file ".\Registry\ffffffff-a6c3-4268-8212-e7038bfcccdd.rgu" within a few lines of line 98.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\ffffffff-a6c3-4268-8212-e7038bfcccdd.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives

pop3, This would be nice, setup 4 myself as well.

tnx

Today settings fixed. Sorry.. I was still missing double slashes in the path for cusTSK.

For Pop3 at the moment, a provxml imported to a cab file would be the best way to go.


In the next few days I'll have timezone fixed as well, so you shouldn't get asia for gmt -6, etc.
That should make "skip welcome/customizations" more useable, provided you have your proper calibration string.

Thanks for the Today fix! I reflashed with the non-today version on my active 6700, but want to try it out with the "New" new WM6 kitchen.

When I run the program and put in OWNER INFO and place an address in the box, and save "settings as the default" and re-run the program it is not there. Also it does not show up in the .ini file (address).

Change log shows newest version as 1.1.4 but the link says 1.1.3 (and you don't include the file version in your filename). FYI.

There are still some problems. When selecting timezone in the prg it says central US. On the PPC it says central Canada, eh...

--1.1.5
-Timezones should be correct now.
-Added additional items to "OEM Info" section for new version of buildOS. (still compliant with old version as well)
-Now using CabLib.dll instead of cab10.dll
-Added version to titlebar.

I tried to add cab and they dont seem to migrate into the ROM.
Any suggestion?

I think this should be ioncluded into the kitchen, JMO

if the files made it to the oem, they'll make it to the rom.
Not sure what you mean.

I've been working with the kitchen crew also to get it ready for release. The most recent version will be included :)

Thanks for the autoinstall.
Ive been lookin for something just like that.
I was tryin to find a copy of colonels old ROM that had something just like this.
Any how thanks. you should start a thread on it.

I guess I misunderstood the instruction. I dragged and dropped cab file into the box. :) I didnt know it was for OEMs

thx tiermann, how/where would someone do this?

thanks again