How I Repackage the vendor msi (Microsoft Access 2000) that going to work on NT 4.0 and XP both. I create one package for each that works but I need help to create one package for both OS.

Million thanks in advance.

0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


To what end are you attempting to repackage this MSI? The Custom Installation Wizard (CIW) provided by Microsoft will walk you through creating an MST (Transform) which should provide any customization of the installation you require (it even provides the command line required to silently install the whole thing).

As a general rule it is not a good thing to repackage MSI files. Aside from the inherent complexities of Office products and their interaction with other products at the feature level, you would have problems/failures in attempting to apply patches or upgrade to a later version.

Even if your repackaged MSI appears to work in testing, I would be willing to bet you would experience problems in the near future. If I have misunderstood your problem, please elaborate- but if you are asking for tips on repackaging a Microsoft Office MSI file I don't think there is anyone that would disagree that you simply should not do it.

Hope this helps,
Answered 03/11/2004 by: bkelly
Red Belt

Please log in to comment
If you managed to capture and repackage the MS Access msi and make it work....then I'm really impressed.
Answered 03/11/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment