Hi all

A while ago I've created an MST for a vendor MSI package (Altova XML Spy). The MST actually contains no more than simply a license-file and that way (MSI + MST) the program is licensed at install.

The problem (the shit has hit the fan): that license-file is expired and people of the distribution team prefer I create an MSP patch for the original package. I understand that a patch is created based on 2 different MSI's (the old VS the new) but in this case it's about patching an install made out of an MSI with an MST... so I was thinking: hell.. just patch the MST file... errrrrr

What's the way forward with this...? I'm stuck...
0 Comments   [ + ] Show 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.


Thanks Wildhair !

Since the initial version (1.0) of the package has only been distributed towards a few pilot users (and not the complete enterprise) I think I better make a whole new version of that package (1.1) and tell the distribution team to distribute the newer version (and forget about an MSP).

Funny... Minitab is one of the applications I had to package a week ago :) It's a small world after all [:D]
Answered 05/10/2006 by: renio
Senior Yellow Belt

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