For those that need a personalized OEM for their ROMS!!!!!

[boyo]

Have you thought about integrating activesync setup too?
Should be fairly easy, just disect the mail2web cab and recreate it.
I have an OEM that I created to setup my activesync when reflashing so i know it's possible.

[luv2chill]

You need provxml to set up connections and mail accounts. Not sure if this app does that already but should be fairly trivial to generate based on user input of server, user name, etc.

[xmind2006]

Just trying this out to re-build my 1.04 ROM and got an error about the power settings when it tried to create the OEM. It errored out saying can't convert "30 secs" to double. The 30 secs was what I selected for the backlight time out.

Not that it takes that long to fill out the stuff, but could I request a "save settings" or such that once I close Personal OEMizer that it'll re-open with my last settings?

Just a thought, otherwise a very cool and user-friendly app.

[tiermann]

Should be fixed now. I had it looking at the value of the wrong dropdown so it didn't know wtf to do with "30 secs" hehe.

It's updated on my site and the ftp here.

I'm still working on the ability to save your settings (hence the slightly different look on the toolbar now) and it will have the option to "Save settings as default" or "Always save on exit" when I'm done.

[xmind2006]

Cool, thanks for the quick update.

After flashing, I did notice the homepage didn't get changed as to what I specified in the OEMizer. However, I'm not sure this is a fault with the OEMizer as it could have been reset by one of the other OEMs.

[tiermann]

Another update...

You can now save your settings as default or choose to always save settings on exit. The options are located in the "Create OEM" dropdown.

It will save all settings that are Checkboxes, Dropdowns, Sliders, or Single-Line Textboxes to OEMizer.ini and reload them on next run. Any other settings like the files list (listboxes) or additional registry entries (multiline textboxes) are not saved yet. I'll eventually be adding those in too, but for now this should make it a little quicker to resume what you were doing.

[sethlo]

Can someone (Teirmann?) give me a little guidance on using the Autorun setup feature in OEMizer? I think that in the text field I should include something like the following sample I found in one of Colenel's roms:

LOCKisabled
CPY1:\Storage Card\Boot\NameOfCab.cab
CPY2:\Windows\NameOfCab.cab
CAB: \Windows\NameOfCab.cab
CPY1:\Storage Card\Boot\mail2webActivesync.cab
CPY2:\Windows\mail2webActivesync.cab
CAB: \Windows\mail2webActivesync.cab
CPY1:\Extended_ROM\config.txt
CPY2:\Windows\Config.txt
LOCKisabled
RST: Reset

However, I am bit confused by the "Full Path To Autorun" and "Full Path to Config.txt" fields. Am I right that these fields ask for where Autorun (the program with the grey square and hammer icon?) and Config.txt are going to go on my Apache? Or is it asking for where OEMizer is going to get these files from?

Please let me know if I am on the right track here. Everything else in OEMizer seems pretty self explanatory to me. Btw, Tiermann, thank you for your work on this program; it seems great and I look forward to giving it a try. I am sure this must be more simple than I am making it. Also --- just had this thought --- maybe some sample text to use as a template would be good in the text field in the Autorun section???

[tiermann]

The paths in the Autorun section are the paths on the device (Ex: \Windows\Autorun.exe) and to add the autorun.exe to your OEM you'll need your own copy of it (which can be found in the zip in the first post in this thread) added to the Files & Shortcuts section.

OEMizer will generate the Config.txt (from your input in the textbox) and put in in the OEM during the "Create OEM" process. It will automatically be in \Windows\Config.txt. You'll just need to add it to the initflashfiles.txt manually afterwards if you want it somehwere different.

Make sense?

[sethlo]

Originally Posted by tiermann

The paths in the Autorun section are the paths on the device (Ex: \Windows\Autorun.exe) and to add the autorun.exe to your OEM you'll need your own copy of it (which can be found in the zip in the first post in this thread) added to the Files & Shortcuts section.

OEMizer will generate the Config.txt (from your input in the textbox) and put in in the OEM during the "Create OEM" process. It will automatically be in \Windows\Config.txt. You'll just need to add it to the initflashfiles.txt manually afterwards if you want it somehwere different.

Make sense?

Ok, I think I got it. Does this sound right? -- OEMizer will put config.txt in the OEM folder it builds. If I leave it there and if I put Autorun in the personalized oem folder after the folder is built by OEMizer, then I should make the paths go to \Windows\Autorun.exe and Windows\Config.txt. (Because that's where the items will go when I flash the phone).

Or, I could place my copy of Autorun on my storage card or in my ext rom along with config.txt and change the paths accordingly. (perhaps this will save a little memory for other things in my rom).

Please let me know whether or not this is correct. Sorry if I am being a little didactic, but this is new to me. Thanks again.

edit: I'll need to change my initflashfiles.txt if I put autorun in my personalized oem folder to tell it to put it in \Windows. if that's where I want it to go. Likewise, I'll have to change initflashfiles.txt if I move config.txt. Right?

[tiermann]

Originally Posted by sethlo

Ok, I think I got it. Does this sound right? -- OEMizer will put config.txt in the OEM folder it builds. If I leave it there and if I put Autorun in the personalized oem folder after the folder is built by OEMizer, then I should make the paths go to \Windows\Autorun.exe and Windows\Config.txt. (Because that's where the items will go when I flash the phone).

Or, I could place my copy of Autorun on my storage card or in my ext rom along with config.txt and change the paths accordingly. (perhaps this will save a little memory for other things in my rom).

Please let me know whether or not this is correct. Sorry if I am being a little didactic, but this is new to me. Thanks again.

All that is correct.

Originally Posted by sethlo

edit: I'll need to change my initflashfiles.txt if I put autorun in my personalized oem folder to tell it to put it in \Windows. if that's where I want it to go. Likewise, I'll have to change initflashfiles.txt if I move config.txt. Right?

If you want it to go in \Windows then it won't need to be added to initflashfiles.txt. All files in the OEM folders automatically go there. The only time you'll need to add a file to initflashfiles.txt is if you want to copy it to another folder other than \Windows itself.