Final Solution to overwrite all files of old version

We need to set REINSTALLMODE property of our msi file to amus.

Following is the link to know more about the meaning of 'amus'
http://msdn.microsoft.com/en-us/libr...8VS.85%29.aspx

There are two ways to do that.

1. By using msiexec.exe which comes with .NET SDK (if you have VS 2005 or VS 2008 it will come with it, just browse to command prompt of visual studio and you will find it there)

once you find msiexec.exe just type following command to set REINSTALLMODE property to amus for your installer.

msiexec.exe /i foo.msi REINSTALLMODE=amus

2. By using orca

Orca is utility to modify msi files.

You can download 'Orca' from following links.
http://www.technipages.com/wp-conten...07/11/orca.Msi
or
http://www.softpedia.com/get/Authori...ors/Orca.shtml

Steps:
-Install orca into your computer.
-Open orca
-Drag and drop your msi into orca UI
-Into left panel it will list the name of tables
-select property table
-go to right panel and right click
-click on 'Add Row'
-into 'Property' type REINSTALLMODE
-into 'Value' type amus
-save msi file
-and that's it

Now when you install it will overwrite all files.




Yofnik wrote:

RemovePreviousVersion STILL not working
05-Apr-07

Hi All,
I am sorry to beat a dead horse here, but I am still having trouble
getting my upgrade MSI to uninstall a previous version of the
application. Here are the facts:

- MSI built with Visual Studio 2003
- Version, ProductCode, and PackageCode have been updated.
- UpgradeCode has not been changed.
- RemovePreviousVersion set to true.
- Both versions of the application were installed at the System level
(selected Everyone)

This is driving me nuts as I still see multiple entries in the Add/
Remove Programs list. I have searched and searched the user groups and
all responses I found relate to one of the facts I listed above. I am
still having problems though. Is there anything else that could be
causing this? Please help!

Thanks,
Yofnik

Previous Posts In This Thread:

On Thursday, April 05, 2007 1:20 PM
Yofnik wrote:

RemovePreviousVersion STILL not working
Hi All,
I am sorry to beat a dead horse here, but I am still having trouble
getting my upgrade MSI to uninstall a previous version of the
application. Here are the facts:

- MSI built with Visual Studio 2003
- Version, ProductCode, and PackageCode have been updated.
- UpgradeCode has not been changed.
- RemovePreviousVersion set to true.
- Both versions of the application were installed at the System level
(selected Everyone)

This is driving me nuts as I still see multiple entries in the Add/
Remove Programs list. I have searched and searched the user groups and
all responses I found relate to one of the facts I listed above. I am
still having problems though. Is there anything else that could be
causing this? Please help!

Thanks,
Yofnik

On Thursday, April 05, 2007 1:43 PM
Comcast wrote:

Where is the call to RemoveExistingProducts in the execution sequence.
Where is the call to RemoveExistingProducts in the execution sequence. Try
moving it to right after InstallValidate.

Steve

On Thursday, April 05, 2007 1:51 PM
Phil Wilson wrote:

I believe this is a bug in VS 2003.
I believe this is a bug in VS 2003. The search for whether the older product
is installed happens before the per-user/per-machine value for ALLUSERS has
been set, so it is still in per-user mode when it finds the older version
and so won't upgrade it.

It's possible that msiexec /i <your msi> ALLUSERS=1 will work. If so, you
could edit the MSI file with Orca and add ALLUSERS with a value of 1 in the
Property table so you don't need the command line. ALLUSERS is
case-sensitive. This is fixed in VS 2005.
--
Phil Wilson
[Microsoft MVP Windows Installer]

"Yofnik" <yofnik@comcast.net> wrote in message
news:1175793600.332204.108060@q75g2000hsh.googlegr oups.com...

On Thursday, April 05, 2007 2:38 PM
Yofnik wrote:

Re: RemovePreviousVersion STILL not working
I tried both suggestions:

- In the InstallExecuteSequence table, I gave RemoveExistingProducts a
value of 1450, InstallValidate has a value of 1400.

- I added ALLUSERS=1 to to the Property table.

No luck in either case.

On Thursday, April 05, 2007 3:09 PM
Comcast wrote:

Set the ALLUSERS property to 1 at the top of the InstallExecuteSequence table.
Set the ALLUSERS property to 1 at the top of the InstallExecuteSequence
table.

On Friday, April 06, 2007 6:50 PM
Phil Wilson wrote:

Just in case it's not the ALLUSERS issue, the other thing that causes this is
Just in case it is not the ALLUSERS issue, the other thing that causes this
is ProductVersions less than 1.0 in your Visual Studio setup projects.

--
Phil Wilson
[Microsoft MVP Windows Installer]

On Monday, April 09, 2007 2:36 PM
Yofnik wrote:

Setting ALLUSERS to 1 in the InstallExecuteSequence table did thetrick.
Setting ALLUSERS to 1 in the InstallExecuteSequence table did the
trick. Thanks guys.

Jeff

On Monday, April 09, 2007 2:38 PM
Yofnik wrote:

Setting the ALLUSERS property to 1 in the InstallExecuteSequence tabledid the
Setting the ALLUSERS property to 1 in the InstallExecuteSequence table
did the trick. Thanks guys.

On Thursday, April 12, 2007 1:31 PM
wheresjim wrote:

How can you set ALLUSERS=1 in the InstallExecuteSequence table?
How can you set ALLUSERS=1 in the InstallExecuteSequence table? The
schema I see in my MSIs for InstallExecuteSequence is:

("Action", String, 72, PRIMARY KEY)
("Condition", String, 255)
("Sequence", ShortInteger)

Is the schema different for VS .NET 2003?


On Apr 5, 12:09 pm, "Comcast" <nos...@comcast.net> wrote:

On Thursday, April 12, 2007 5:01 PM
Yofnik wrote:

I entered "ALLUSERS" for the Action and 1 for the Sequence. That didthe trick.
I entered "ALLUSERS" for the Action and 1 for the Sequence. That did
the trick.

On Friday, November 07, 2008 2:37 PM
snappy jo wrote:

Version installation exception: "Another version of the product is already installed"
To whom it may concern,
Take the following setup actions when trying to install new version:

1. On Install project, config the following:
DetectNewerInstalledVersion = true
Install AllUsers = true
RemovePrevousVersions = true

2. Before each build, change the Install package version (1.0.0 to 1.0.1), which will require a new product code, click ok for a new code.

3.Navigate to your main project properties->application->assembly information and change the assembly version (1.0.0.0 to 1.0.0.1), click ok, Save and build both you main and install projects.

The reason for the "Another version of the product is already installed" prompt is because your trying to install a version with the same product code. Execute due deligence when doin a new build so it will be defined as it's own new version. Hope this helps..
Thanks,
Snappy


Submitted via EggHeadCafe - Software Developer Portal of Choice
Adding WCF Service References
http://www.eggheadcafe.com/tutorials...ce-refere.aspx

Hi there


Im having alot of trouble with this im getting the canot install error and found this post

Having loked at the 2 methods here one of them I either dont understand or just cant get it to function

Your second method for forcing an install "orca" will not work the "orca" program gives me this error when I try to add a value


failed to add row to property value (in upper case)

in lower case it allows me to enter these properties but im still getting the same error when i try to run the installer

SteamInstall_English.msi


What can I do help?

I really dont want to have to re-install windows


thx




> On Thursday, April 05, 2007 1:20 PM Yofnik wrote:

> Hi All,
> I am sorry to beat a dead horse here, but I am still having trouble
> getting my upgrade MSI to uninstall a previous version of the
> application. Here are the facts:
>
> - MSI built with Visual Studio 2003
> - Version, ProductCode, and PackageCode have been updated.
> - UpgradeCode has not been changed.
> - RemovePreviousVersion set to true.
> - Both versions of the application were installed at the System level
> (selected Everyone)
>
> This is driving me nuts as I still see multiple entries in the Add/
> Remove Programs list. I have searched and searched the user groups and
> all responses I found relate to one of the facts I listed above. I am
> still having problems though. Is there anything else that could be
> causing this? Please help!
>
> Thanks,
> Yofnik


>> On Thursday, April 05, 2007 1:43 PM Comcast wrote:

>> Where is the call to RemoveExistingProducts in the execution sequence. Try
>> moving it to right after InstallValidate.
>>
>> Steve


>>> On Thursday, April 05, 2007 1:51 PM Phil Wilson wrote:

>>> I believe this is a bug in VS 2003. The search for whether the older product
>>> is installed happens before the per-user/per-machine value for ALLUSERS has
>>> been set, so it is still in per-user mode when it finds the older version
>>> and so won't upgrade it.
>>>
>>> It's possible that msiexec /i <your msi> ALLUSERS=1 will work. If so, you
>>> could edit the MSI file with Orca and add ALLUSERS with a value of 1 in the
>>> Property table so you don't need the command line. ALLUSERS is
>>> case-sensitive. This is fixed in VS 2005.
>>> --
>>> Phil Wilson
>>> [Microsoft MVP Windows Installer]
>>>
>>> "Yofnik" <yofnik@comcast.net> wrote in message
>>> news:1175793600.332204.108060@q75g2000hsh.googlegr oups.com...


>>>> On Thursday, April 05, 2007 2:38 PM Yofnik wrote:

>>>> I tried both suggestions:
>>>>
>>>> - In the InstallExecuteSequence table, I gave RemoveExistingProducts a
>>>> value of 1450, InstallValidate has a value of 1400.
>>>>
>>>> - I added ALLUSERS=1 to to the Property table.
>>>>
>>>> No luck in either case.


>>>>> On Thursday, April 05, 2007 3:09 PM Comcast wrote:

>>>>> Set the ALLUSERS property to 1 at the top of the InstallExecuteSequence
>>>>> table.


>>>>>> On Friday, April 06, 2007 6:50 PM Phil Wilson wrote:

>>>>>> Just in case it is not the ALLUSERS issue, the other thing that causes this
>>>>>> is ProductVersions less than 1.0 in your Visual Studio setup projects.
>>>>>>
>>>>>> --
>>>>>> Phil Wilson
>>>>>> [Microsoft MVP Windows Installer]


>>>>>>> On Monday, April 09, 2007 2:36 PM Yofnik wrote:

>>>>>>> Setting ALLUSERS to 1 in the InstallExecuteSequence table did the
>>>>>>> trick. Thanks guys.
>>>>>>>
>>>>>>> Jeff


>>>>>>>> On Monday, April 09, 2007 2:38 PM Yofnik wrote:

>>>>>>>> Setting the ALLUSERS property to 1 in the InstallExecuteSequence table
>>>>>>>> did the trick. Thanks guys.


>>>>>>>>> On Thursday, April 12, 2007 1:31 PM wheresjim wrote:

>>>>>>>>> How can you set ALLUSERS=1 in the InstallExecuteSequence table? The
>>>>>>>>> schema I see in my MSIs for InstallExecuteSequence is:
>>>>>>>>>
>>>>>>>>> ("Action", String, 72, PRIMARY KEY)
>>>>>>>>> ("Condition", String, 255)
>>>>>>>>> ("Sequence", ShortInteger)
>>>>>>>>>
>>>>>>>>> Is the schema different for VS .NET 2003?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Apr 5, 12:09 pm, "Comcast" <nos...@comcast.net> wrote:


>>>>>>>>>> On Thursday, April 12, 2007 5:01 PM Yofnik wrote:

>>>>>>>>>> I entered "ALLUSERS" for the Action and 1 for the Sequence. That did
>>>>>>>>>> the trick.


>>>>>>>>>>> On Friday, November 07, 2008 2:37 PM snappy jo wrote:

>>>>>>>>>>> To whom it may concern,
>>>>>>>>>>>
>>>>>>>>>>> Take the following setup actions when trying to install new version:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 1. On Install project, config the following:
>>>>>>>>>>>
>>>>>>>>>>> DetectNewerInstalledVersion = true
>>>>>>>>>>>
>>>>>>>>>>> Install AllUsers = true
>>>>>>>>>>>
>>>>>>>>>>> RemovePrevousVersions = true
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2. Before each build, change the Install package version (1.0.0 to 1.0.1), which will require a new product code, click ok for a new code.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 3.Navigate to your main project properties->application->assembly information and change the assembly version (1.0.0.0 to 1.0.0.1), click ok, Save and build both you main and install projects.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The reason for the "Another version of the product is already installed" prompt is because your trying to install a version with the same product code. Execute due deligence when doin a new build so it will be defined as it's own new version. Hope this helps..
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Snappy


>>>>>>>>>>>> On Friday, February 19, 2010 1:51 AM Jinal Desai wrote:

>>>>>>>>>>>> We need to set REINSTALLMODE property of our msi file to amus.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Following is the link to know more about the meaning of 'amus'
>>>>>>>>>>>>
>>>>>>>>>>>> http://msdn.microsoft.com/en-us/libr...8VS.85%29.aspx
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> There are two ways to do that.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 1. By using msiexec.exe which comes with .NET SDK (if you have VS 2005 or VS 2008 it will come with it, just browse to command prompt of visual studio and you will find it there)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> once you find msiexec.exe just type following command to set REINSTALLMODE property to amus for your installer.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> msiexec.exe /i foo.msi REINSTALLMODE=amus
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2. By using orca
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Orca is utility to modify msi files.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> You can download 'Orca' from following links.
>>>>>>>>>>>>
>>>>>>>>>>>> http://www.technipages.com/wp-conten...07/11/orca.Msi
>>>>>>>>>>>>
>>>>>>>>>>>> or
>>>>>>>>>>>>
>>>>>>>>>>>> http://www.softpedia.com/get/Authori...ors/Orca.shtml
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Steps:
>>>>>>>>>>>>
>>>>>>>>>>>> -Install orca into your computer.
>>>>>>>>>>>>
>>>>>>>>>>>> -Open orca
>>>>>>>>>>>>
>>>>>>>>>>>> -Drag and drop your msi into orca UI
>>>>>>>>>>>>
>>>>>>>>>>>> -Into left panel it will list the name of tables
>>>>>>>>>>>>
>>>>>>>>>>>> -select property table
>>>>>>>>>>>>
>>>>>>>>>>>> -go to right panel and right click
>>>>>>>>>>>>
>>>>>>>>>>>> -click on 'Add Row'
>>>>>>>>>>>>
>>>>>>>>>>>> -into 'Property' type REINSTALLMODE
>>>>>>>>>>>>
>>>>>>>>>>>> -into 'Value' type amus
>>>>>>>>>>>>
>>>>>>>>>>>> -save msi file
>>>>>>>>>>>>
>>>>>>>>>>>> -and that's it
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Now when you install it will overwrite all files.

It would help if you'd get a real newsreader and not post
to online websites. The online sites just copy usenet posts
to serve as their own "content". If you don't know what
usenet is then look it up. You're posting to a long, meandering
discussion from 4 years ago! How about just trying to explain
more about the problem that you're having, and the actual
errors. The installer is not removing old an version? Then why
not just remove that first.

I downloaded the installer. (I got "SteamInstall.msi", not
"SteamInstall_English.msi") The actual installation is fairly
simple. Just a few files and a handful of basic Registry entries.
You could do that by hand if necessary.

| Hi there
|
|
| Im having alot of trouble with this im getting the canot install error and
found this post
|
| Having loked at the 2 methods here one of them I either dont understand or
just cant get it to function
|
| Your second method for forcing an install "orca" will not work the "orca"
program gives me this error when I try to add a value
|
|
| failed to add row to property value (in upper case)
|
| in lower case it allows me to enter these properties but im still getting
the same error when i try to run the installer
|
| SteamInstall_English.msi
|
|
| What can I do help?
|
| I really dont want to have to re-install windows
|
|
| thx
|
|
|
|
| > On Thursday, April 05, 2007 1:20 PM Yofnik wrote:
|
| > Hi All,
| > I am sorry to beat a dead horse here, but I am still having trouble
| > getting my upgrade MSI to uninstall a previous version of the
| > application. Here are the facts:
| >
| > - MSI built with Visual Studio 2003
| > - Version, ProductCode, and PackageCode have been updated.
| > - UpgradeCode has not been changed.
| > - RemovePreviousVersion set to true.
| > - Both versions of the application were installed at the System level
| > (selected Everyone)
| >
| > This is driving me nuts as I still see multiple entries in the Add/
| > Remove Programs list. I have searched and searched the user groups and
| > all responses I found relate to one of the facts I listed above. I am
| > still having problems though. Is there anything else that could be
| > causing this? Please help!
| >
| > Thanks,
| > Yofnik
|
|
| >> On Thursday, April 05, 2007 1:43 PM Comcast wrote:
|
| >> Where is the call to RemoveExistingProducts in the execution sequence.
Try
| >> moving it to right after InstallValidate.
| >>
| >> Steve
|
|
| >>> On Thursday, April 05, 2007 1:51 PM Phil Wilson wrote:
|
| >>> I believe this is a bug in VS 2003. The search for whether the older
product
| >>> is installed happens before the per-user/per-machine value for
ALLUSERS has
| >>> been set, so it is still in per-user mode when it finds the older
version
| >>> and so won't upgrade it.
| >>>
| >>> It's possible that msiexec /i <your msi> ALLUSERS=1 will work. If so,
you
| >>> could edit the MSI file with Orca and add ALLUSERS with a value of 1
in the
| >>> Property table so you don't need the command line. ALLUSERS is
| >>> case-sensitive. This is fixed in VS 2005.
| >>> --
| >>> Phil Wilson
| >>> [Microsoft MVP Windows Installer]
| >>>
| >>> "Yofnik" <yofnik@comcast.net> wrote in message
| >>> news:1175793600.332204.108060@q75g2000hsh.googlegr oups.com...
|
|
| >>>> On Thursday, April 05, 2007 2:38 PM Yofnik wrote:
|
| >>>> I tried both suggestions:
| >>>>
| >>>> - In the InstallExecuteSequence table, I gave RemoveExistingProducts
a
| >>>> value of 1450, InstallValidate has a value of 1400.
| >>>>
| >>>> - I added ALLUSERS=1 to to the Property table.
| >>>>
| >>>> No luck in either case.
|
|
| >>>>> On Thursday, April 05, 2007 3:09 PM Comcast wrote:
|
| >>>>> Set the ALLUSERS property to 1 at the top of the
InstallExecuteSequence
| >>>>> table.
|
|
| >>>>>> On Friday, April 06, 2007 6:50 PM Phil Wilson wrote:
|
| >>>>>> Just in case it is not the ALLUSERS issue, the other thing that
causes this
| >>>>>> is ProductVersions less than 1.0 in your Visual Studio setup
projects.
| >>>>>>
| >>>>>> --
| >>>>>> Phil Wilson
| >>>>>> [Microsoft MVP Windows Installer]
|
|
| >>>>>>> On Monday, April 09, 2007 2:36 PM Yofnik wrote:
|
| >>>>>>> Setting ALLUSERS to 1 in the InstallExecuteSequence table did the
| >>>>>>> trick. Thanks guys.
| >>>>>>>
| >>>>>>> Jeff
|
|
| >>>>>>>> On Monday, April 09, 2007 2:38 PM Yofnik wrote:
|
| >>>>>>>> Setting the ALLUSERS property to 1 in the InstallExecuteSequence
table
| >>>>>>>> did the trick. Thanks guys.
|
|
| >>>>>>>>> On Thursday, April 12, 2007 1:31 PM wheresjim wrote:
|
| >>>>>>>>> How can you set ALLUSERS=1 in the InstallExecuteSequence table?
The
| >>>>>>>>> schema I see in my MSIs for InstallExecuteSequence is:
| >>>>>>>>>
| >>>>>>>>> ("Action", String, 72, PRIMARY KEY)
| >>>>>>>>> ("Condition", String, 255)
| >>>>>>>>> ("Sequence", ShortInteger)
| >>>>>>>>>
| >>>>>>>>> Is the schema different for VS .NET 2003?
| >>>>>>>>>
| >>>>>>>>>
| >>>>>>>>> On Apr 5, 12:09 pm, "Comcast" <nos...@comcast.net> wrote:
|
|
| >>>>>>>>>> On Thursday, April 12, 2007 5:01 PM Yofnik wrote:
|
| >>>>>>>>>> I entered "ALLUSERS" for the Action and 1 for the Sequence.
That did
| >>>>>>>>>> the trick.
|
|
| >>>>>>>>>>> On Friday, November 07, 2008 2:37 PM snappy jo wrote:
|
| >>>>>>>>>>> To whom it may concern,
| >>>>>>>>>>>
| >>>>>>>>>>> Take the following setup actions when trying to install new
version:
| >>>>>>>>>>>
| >>>>>>>>>>>
| >>>>>>>>>>>
| >>>>>>>>>>> 1. On Install project, config the following:
| >>>>>>>>>>>
| >>>>>>>>>>> DetectNewerInstalledVersion = true
| >>>>>>>>>>>
| >>>>>>>>>>> Install AllUsers = true
| >>>>>>>>>>>
| >>>>>>>>>>> RemovePrevousVersions = true
| >>>>>>>>>>>
| >>>>>>>>>>>
| >>>>>>>>>>>
| >>>>>>>>>>> 2. Before each build, change the Install package version
(1.0.0 to 1.0.1), which will require a new product code, click ok for a new
code.
| >>>>>>>>>>>
| >>>>>>>>>>>
| >>>>>>>>>>>
| >>>>>>>>>>> 3.Navigate to your main project
properties->application->assembly information and change the assembly
version (1.0.0.0 to 1.0.0.1), click ok, Save and build both you main and
install projects.
| >>>>>>>>>>>
| >>>>>>>>>>>
| >>>>>>>>>>>
| >>>>>>>>>>> The reason for the "Another version of the product is already
installed" prompt is because your trying to install a version with the same
product code. Execute due deligence when doin a new build so it will be
defined as it's own new version. Hope this helps..
| >>>>>>>>>>>
| >>>>>>>>>>> Thanks,
| >>>>>>>>>>>
| >>>>>>>>>>> Snappy
|
|
| >>>>>>>>>>>> On Friday, February 19, 2010 1:51 AM Jinal Desai wrote:
|
| >>>>>>>>>>>> We need to set REINSTALLMODE property of our msi file to
amus.
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>> Following is the link to know more about the meaning of
'amus'
| >>>>>>>>>>>>
| >>>>>>>>>>>>
http://msdn.microsoft.com/en-us/libr...8VS.85%29.aspx
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>> There are two ways to do that.
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>> 1. By using msiexec.exe which comes with .NET SDK (if you
have VS 2005 or VS 2008 it will come with it, just browse to command prompt
of visual studio and you will find it there)
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>> once you find msiexec.exe just type following command to set
REINSTALLMODE property to amus for your installer.
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>> msiexec.exe /i foo.msi REINSTALLMODE=amus
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>> 2. By using orca
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>> Orca is utility to modify msi files.
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>> You can download 'Orca' from following links.
| >>>>>>>>>>>>
| >>>>>>>>>>>>
http://www.technipages.com/wp-conten...07/11/orca.Msi
| >>>>>>>>>>>>
| >>>>>>>>>>>> or
| >>>>>>>>>>>>
| >>>>>>>>>>>>
http://www.softpedia.com/get/Authori...ors/Orca.shtml
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>> Steps:
| >>>>>>>>>>>>
| >>>>>>>>>>>> -Install orca into your computer.
| >>>>>>>>>>>>
| >>>>>>>>>>>> -Open orca
| >>>>>>>>>>>>
| >>>>>>>>>>>> -Drag and drop your msi into orca UI
| >>>>>>>>>>>>
| >>>>>>>>>>>> -Into left panel it will list the name of tables
| >>>>>>>>>>>>
| >>>>>>>>>>>> -select property table
| >>>>>>>>>>>>
| >>>>>>>>>>>> -go to right panel and right click
| >>>>>>>>>>>>
| >>>>>>>>>>>> -click on 'Add Row'
| >>>>>>>>>>>>
| >>>>>>>>>>>> -into 'Property' type REINSTALLMODE
| >>>>>>>>>>>>
| >>>>>>>>>>>> -into 'Value' type amus
| >>>>>>>>>>>>
| >>>>>>>>>>>> -save msi file
| >>>>>>>>>>>>
| >>>>>>>>>>>> -and that's it
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>>
| >>>>>>>>>>>> Now when you install it will overwrite all files.
|
|
|

[yaufent]

There's nothing in the context menu of a folder in the Installation Expert's Files page for creating a shortcut. From your instructions, it sounds like you're explaining how to create a folder and a shortcut to it in Windows Explorer.