date/time - 11/03/2008 - 4:43pm response time - 2 hr customer Product - Mc9090 OS - BSP43 WM50 Case 1763309 Summary - Customer needed to update devices with new Fusion package. Custom Airbeam Osupdate package was generated to run from sd card which included the new Fusion build. When launched from lnk file, device and fusion updates successfully.  Customer needs this to work by launching the process through the cold boot/ trigger method. When this package is launched thru this method, the package partially loads, then the device is stuck on warm boot screen and have to reflash with osupdate package from website to recover. I sent issue to Paul Cowan/ Tom Mountjoy - below is response ~ Using the Laser trigger method to clean boot the device will cause the MS update loader to be directly invoked.  It is my understanding at that point the loader will look for a pkgs.lst file in \Temp and the Root of the SD card.  If one is found it will attempt to do the update based on the pkgs.lst file.
When you created the package in local mode there is a TXT file that is the OSUPdate response file.  When you invoke the update process by clicking on the short cut to invoke StartUpdloader a pkgs.lst file is generated from the response file and then the update process continues from that point.  The update loader will use the generated pkgs.lst file to complete the process.

  Given the package that you gave me and using the Laser trigger method to invoke the clean boot no pkgs.lst file will be in existence to be processed.

  I don't have an answer as to what actually happens at that point which causes the device to get stuck in the Warm Boot scenario.  However, OSUpdate is not involved in this particular scenario due to the Laser trigger process. 

  The bottom line is OSUpdate Package Builder local mode files are not designed to be used directly by the clean boot/laser trigger because it does not generate a pkgs.lst file.

  You may want to check with the OS/Device team to see if there might be additional files that could be provided with you package in order to make this scenario work. Or maybe they could explain what might be done to make this work the way you need it to.

Tom

This  is an issue that needs to be resolved because there will not be any further maintenance releases of the wm50 os and customers need to update fusion as fixes are released. Customer need to be able to accomplish this without intervention. This issue will be reoccuring.
any assistance or alternatives would be greatly appreciated.