[rstoyguy]

Advanced Topics: Importing Program Settings
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Reserved for later...

Advanced Topics: Setupdll.dll
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This file sometimes has some additional code that will run doing a .cab install. When installing a .cab on Windows Mobile, there are four "Hooks" that winmo looks for when dealing with .cabs. There are only two that we are concerned with. There is a "hook" that is called before the .cab is installed and another one after the .cab is installed. If this file is present, more than likely there is something more and YOU WILL HAVE TO MANUALLY EDIT YOUR OEM.

Etiquette Note: This file is almost always and exclusively used in this fashion, and some PPCGeeks etiquette...If an OEM contains this file, it is considered a "poorly" put together OEM. This file will also almost always create that "Duplicate File" error is BuildOS (or whatever else you use) so just get rid of it!

Here are some things it can do:
MemMaid: Calls that little help screen (harmless), PocketTunes: Displays a license agreement (harmless), WeatherPanel: UnZips all the graphics files, Touchpal: Prompts you for your device type and then copies the VGA/QVGA files depending on your choice... Those are just a couple, thank goodness that this is not used much, but it is out there.

How to defeat it:
You will need to install the .cab to your device, preferably to a clean rom. Then you will have to match up the files from the OEM to where the files were installed on your device. Then edit the initflashfiles.txt, and files in your OEM to make the changes. I'm not going any further with this, YOU will have to figure it out. There are just too many variables and it just takes experience... You can always visit one of my oem requests threads and request it. If you ask I will actually post the "trickery" I found briefly.


Advanced Topics: Adding multiple files using OEMIzer (Good for Skins-n-Things)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I don't use the OEMIzer much, but I have found it a very good use for it. Say you are wanting to install a skin that installs all the files to \program files\weatherpanel\skins and all you have is a zip file with those files. Here is a brief how-to do that...

Create in your oem-making directory a directory called ..\oemizer, the inside create two directories, ..\oemizer\oemizer and ..\oemizer\OEM. Copy the 3 oemizer files from one of blank kitchens (found in my Adding/Removing Programs Tutorial in my sig) into the ..\oemizer\oemizer directory.

Now that your prepped, let's do it!
Open up OEMIzer and move the window to the left side of the screen, then open up a windows explorer window and move it the right side so you have the two windows open in a side-by-side style.
In OEMIzer, click the "Files and Shortcuts" tab and make sure its checked.
Next, from your file explorer, select and drag-n-drop those files into the OEMizer window.
Now in OEMizer, select all the files in the window.
Down below in the box that says "\windows\", change this filename to where you want your files installed. Be sure to put a trailing \, so it's "\program files\weatherpanel\skins\".
Now click the "edit" button. You should see that this changed all the items in the window.
Now your ready to make the OEM, so click the Green globe above that says "Create OEM".

Your oem was created in the ..\oemizer\oem directory. Now what I do is copy the files into the OEM I was creating, and APPEND the contents of the initflashfiles.txt from the newly created OEM into the one I was originally working with.

It can be a pain to manually create an initflashfiles entry when your skin is 400+ files, I've found this to be a huge timesaver!