Reboot Question at end of install

[NewsArchive]

At the end of install, the Reboot Yes or no question pops up.
I don't remember asking for this anywhere..
How do I get rid of it?

--
Dan Scott
C55 - C6.3 Legacy
Garage Partner Pro / Invoice Partner
www.garagepartner.com
Plan A is always more effective when the device you are working on
understands that Plan B involves a larger hammer

[NewsArchive]

> At the end of install, the Reboot Yes or no question pops up.
> I don't remember asking for this anywhere..
> How do I get rid of it?

Dan,
Most likely you replaced a file that was in use. The system needs to reboot
to copy your new file into place.
Other things like that can cause the installer to figure out that it needs
to reboot.

HTH,
Rick

[NewsArchive]

What Rick said. I do a check to see if the program is still running and won't
proceed with the install while it is. No client of mine has ever been forced to
reboot because of my updates.

Russell B. Eggen
www.radfusion.com

[NewsArchive]

Rick and Russ

I have check for in-use files checked.

--
Dan Scott
C55 - C6.3 Legacy
Garage Partner Pro / Invoice Partner
www.garagepartner.com
Plan A is always more effective when the device you are working on
understands that Plan B involves a larger hammer

[NewsArchive]

Dan

You need to do more than that I think. (And I do not know where you see such a
checkbox if that is what you are referring to..)

In-use and Running are separate beasts I think. I would use In-Use for things like
data files.

Here is what I have in my scripts.

Set Variable %PROGISRUNNING% to FUNCTION:Detect Active Application("MyEXE.EXE") [File
Name]
If %PROGISRUNNING% Equals "1" Then
Display Message Box "My Manager System cannot be updated while someon..." --
"Update Not Allowed"
Exit Installation()
End

HTH

JohnG

[NewsArchive]

Hi John

The thing is, it was a new install, none of the files were there before.

--
Dan Scott
C55 - C6.3 Legacy
Garage Partner Pro / Invoice Partner
www.garagepartner.com
Plan A is always more effective when the device you are working on
understands that Plan B involves a larger hammer

[NewsArchive]

Hi Dan

Then perhaps your install is trying to update one of the system files (Probably a
no-no) or another DLL in a common location.

Or perhaps you have added a service that should be started at boot time? Or one of the
other powerful functions built into SB..

Something is causing it based on a dependancy if you did not explicitly ask it to
reboot somewhere.

JohnG

[NewsArchive]

Here is the reboot ?

--
Dan Scott
C55 - C6.3 Legacy
Garage Partner Pro / Invoice Partner
www.garagepartner.com
Plan A is always more effective when the device you are working on
understands that Plan B involves a larger hammer

[NewsArchive]

Dan,

>
> Here is the reboot ?
>

If you do not have a "Reboot/Resume..." script function in your script then
you replaced a "locked" (in-use) file. Windows needs a reboot to complete
the installation process.

If you don't know which file causes it then you can find the name of the
file in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session
Manager\PendingFileRenameOperations

Friedrich