Adding 4 registry to a Windows Messenger 5.0 msi installation...
Hey everyone,
Your site has given me a lot of usefull information - so thank you! :) Anyways, we are looking to deploy Windows Messenger 5.0. It has a very nice feature which enables companies to brand the messenger with their corporte logo, help link, etc. I've been looking into what I would need to do to repackage the Messenger msi file to include the 4 registry entries for the branding. I'm an extreme newbie at this so your help and patience in appreciated. I've been working with both WinInstall LE 2003 and I downloaded an eval copy of Wise Package Studio 5.1 which seems much more robust. Now I just have to learn how to use them hah. At any rate I can't seem to get either of them to work correctly. (I'm sure it's user error though) I've looked for some basic walkthroughs but I can't seem to find anything that really pertains exactly to what I'm doing. Can anyone point me in the right direction? Thanks in advance!
Josh
Your site has given me a lot of usefull information - so thank you! :) Anyways, we are looking to deploy Windows Messenger 5.0. It has a very nice feature which enables companies to brand the messenger with their corporte logo, help link, etc. I've been looking into what I would need to do to repackage the Messenger msi file to include the 4 registry entries for the branding. I'm an extreme newbie at this so your help and patience in appreciated. I've been working with both WinInstall LE 2003 and I downloaded an eval copy of Wise Package Studio 5.1 which seems much more robust. Now I just have to learn how to use them hah. At any rate I can't seem to get either of them to work correctly. (I'm sure it's user error though) I've looked for some basic walkthroughs but I can't seem to find anything that really pertains exactly to what I'm doing. Can anyone point me in the right direction? Thanks in advance!
Josh
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
JGraham9382
19 years ago
Ok I checked that box and tried to save the MSI again and the module errors still came up. I re-ran the MSI but it didn't make my registry changes. :( I'll look into using a transform. If you have any more suggestions please let me know. Thanks for the help.
Josh
Josh
Posted by:
kkaminsk
19 years ago
Well the transform should do the trick.
For some reason I was able to recompile with my merge modules missing having the checkbox set. But then again I am using 4.62 on the site I am at. Maybe there is a behaviour change in 5.0?
For some reason I was able to recompile with my merge modules missing having the checkbox set. But then again I am using 4.62 on the site I am at. Maybe there is a behaviour change in 5.0?
Posted by:
kkaminsk
19 years ago
Well not to be a jerk but this question is so 101 which might explain the lack of response. I do not know WinInstall but in Wise when your in the Installation Expert mode there is a registry page where you can add or import registry entries. If you open the Help -> Help Topics you should be able to easily locate the information in Creating or Editing Registry Settings.
Posted by:
JGraham9382
19 years ago
Ya I guess I could have explained one of the problems that I was having with it. :) Whenever I did that and went to recompile or test the MSI it says that it was missing some of the merge modules. I found one of them (it was from microsoft) but there are two more - watsonintl and watson which it says are missing. I can't find those anywhere. Any suggestions?
Posted by:
kkaminsk
19 years ago
Those look to be propreitary merge modules. To get around that, make your registry edits without recompiling the MSI. In the installation expert page go to the Product Details tab then there should be a "Don't recompress / update files when saving" checkbox. That should get you around the merge module issue. Or you could just make a MST which is the textbook way of customizing a MSI. Unfortunately I kinda ignored that.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.