Tiermann, will this help me create the provxml for my mail2web account? It's Exchange, not POP or IMAP so that's why I ask.

Thanks tiermann for you improvements. It helps greatly to be able to save pop settings. Unfortunantly my ISP doesn't allow email to be sent through another provider (charter) so I have to use Verizon smtp to send mail. I have to go in and manually configure smtp.vzwmail.net and username and password for my verizon account to send. Do you plan in the future to add smtp config in the oemizer?

The option isn't available in provxml to add a different user/pass for outgoing. It'll just use the same pw for authentication, etc too, so that unfortunately means I can't do it in the same way. I'll look into it though and see if there's some other way to input it.


Almost :) Next version will have a Mail2Web/Exchange section. I have a provxml template all laid out and is actually a resource in the current version. I'll have the interface done by next release.

thx again tiermann for getting the pop3 work. I created 4 pop3 accounts, and sure enough they were there after flashing.....I did have to populate the email addy field & also had to tweak some settings in each, but still a time saver!

thx much!

Very cool, thanks Tiermann!

Tier.
On the autoinstaller program, can you make the default install folder the extended ROM? Any plans to merge the autoinstaller with the OEMizer? I like the autoinstaller but I would prefer to use the ext ROM storage first..

If this was merged into the BuildOS, so you fill ever thing out in the buildOS and make all the choices in one stop would be a complete package.

Where are the instructions for the auto installer?

I don't think there is a way to make autorun install to ext_rom. It just goes with the default directory specified in the cabs. You might want to edit the cabs themselves with WinCE Cab or something similar to point to extended rom instead of program files.

http://tiermann.co.nr/tauto
You can ignore the usage part because it's already included in the kitchen (customization section) and the cpacks i made for carriers are outdated since the kitchen release.No need for them though unless you're trying to put out a Generic rom.
I'll have to update those and they can simply be put in a new user_oem to work just the same.

All it is really is just a front-end for the old autorun since it doesn't get used anymore with built in carrier customizations.

Normal usage instruction when including Tier Autoinstall from the kitchen go like this...
1) It will pop up on first boot with a list of cabs it found.
2) You can pick which cabs you want to install by checking the box next to each one.
3) You click "Install" and it will rewrite the config.txt and run old autorun to install the cabs.
4) It will soft-reset once and you're good to go.

I saw it in cutomizatios section but don't understand how to use it. Is this where the section in OEMizer that cabs are added come into play?

No.. this is for cabs that you don't want to (or there's really no point to due to size or layout) convert to oem. Just dump them all on your storage card and they'll show up on the list to install all at once on first boot without having to click "install to" etc for each one.

SlingPlayer is a good example because it contains ~257 files and can't be cut down to run from one directory. GoogleMaps is another one you won't want to turn into an OEM because it won't let you run the program if a newer version is available.