Re: [WiX-users] MSComm32.ocx MSM not registering ocx

Dave Williamson Fri, 18 Aug 2006 05:34:48 -0700

Thanks Bob. I did just that.

wix_2.0.3719.0

windows installer 2.00.2600.1106

I looked at the installation log and MSI thinks mscomm32.ocx needs to be installed and it installs it without error. So I did a regedit export of the registry then manually registered the mscomm32.ocx using regsvr32 and did a regedit export again and looked for the diffs. And there were some differences.

(And I did compare the Dark output of the msm to the tallow generated code and they were different)

The Dark output showed some interesting constructs that were not directly in the tallow code but seemed like they were the same thing but represented in a different manner.

But yet curiously enough those entries appear to be the missing entries in the registry (see diffs below).

I don't understand why I see the correlation that I see and thus am unable to determine what I need to do.

Here are the differences (MSI entry followed by after regsvr32 entry):

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{648A5600-2C6E-101B-82B6-000000000014}]

==================
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{648A5600-2C6E-101B-82B6-000000000014}]
@="Microsoft Communications Control, version 6.0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{648A5600-2C6E-101B-82B6-000000000014}\InprocServer32]
"ThreadingModel"="Apartment"

==================
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{648A5600-2C6E-101B-82B6-000000000014}\InprocServer32]
"ThreadingModel"="Apartment"
@="C:\\WINDOWS\\system32\\mscomm32.ocx"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{648A5603-2C6E-101B-82B6-000000000014}\1.1\HELPDIR]
@="C:\\WINDOWS\\\\HELP"
==================
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{648A5603-2C6E-101B-82B6-000000000014}\1.1\HELPDIR]
@=""

The following keys were not created by the MSI at all:

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{648A5600-2C6E-101B-82B6-000000000014}\ProgID]
@="MSCOMMLib.MSComm.1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{648A5600-2C6E-101B-82B6-000000000014}\VersionIndependentProgID]
@="MSCOMMLib.MSComm"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{648A5604-2C6E-101B-82B6-000000000014}]
@="MSComm General Property Page Object"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{648A5604-2C6E-101B-82B6-000000000014}\InprocServer32]
@="C:\\WINDOWS\\system32\\mscomm32.ocx"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{D0FC8A81-2CB2-101B-82B6-000000000014}]
@="MSComm Hardware Property Page Object"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{D0FC8A81-2CB2-101B-82B6-000000000014}\InprocServer32]
@="C:\\WINDOWS\\system32\\mscomm32.ocx"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{E0DC8C80-3486-101B-82B6-000000000014}]
@="MSComm Buffers Property Page Object"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{E0DC8C80-3486-101B-82B6-000000000014}\InprocServer32]
@="C:\\WINDOWS\\system32\\mscomm32.ocx"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MSCOMMLib.MSComm]
@="Microsoft Communications Control, version 6.0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MSCOMMLib.MSComm\CLSID]
@="{648A5600-2C6E-101B-82B6-000000000014}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MSCOMMLib.MSComm\CurVer]
@="MSCOMMLib.MSComm.1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MSCOMMLib.MSComm.1]
@="Microsoft Communications Control, version 6.0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MSCOMMLib.MSComm.1\CLSID]
@="{648A5600-2C6E-101B-82B6-000000000014}"

Dave Williamson
Clear Sky Software
[EMAIL PROTECTED]
www.clearskysoftware.com

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Thursday, August 17, 2006 11:14 AM
To: Dave Williamson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] MSComm32.ocx MSM not registering ocx

Dave Williamson wrote:

Anyone know where I should start to look to find out what is wrong when using the MSM? Or is it bad to use the MSM?

Take a look at a verbose installation log. Compare it with the merge module's contents. Are all the components being installed? Check in the log around the InstallValidate action to see which components MSI thinks need to be installed.

Dark the .msm and compare it to what tallow produced.

Should I pull the component GUID out of the MSM and then use that GUID with the tallow generated code?

Only if they component composition is identical. Otherwise you're breaking component rules.

-- 
sig://boB
http://bobs.org

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MSComm32.ocx MSM not registering ocx

Reply via email to