This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: How do i tell him to overwrite always ?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 10, 2007
09:08 AM
How do i tell him to overwrite always ?
Hi,
i have a Basic MSI Project, and i generate one compressed setup.exe.
The setup.exe should always install everything above the existing version.
I set ReinstallModeText to 'amus'
I tryed using comand line parameters 'REINSTALL=ALL REINSTALLMODE=amus' (also tried with vamus)
I have an ini file wich is modified from one executable program.
After i made a change in the source ini file, i would have expect that the installation recognize this and copy this file, but he doesn't.
For each file in my installation there is also one entry in the logfile, like this:
MSI (s) (74:E8) [15:35:12:659]: The file represented by File table key '_DEACC94DC52D7E92272030A4557D6069' has no eligible binary patches
Why doesn't he copy the files ?
Andreas
i have a Basic MSI Project, and i generate one compressed setup.exe.
The setup.exe should always install everything above the existing version.
I set ReinstallModeText to 'amus'
I tryed using comand line parameters 'REINSTALL=ALL REINSTALLMODE=amus' (also tried with vamus)
I have an ini file wich is modified from one executable program.
After i made a change in the source ini file, i would have expect that the installation recognize this and copy this file, but he doesn't.
For each file in my installation there is also one entry in the logfile, like this:
MSI (s) (74:E8) [15:35:12:659]: The file represented by File table key '_DEACC94DC52D7E92272030A4557D6069' has no eligible binary patches
Why doesn't he copy the files ?
Andreas
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 13, 2007
07:36 AM
Hello,
i still have this problem.
can someone help me please?
Andreas
i still have this problem.
can someone help me please?
Andreas
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 13, 2007
08:18 AM
Could you post up the entirety of the log file and perhaps we can figure it out?
Unfortunately, that line you posted doesn't really mean much.
Unfortunately, that line you posted doesn't really mean much.
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 14, 2007
11:23 AM
Looking at the log file, it appears that a number of your INI files are not being overwritten due to Windows Installer file versioning rules. Specifically, it appears that the Hash of the old file matches the new hash of the new file. Typically, a change in the file would result in a change in the Hash for that file.
Specifically, MSI (s) (40:38) [08:59:16:441]: File: C:\Programme\Company\Product\ini\ps.ini; Won't Overwrite; Won't patch; Existing file is unversioned and unmodified - hash matches source file
It appears you may want to specify "Always Overwrite" for these files or author a custom action to set REINSTALLMODE to vamus instead of vomus.
Setup.exe will always pass REINSTALL=ALL REINSTALLMODE=vomus IS_MINOR_UPGRADE=1, so you'll want to overwrite that.
Specifically, MSI (s) (40:38) [08:59:16:441]: File: C:\Programme\Company\Product\ini\ps.ini; Won't Overwrite; Won't patch; Existing file is unversioned and unmodified - hash matches source file
It appears you may want to specify "Always Overwrite" for these files or author a custom action to set REINSTALLMODE to vamus instead of vomus.
Setup.exe will always pass REINSTALL=ALL REINSTALLMODE=vomus IS_MINOR_UPGRADE=1, so you'll want to overwrite that.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 15, 2007
04:13 AM
Many thx.
Now that i know the installer uses 'vomus' ... it all seems easy ... :rolleyes:
Is it somehow possible to use or set IS_MAJOR_UPGRADE, and force a deinstall before installation ? 😉
(i don't want to change the first number of the version number ...)
Andreas
Now that i know the installer uses 'vomus' ... it all seems easy ... :rolleyes:
Is it somehow possible to use or set IS_MAJOR_UPGRADE, and force a deinstall before installation ? 😉
(i don't want to change the first number of the version number ...)
Andreas
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 15, 2007
01:10 PM
You would have to fully author a major upgrade to utilize that behavior.