Hi,

I've discovered an issue with creating an MST through WPS InstallTailor where InstallTailor will add/change the minimum Windows Installer version (from what's in the original MSI) to the Windows Installer version that's installed on the packaging machine (which was Windows 7 with Windows Installer 5.00 or in MSI language; VersionDatabase = 500).

This means that anyone creating an MST in this manner, wouldn't be able to run the same MST under Windows XP for the reason that Windows Installer 4.5 is the latest (last?) version to be offered for Windows XP (which is VersionDatabase = 450).

Please perform the following steps to resolve the issue:-
  1. Open the .MSI in Windows Installer Editor.
  2. Go to Setup Editor > Tables tab > Summary table.
  3. Take note of the Minimum Installer Version field (such as 1.10 which is the correct minimum version for this MSI)
  4. Open the .MST in Windows Installer Editor.
  5. Go to Setup Editor > Tables tab > Summary table.
  6. Change the value of the Minimum Installer Version field to the correct version as indicated in step 3.
  7. Compile the .MST.

Please note, to also confirm that the 'Minimum Installer Version' required by the MSI/MST is also the one that's been installed on your client workstations (msiexec /? will give you the version details).

Kind Regards,

spirosl
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
It's not really an issue, is it?

For more years than I care to remember, most development has always targetted the lowest common denominator. For corporate packaging, that's Windows XP. You package on XP, then target your higher version OSs from that base,incorporating appropriate changes.
Answered 01/13/2011 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity