Updated version of the document and inclusion of the two special DLL files.

Chris; One very important thing that may not be obvious about this approach is that it relies on the actual OS Update NOT erasing the Application Partition.  This is because the CAR/GAR file is processed and does its modifications to the Application Parition BEFORE the actual OS Update is performed.  If the OS Update then clears the Application Partition, then all that content will be lost.  Since there is NO LONGER any way to create an Application Partition with pre-built content, there is no way around this since the OS Update process cannot load an image of the Application Parition. There are two main implications of this.  The first is, you MUST NOT include anything (such as the Clean and Blank files for WM) as part of your OS Update or you will cause this condition.  The second is, if the OS Update causes the Application Partition to be cleared, then you are pretty much out of luck.  In most cases, this will only happen when moving from one MAJOR OS version to another (e.g. WM5 to WM6).  It generally happens when the size of the Application Partition had to change, such as when the OS itself got bigger.  Only the device team that produced the OS Update can tell you for sure whether this will happen when applying a given OS Update to any specific prior OS. In some cases, such as moving from WM5.0 to WM6.1, there were special multi-step processes that were developed to circument these limitations.  But such processes generally required that OS Update Packages be specially built and DID NOT allow for general pre-loading of the Application Partition.  Instead, they preserved key information that could allow a management system such as MSP to deploy the OS Update, retain manageability across that update, and redeploy the Application Partition contents AFTER the OS Update.  Such solutions are also generally VERY specific to particular families of devices. Allan