Sometimes the sdk installer will need a reboot if it encountered locked files during the installation. A change will soon be made to the sdk installer, in which it will write to a temp file which will state if it needs a reboot or not. After calling the sdk installer, the cobundle installer should check this file to see if the machine needs a reboot. If the file says it needs a reboot, the end of the cobundle install should prompt the user to reboot the machine.

Up until Merlin beta3, the sdk installer has never detected whether it is in SILENTMODE. The final dialog box has always either shown a need for a reboot or a finishing dialog allowing the user to see a readme file. This problem will result in many failures of silent installations. See new hotbug 4522933 for a better explanation of this.

This problem exists in the cobundle with Merlin beta2, although it seems that it hasn't been caught by anyone yet. There are plans to cobundle forte with Merlin beta3, which still has this problem. The problem is that it is too late to change the beta3 installer code. One solution would be if we can gaurantee that the installer prompts the user for a reboot, the setup.iss file can expect the same dialog boxes every time. We can do this by bundling up the plugin140.cpl file with the cobundle installer. The cobundle installer will copy this file to the windows/system32 directory and open the file. It will therefore be locked by the OS because it is in use. The cobundle installer will then run the sdk installer silently, which will try to copy this file and detect that it is locked. Because of this, we can gaurantee that every cobundle install will need a reboot. This can be a temporary solution until we get the fix for bug 4522933 integrated into Merlin rc.

###@###.### 2001-11-05