Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

ComCapture on x64

Updated: 16 Nov 2011 | 9 comments
piyushnasa's picture
+1 1 Vote
Login to vote
This issue has been solved. See solution.

Does anyone here has and idea on what is the difference between running a regsvr32 from C:\Windows\System32\ and C:\Windows\syswow64 folder.

As in I know that they are used for 64 bit registering and 32 bit registering, but where actually it makes a difference?

Also when we run comcapture in WISE package studio, does it do a 64 bit register or 32 bit?

Awaiting your thoughts.. kind of urgent.

 

-Piyush

Comments

Mistral's picture
15
Nov
2011
2 Votes +2
Login to vote

Wisecomcapture is a 32bit

Wisecomcapture is a 32bit executable (only).

 

regsrv32 in System32 is the 64bit executable to register 64bit (native).

regsrv32 in Syswow64 is the 32bit executable to register 32bit (goes to Wow6432Node).

 

WPS is announced to be capable of 64bit capture with a SP in Q1-2/2012.

A Wise Package Studio 8.0 maintenance release is planned for the first half of next year. The release is expected to include critical bug fixes, and 64-bit support for the WiseScript Editor and SetupCapture tools.

VBScab's picture
15
Nov
2011
0 Votes 0
Login to vote

Why use RegSvr32 anyway?

You should be using the advertising tables.

Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.

EdT's picture
15
Nov
2011
1 Vote +1
Login to vote

I think the problem is that

I think the problem is that WiseComCapture cannot extract 64 bit registration information from a 64 bit DLL, and the capture engine cannot capture registration data, so it's a bit tricky to find the information needed to populate the advertising tables.  If you know of any tools to extract 64 bit registration information then please share with us.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Evan.Border@FlexeraSoftwaredotcom's picture
15
Nov
2011
1 Vote +1
Login to vote

Use Regshot

Use the free RegShot x64 utility to capture the registry (perform the %SystemRoot%\System32\regsvr32.exe between the snapshots).  Once you have the text "compare" report, you can do a few search-and-replaces to create a .reg file that you can then import into the Windows Installer Editor's Components tab (importing it into the same component that contains the file, of course).

Regshot can be found at: http://code.google.com/p/regshot/

 

-Evan

-Evan  (to e-mail me, replace the "dotcom" at the end of my screen name with .com)

piyushnasa's picture
16
Nov
2011
1 Vote +1
Login to vote

Thanks Evan, I have used

Thanks Evan,

I have used Regshot for 32 bit to get this working..

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

piyushnasa's picture
15
Nov
2011
1 Vote +1
Login to vote

Thanks all for posting your

Thanks all for posting your thoughts. I will try to use RegShot and suggested by you Evan. Hopefully it will help.

The issue which I am facing is that the dll/ocx which I register on 32 bit somehow do not work on 64 bit when I replicate them through MSI.

but when I unregister them and register them through Windows\Syswow64\regsvr32, then it seems to work fine.

Weird but that is how it is.. Lets see what Regshot can check in this.

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

EdT's picture
16
Nov
2011
0 Votes 0
Login to vote

Have you tried detecting the

Have you tried detecting the operating system you are running on, and if 64 bit, then ensure you run the correct version of REGSVR32.exe by always specifying the full and appropriate path?

I suspect that the use of the 64 bit version of regsvr32.exe on a 32 bit DLL is failing. If you try the same operation from a command prompt, do you get any error messages?

Of course, the technically correct solution is as described in other postings in this thread, but where this proves impossible (for whatever reason) then compromises have to be made.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

piyushnasa's picture
16
Nov
2011
0 Votes 0
Login to vote

Thanks EdT for your help.

Thanks EdT for your help. Even I think that 64 bit Regsvr32 is failing to register 32 bit dll.

I have used Regshot to capture the registries by registering the dll through regsvr32 of Syswow64 folder. It seems to work fine now.

Thanks a lot for your help.

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

Evan.Border@FlexeraSoftwaredotcom's picture
15
Nov
2011
0 Votes 0
Login to vote

Use advertising info

As VBScab stated, you should be using the advertising tables. So mark the checkbox that says "Extract advertising information from registry file" when importing the reg file (from the Setup Editor's Components tab).

-Evan  (to e-mail me, replace the "dotcom" at the end of my screen name with .com)