Software Deployment

Well this does confuse me a bit because you are having a typelib associated with .reg and .bat files. Typically COM components are .dll or .exe. I have had Wise outright get the GUIDs wrong when trying to register TypeLibs. I would take a clean machine with a working install and one without then do a delta on HKEY Classes Root. The delta should give you an idea of what Wise is doing wrong. If you cannot figure it out then try removing the delta entries from your MSI and then add them back in but have Wise not convert them to advertising info.

I am assuming you are getting the 1911 from a bad GUID but it could be because of the file type you are using but I dunno for sure because I have not gone down that road. So there is the path of removing all registry entries associated with those two files and then putting them back without converting to advertising information.

I know this is kinda lame for a response but COM is not fun to debug. If anyone has a good reference for how all the registry entries for a COM registration relate to each other it would be nice to help illustrate how it all works. Let me know if this helps at all and if not I'll try to see what I can suggest.

Believe me, the typelib error regarding a .bat or .reg file has me scratching my head too. The association is certainly not part of my intention or design. The files in questions were manually added by me for utility purposes, and are not tied to the installation in any way. For the moment, I will spare this thread the ugly details of how and why I am using this .reg file.

As far as the machine goes, the one I am using is clean. It is a vmware 4.x workstation running Win2K sp4. It is configured to return to the snapshot state upon shutdown, and has a minimal "clean machine" install of Wise Package Studio.

One thing you bring to mind which I have not tried is to retain the registry entries as they are and not convert to advertising info.

This is all part of the fun of trying to repackage Lotus Approach 97 into a stable .msi. Approach 97 is not supported on Win2K, so the whole thing is dicey to begin with. It is one of those client-driven needs that takes one down a less than desireable path.


Craig --<>.

In answer to my own question, I found two solutions:

1. edit the .msi, moving the .reg / .bat files into their own custom component.

or

2. before "end capture", place the desired .reg / .bat files into a higher level directory that contains no dll's so that they do not become a component of any .dll

I chose the latter, as it seemed to be the cleaner option.


Craig --<>.