![]() |
Re: Official Personal OEMizer Thread
how do i access those saved settings for later use?
thanx for any and all info on this great app! |
Re: Official Personal OEMizer Thread
They open automatically.. make sure it's actually creating OEMizer.ini in the tools folder.
If not, try running OEMizer as admin if you're using vista. That's the only thing I can think of that might cause it not to save to the ini file. I can't reproduce your same problem here. Everything saves fine wether it's run directly from tools or by the buildOS menu. |
Re: Official Personal OEMizer Thread
I'm using Win xp. i saved an oem and noticed there is no OEMizer.ini in the tools folder... upon further investigation i found my Oemizer.ini and build dsm in the same folder i got my files and cabs that i added to Oemizer. Those files are located on my storage drive with all apps,cabs and files.I know this is the key... do i have to move my source cabs and files to somewhere in the buildos folder?
|
Re: Official Personal OEMizer Thread
So.. with this I can take my .cab file of PocketCM and converted into a OEM to throw into my custom rom?
|
Re: Official Personal OEMizer Thread
Hey tiermann when will oemizer support adding a custom cert into oem for exchange server for those of us that use a self signed cert for exchange?
|
Re: Official Personal OEMizer Thread
http://blogs.msdn.com/windowsmobile/..._cab_file.aspx
If you follow those instructions and paste it into the provxml tab in oemizer instead of a setup.xml it should work in your build. I'll work on doing it programatically though. |
Re: Official Personal OEMizer Thread
Quote:
|
Re: Official Personal OEMizer Thread
Quote:
|
Re: Official Personal OEMizer Thread
wow. thats really cool.
props. |
Re: Official Personal OEMizer Thread
Tiermann, you should also note that although you can copy preexisting personal OEMs into the 6.1 kitchen, that the next time OEMizer is run it will have an error, since the explorer points to the c/buildos folder. I had to go into the ppckitchen.org folder and run it from there and create a new OEM to fix it. No big problem but I figured a heads-up was in order.
|
| All times are GMT -4. The time now is 01:42 AM. |
Powered by vBulletin® ©2000 - 2026, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com