Hi Jeff,

> I am using SB 7 to update a program that is usually going to be
> already running at the time that the setup is started.
>
> Since this particular program may or may not be running as a service,
> I call Clarion code in a support dll to shut my application down
> before the installation continues.
>
> Despite the fact that my program is already terminated by the time the
> files get installed, I still get a prompt that a re-boot is needed.
>
> What can I do so that this isn't necessary?
>
> If the service is not running when the setup is run, then I do not get
> a reboot message.

You can use the "Check In-use File..." and "Check In-use Folder Tree..."
functions to check if files are in-use (active or locked).

If a file cannot be replaced during the file installation process (access
denied), it is logged and Windows has to replace it after a restart.

If the reboot message is displayed (and you do not force a reboot
programmatically from your script) then at least one existing file was
locked. In your case, I assume your service is still running (doing some
shut-down activities). Can't you use the Service functions in SetupBuilder
to stop the service? Then give a few seconds for shutdown, check again
(from SetupBuilder using "Check Service...") whether the service is still
active, then (to be on the safe side), use "Check In-use File..." on the
service file. Do this in a Loop and you should be done. If, say, after 4
or 5 "retries" the service is still active or the file is still locked,
display a message stating that the service can't be shut-down yada yada and
a reboot might be required at the end of the installation process. Or even
terminate the install to avoid a required reboot.

Does this help?

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is Windows 7 installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner