3 replies to this topic

[Stefan Secker]

Hi there,

my IS Dev 7.04 setup contains the .NET framework and the installer
version 2.0 on the source media. A setup launcher installs that stuff
if necessary.

On Windows XP the .NET installation doesn't cause a reboot, and in
addition Windows XP contains the version 2.0 installer
(msi.dll 2.0.2600).

My setup always asks for a reboot there, because it tries to update
the Windows Installer if executed by the setup.exe. Why is that?
Can this behaviour be changed ?

I already tried to change my setup back to 1.2 schema, but that didn't
help either ????

Thanx for any help

Stefan

[hteichert]

If you are running your setup by starting "setup.exe", this wrapper first checks if the installed version of the windows installer service (msi.dll, msiexec.exe, ...) fulfills the requirements. The required version is noted in the file "setup.ini". I can't tell you which version is used by IS Dev 7.04 by default, cause i'm still using 1.52, but almost all wrappers use this kind of check.
The older versions of IS Dev used a section named "[Startup]" with an entry "MsiVersion=a.b.c.d" to define the required MSI version.
You could change the value for "a.b.c.d" in the "setup.ini" to be less or equal than the standard version on Win XP, but be aware of eventually arising problems on other Microsoft operating systems and that there are some faulty MSI 2.0.2600.d versions around (the "d" is the problem!)

[Stefan Secker]

Hi,

thanx for your help so far,
I solved the problem with the (for a while vanished) setup.ini. In my case it looked for 2.0.2600.2
So the Installer reboot issue is gone now!

Unfortunately the setup launcher does still causes a reboot when installing the .NET framework, although installing it manually doesn't cause it?
Any help for that problem available ???

Stefan

Edited by Stefan Secker, 24 September 2003 - 17:13.

[ijahman]

installing the .NET framework ... isn't this an MSI, too?
In this case:
do a verbose log, then you might find the cause.

use msiexec /i "<msifile>" /L*v "<logfile>"
or set the logging policy using
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
Logging=vicewarmupo

regards, Fritz

Edited by ijahman, 26 September 2003 - 17:37.