project 2010

2 problems.

First the data that I have

- mak licence
- via /admin hwe have created a msp file.
- We have try to put the activation in the package, so the user does'nt must active it in our deployment. But this is not solved.

We have installed virtualpc with windows xp servicepack 3 without no other updates (windows updates). No connection to the network.
And we have installed Wise Package Studio 7.0 on the virtual pc. Must say, i'm fresh in it, I have only created in the past some small programs.
We have here a big software. If I go to the components (via wise setup editor), I see the following file mscomct2.ocx in red, how must I solve it ?

----> Registry
-----> Software
internet explorer
activex compatibility
{1906.....} --> registry1919
{20DD....} |> registry1918

If I compile it, it say's "Setup requires Internet Explorer version 5.0.2314.0 or above"

0 Comments   [ + ] Show comments

Answers (1)

Posted by: anonymous_9363 12 years ago
Red Belt
Presumably you're describing the use of one of the Wise products? This tends to show componets as red if they have no key path set. If you don't understand what a key path is, I suggest passing the project to someone who does or, if you have time, to read Phil Wilson's ouevre, The Definitive Guide to Windows Installer.

Automation of the activation of Office 2010 products (and 2007, which is similar as far as configuration is concerned) is well covered here on AppDeploy, both in posts and the 'Package KB' plus, of course, our dear friend, MSDN.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ