/build/static/layout/Breadcrumb_cap_w.png

HKLM\Software\Microsoft\COM3

Hi All,

Will any one please help me here?

In my capture of an application i have got some registry entries in HKLM\Software\Microsoft\COM3 and some .clb files in C:\Windows\Registration.

I have one file InaCalcPro.dll in my application and the registry entries are of this file.

When i register this file using wisecomcapture the i dont get any registries in above said key(I got registration entries under HKCR).
But when i register it using regsvr32 then i get the entries under that key(duplicates fo registry entries which i got under HKCR).C:\Windows\Registration are also a part of this registration.

Why iam getting difference in these registrations?What exactly is HKLM\Software\Microsoft\COM3? I know this is for COM+ applications but no more idea on this. Can i safely exclude these registries and files?

I have googled a lot on this with no success.

Thanks for your help.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: naveen.packager 13 years ago
Green Belt
0
Is this such a basic question that should not be asked??[:(]

I don't know, I apologize if it is.But waiting for any kind of little help on this.
Posted by: anonymous_9363 13 years ago
Red Belt
0
I have always removed any captured entries in the COM3 branch and not experienced any adverse effects.
Posted by: naveen.packager 13 years ago
Green Belt
0
Thank you very much VBScab.
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

Share

 
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