[schettj]

Originally Posted by finster869

Sorry, didn't try it using those freewares. The method is pretty straight forward:

1. Extract all files (non-registry and shortcuts) to a folder.

This can be done with the freeware MSCEInf.exe
http://www.codeppc.com/telechargemen...nf/msceinf.htm
(Get the english version )
Simply extract all files in the CAB to a folder

2. Export all registries to a .reg file

With the above app, you will get a folder from the CAB - in the folder will be:
one or more folders
SETUPDLL.dll
Tools.inf
open the Windows folder
You're going to be using most everything in here, but you will be doing some work on it. You will not be using CheckFile.exe or __cusTSKTEMP.exe if they are there, and you will be using the contents of Platformxxx.reg (That's your registry entries!) and CM_Entries.xml (those are the ones that are going into your mxip_PACKAGE_REV.provxml file)

Ok - so copy all files except the above to your OEM folder, make a UNICODE reg file as in step 4 below and copy the contents of the .reg file into it, and make a plain text file named mxip_PACKAGE_REV.provxml (where PACKAGE is your package name, and REV is some 3 digit rev number) and copy the contents of the CM_Entries.xml into it. You do not need this proxml file if there is no CM_Entries.xml file, or if its empty.

Finally, look at the Customize.lst file in Notepad - it tells you where any addition files are in the CAB - for example if it says
\temp\PhoneSetting.htm
Then that file (PhoneSettings.htm) will be in the temp directory one up from Windows... so copy those files to your OEM folder too... and you'll then need to copy those files via initflashfiles.txt to their correct locations... often the correct location will be in the CM_Entries.xml file, so you can edit the move operations out of there and just put the right moves into initflashfiles.txt

Example:

Customize.lst :

 \temp\PhoneSetting.htm

CM_Entries.xml

<wap-provisioningdoc>








	<characteristic type="FileOperation">
		<characteristic type="\Program Files\IOTA\jTelDll.dll" translation="install">
			<characteristic type="Copy">
				<parm name="Source" value="\temp\jTelDll.dll" translation="install"/>
			</characteristic>
		</characteristic>
		<characteristic type="\temp\jTelDll.dll" translation="install">
			<characteristic type="Delete">
				<parm name="ForceDelete"/>
			</characteristic>
		</characteristic>
	</characteristic>

	<characteristic type="Registry">
	<characteristic type="HKLM\Software\Apps" translation="filesystem">
		<parm name="CabName" datatype="string" value="IOTA_v1_10" translation="filesystem"/>
	</characteristic>
	</characteristic>
</wap-provisioningdoc>

In this case, we will not use ANY of this, but it does tell us what we need to know... that the file \temp\jTelDll.dll in the CAB needs to be in \Program Files\IOTA\jTelDll.dll on the device...

initflashfiles.txt

Directory("\Program Files\IOTA"):-File("jTelDll.dll","\Windows\jTelDll.dll")

Phew!

Now, back to the checklist!

3. Get a UUID number from http://kruithof.xs4all.nl/ (click on 1st link).
4. Open reg file with notepad and save as unicode, all files, with the UUID number .rgu as the name (xxxxxxx.rgu).
5. Open notepad and save a blank file unicode, all, with the UUID number.dsm (xxxxxx.dsm).
6. Make your initflash.txt file with any necessary shortcuts.
7. If you made a shortcut, then make the linkfile by opening up notepad and typing 25#"MemMaid.exe" or whatever. Save the file unicode with the name of the .lnk file from the initflash.txt file (i.e. MemMaid.lnk).
8. MOve the folder to OEM and you should be good to go!!!

I hope to be able to write up a better guide to the CM_Entries.xml stuff, as its kinda important to read it, delete what you don't need, and include what you do, but you get the general idea (hopefully!) and can start poking around with this.