This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- What merge module or object is this?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 16, 2010
11:50 AM
32-bit ocx register issue on 64-bit system
Hi,
I re-engineered one of our old products from IS5.5 to IS2010 (Basic MSI), to comply with new OSs. Everything works perfectly on 32-bit systems. But on 64-bit system (Windows 7), when I tried one application, I got Run-time error '339' with the following message:
I searched the system and found the file (crystl32.ocx) at C:\Windows\SystemWOW64 (googled search indicated that this is called emulation on 64-bit systems for 32-bit apps), even though I made the file's destination as [SystemFolder] in IS2010 IDE and registered the component by setting 'COM Extract at Build' to 'Yes'.
If I simply launch a commandline with 'as administrator' and register the component from C:\Windows\SystemWOW64, the error is gone and my application works fine.
So my question is what should be the solution to my issue? Should I add an 'extra' registration step (CA) during the installation (should be after file copying CA), or I should do it during design time (IS2010 IDE), if so, what's it?
Thanks,
PB
I re-engineered one of our old products from IS5.5 to IS2010 (Basic MSI), to comply with new OSs. Everything works perfectly on 32-bit systems. But on 64-bit system (Windows 7), when I tried one application, I got Run-time error '339' with the following message:
Component 'crystl32.ocx' or one of its dependencies not correctly registered: a file is missing or invalid.
I searched the system and found the file (crystl32.ocx) at C:\Windows\SystemWOW64 (googled search indicated that this is called emulation on 64-bit systems for 32-bit apps), even though I made the file's destination as [SystemFolder] in IS2010 IDE and registered the component by setting 'COM Extract at Build' to 'Yes'.
If I simply launch a commandline with 'as administrator' and register the component from C:\Windows\SystemWOW64, the error is gone and my application works fine.
So my question is what should be the solution to my issue? Should I add an 'extra' registration step (CA) during the installation (should be after file copying CA), or I should do it during design time (IS2010 IDE), if so, what's it?
Thanks,
PB
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 16, 2010
04:07 PM
If I want to use a merge module or IS Object to install 'crystl32.ocx', what MM or Object should I h ave in my ISProject? How do I register it on both 32 or 64 bit systems?
Thanks,
pb
Thanks,
pb
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 16, 2010
06:23 PM
Hi,
I am working with a legacy project on IS2010 (Basic MSI). The old project needs the following three files:
I tried to add one merge module or object that handle the 3 files, but I can't find any.
Can anybody point me what MSM/Object is it? If necessary, where can I download it?
Thanks,
PB
I am working with a legacy project on IS2010 (Basic MSI). The old project needs the following three files:
msjter35.dll(needs registration).
msjint35.dll
msjet35.dll
I tried to add one merge module or object that handle the 3 files, but I can't find any.
Can anybody point me what MSM/Object is it? If necessary, where can I download it?
Thanks,
PB
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 13, 2011
11:12 AM
Did you ever find the solution?
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)