During the sdk installation, the last dialog box will differ depending on whether the customer need a reboot or not. If the user needs a reboot, the last dialog box will ask them if they want to reboot now or later. If the user doesn't need a reboot, the dialog will ask the user if they want to see the readme. This behavior is fine for a regular sdk installation, but it is problematic during silent installations of the sdk. The setup.iss response file is expecting certain dialog boxes in a certain order. If it could be different depending on the system configuration, the silent installation will completely fail and the sdk will uninstall completely automatically.

The sdk installer should work exactly how the jre installer works. It detects whether it was invoked in SILENTMODE and if so, it won't show the reboot dialog box. Instead, it will write to a temporary file whether it needs a reboot. The installer that invoked it checks that file and reboots if necessary. Our sdk installer should always just show the readme file dialog box when invoked in SILENTMODE. It should also write to a temp file whether it needs a reboot, so products like the forte_cobundle can detect whether it needs a reboot
###@###.### 2001-11-05