REINSTALLMODE

[Kim]

Why is the property REINSTALLMODE also used during uninstall? And is
it a problem if you give it different values for uninstall or
reinstall?

thanks

[Phil Wilson]

It isn't used during an uninstall, which is pretty much just the same as
msiexec /x {productcode} . It might have a default value in your setup, but
that doesn't mean it's used.
--
Phil Wilson
[MVP Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

"Kim" <kv...@hotmail.com> wrote in message
news:8b26f5d3.04081...@posting.google.com...

[Kim]

Thanks for your answer, but it does not match with the things I
noticed. May be you can help me out?
My default is "vamus" for the REINSTALLMODE and because the v is there
it is recaching the msi file. That is exact what I want for the repair
or modify (there I use a reinstall) options, but not for my uninstall.
But somehow it is using it, because if I uninstall and the install
source is not available it is giving error 1612 saying it needs the
install source. If I remove the "v" from the REINSTALLMODE so making
it "amus" before calling the operation to deinstall it works I do not
get the error. So I made the conclusion that it uses the REINSTALLMODE
also during uninstall? Do you may be know how this can happen that it
is used?

thanks,
Kim

All other options that can give this error I already tried/checked,
like ResolveSOurce corrupt msi file, components that need the install
source etc.

"Phil Wilson" <pdjw...@nospam.cox.net> wrote in message news:<e5mfljuf...@TK2MSFTNGP09.phx.gbl>...

[Stefan Krueger [MVP]]

How/where do you set this REINSTALLMODE? On the command line when you launch
the uninstall, or in the property table, or...?
--
Stefan Krueger
Microsoft Windows Installer MVP

Windows Installer FAQ
www.msifaq.com - www.msifaq.de

InstallSite - Resources for Setup Developers
www.installsite.org
www.installsite.de

[Phil Wilson]

I'm a bit confused, maybe Stefan too. An uninstall is an msiexec /x
command line. A minor update by reinstalling the product is typically
msiexec /i new msi file REINSTALL=ALL REINSTALLMODE=vomus . A repair is
msiexec /f with some options that are the same as the REINSTALLMODE values,
but you don't use the REINSTALLMODE property. So which of these are you
trying to achive?

--
Phil Wilson [MVP Windows Installer]

----

"Kim" <kv...@hotmail.com> wrote in message

news:8b26f5d3.0408...@posting.google.com...

[Kim]

The default I set in the property table. Afterthat I set it in the
script of the install project just before the call to the uninstall
operation (using installshield 8.0 FeatureRemoveAll).

"Stefan Krueger [MVP]" <skru...@newsgroups.nospam> wrote in message news:<54A7370E-924D-4AA7...@microsoft.com>...

[Stefan Krueger [MVP]]

The "v" in REINSTALLMODE must be set "outside" the msi file (otherwise it
would be too late to use the newer .msi file). Therefore I believe it will
have no effect (in no case) setting it in the Property table.
It may have an effect if you set it in your InstallScript if you are using
the InstallScript MSI project type, because the installscript runs in an
external process that hands over control to MSI basically only for file
transfer. Also seting "v" on the command line (could be via setup.exe, maybe
in setup.ini) will have an effect.

I don't think that Windows Installer specifically ignores the REINSTALLMODE
property (or any other property for that matter) on uninstall. Actually, at
the time it has to evaluate the v switch to perform the re-caching of the
.msi file, it doesn't know yet whether you're going to uninstall or perform
some other operation.

In other words: I'm would expect the behaviour you see. The solution would
be to set REINSTALLMODE to v only when you really want this. Changing your
script accordingly would be my suggested solution.

Two final notes:
- the "a" in REINSTALLMODE is a dangerous switch because it can downgrade
shared files. If your setup installs shared files (including for instance VB
or C runtime merge modules that install to the Windows or System folder)
don't use "a".
- InstallScript MSI is known to cause problems, especially in upgrade
installs. In most cases I'd prefer Basic MSI.

[Kim]

Then I will set it in the script, that works. I will have a look the
"a" if it gives a problem and change it.

Thanks,
Kim

"Stefan Krueger [MVP]" <skru...@newsgroups.nospam> wrote in message news:<FE34A855-29E5-4AE2...@microsoft.com>...