Cab/OEM to fill out owner information and OEM of mail2web se

[takmsdsm]

Is there a way to set up a cab or OEM to fill out the owner information in a rom?

also, someone who is able to make OEMs, anyone interested in making an OEM for my Mail2Web config cab?


Thanks in advance.

[m2maynard]

I think JBabey's custom kitchen has a reg entry that adds some changes to the kitchen registry. It is under Z_Custom or some such. A little technical but possible. Utilize the search and get your hands a little geeky with the rest of us and you should figure it out.

It is possible to do the OEM of the owner information. I have actually customized jbabey's reg hacks for myself including the owner information but have yet to flash the new rom.

I will post again when I do that.

[colonel]

you can use an rgu to setup the personal stuff and you can use a provxml to setup mail2web. Unfortunately, I am heading out of town for the weekend so you may have to wait a couple days on the provxml stuff.

[drdrewusaf]

For simple registry stuff I have a CAB in my EXT_ROM to install all of my personal stuff like registration codes, owner info, and program settings. IMO, using a CAB in the EXT_ROM makes it easier to change things. So, instead of changing an rgu, rebuilding the rom, and reflashing; all I have to do is edit the CAB and hard reset.



Drew

[luv2chill]

For owner information what you need to do is fill it out on your device, and then use a registry editor like Resco or Task Manager (which is free) to export this key:

[HKEY_CURRENT_USER\ControlPanel\Owner]

In particular you need the "Owner" value...which appears in the form of a hex block. You will also see your owner information in clear text in other fields but exporting those only will not work. The hex block is the only thing that works.

If you've filled out anything in the notes field then you'll also need to grab the value called "Owner Notes".

Export both of those reg values, slap into an rgu file in your own "Customize" OEM package, and you'll never have to type that crap ever again.

And yes it's possible to set up e-mail accounts using xml (it is not possible to do via the registry directly--something I had to learn the hard way). That is how the mail2web cab does it--there's just an xml file inside that gets parsed.

To use xml in an OEM package you have to convert into something called provxml (short for provisioning xml). These files were designed to be used by carriers to set up devices for end users, but we can use them too.

There is a lot of cool stuff that can be done with provxml. The tradeoff is that the Configuration Manager (which is what parses the files) is extremely picky about syntax, and any error in the file will cause the whole thing to be thrown out.

I'm planning to do a writeup in the wiki about how to use and troubleshoot provxml... just haven't gotten around to it yet. In the meantime there's lots of info out on the web if you google provxml--that's basically how I taught myself.

To start out with, you can extract the xml file from your mail2web cab and rename it like this:

mxip_abc_123.provxml

where "abc" is some kind of descriptive word and "123" is the version number of the file. You can pick anything you want, but to aid your sanity I suggest incrementing that number anytime you make a change to the file so you can revert back if necessary.

There are some provxml files in the kitchen already, which you can search for (*.provxml) and use as examples. Have fun!

[Kolano]

Originally Posted by luv2chill

There are some provxml files in the kitchen already, which you can search for (*.provxml) and use as examples. Have fun!

I see this in mxipcold_oemoperators_1001.provxml

	<characteristic type="FileOperation">
		<characteristic type="\Windows\Start Menu\Downloads.lnk" translation="install">
			<characteristic type="Copy">
				<parm name="Source" value="\Windows\Downloads.lnk" translation="install"/>
			</characteristic>
		</characteristic>
		<characteristic type="\temp\Downloads.lnk" translation="install">
			<characteristic type="Delete">
				<parm name="ForceDelete"/>
			</characteristic>
		</characteristic>
	</characteristic>

Can you briefly describe what the "delete" command can do.

[ImCoKeMaN]

For mail2web settings save the following to "mxip_mail2web_101.provxml":
(change "YourPassword" and "YourEmail" accordingly)

<wap-provisioningdoc>
   <characteristic type="Sync">
		<characteristic type="Settings">
			<parm name="BodyTruncation" value="1024"/>
		</characteristic>
 		<characteristic type="Connection">
			<parm name="Domain" value="ad2"/>
			<parm name="Password" value="YourPassword"/>
			<parm name="SavePassword" value="1"/>
			<parm name="Server" value="mobile.exchange.mail2web.com"/>
			<parm name="User" value="YourEmail@mail2web.com"/>
			<parm name="URI" value="Microsoft-Server-ActiveSync"/>
		</characteristic>
		<characteristic type="Mail">
			<parm name="Enabled" value="1"/>
			<parm name="MailBodyTruncation" value="1024"/>
			<parm name="MailFileAttachments" value="1024"/>
		</characteristic>
		<characteristic type="Calendar">
			<parm name="Enabled" value="1"/>
		</characteristic>
		<characteristic type="Contacts">
			<parm name="Enabled" value="1"/>
		</characteristic>
		<characteristic type="Tasks">
			<parm name="Enabled" value="1"/>
		</characteristic>
   </characteristic>
</wap-provisioningdoc>

Just copy that in with wordpad and save it to an OEM folder (if using the new kitchen you'll need to run builddsm.exe again too)

Enjoy!

[takmsdsm]

you guys rock!

[luv2chill]

Originally Posted by Kolano

Can you briefly describe what the "delete" command can do.

Sure... it can delete files so long as they aren't in ROM. It's useful for use in xml files that are in cab files as it can delete temp files used by the cab install.

But it has very limited use in the provxml context because at coldinit (when the provxml files are parsed) there's nothing that's not in ROM (only things would be the shortcuts and other files copied with initflashfiles). So nothing much to delete at that point.

[ImCoKeMaN]

Just found out (through not getting email) that the mail2web settings for the "new core" from helmi (newest kitchens) require the "WM6" user ID settings. These are of the type: "username_mail2web.com" but truncated to 20 characters you might want to check for yourself on their help site though. I was previously still getting the contacts to sync so it looked like it was working, but the email wasn't being sent or recieved.