I "2nd" what madongolf says.
All Microsoft .msi based applications - right out of the box - run correctly for a standard user. There should be no need to customize rights on any directory or registry key, unless: 1. the original .msi has been altered 2. the installation has been...
I am using Wise Package Studio 3.2 When I manually add a merge module to a feature, they will not "stick". In other words, after I compile / save my .msi the modules are not present; I reopen the .msi for editing, and the modules are gone.
This is happening regardless of what...
Mark,
I had the same problem when repackaging Dreamweaver MX 2004. The problem does indeed reside in the sqlbase.msm There is some problem where the searches for the IE version fail, even though the target machine meets the minimum IE requirement. You can find these lines in the CustomAction...
Are you literally capturing the installation of Office 2000? If so, this is un-necessary, and will result in an unstable package. Office 2000 is already in .msi format. An adminstrative installation point should be created, and then the resulting .msi should be customized using the Office...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.