Cameyo

chris-prima · Newbie

ActiveX Issues

betaleaf · Senior Member

Try using custom events to register and unregister the ActiveX during runtime OR try setting the file system to Strictly Isolated.

chris-prima · Newbie

Thanks for the reply. We could manually register the ActiveX controls but that defeats the point of using Cameyo. i.e. We are using Cameyo in order to solve registration issues, mostly permission issues. Strictly isolated does not work as the application writes temporary files, the user needs access to other directories and we save things to the registry such as screen positions.

mule · Guru

Please advise url to download your logs and package. You can send by PM if there is something you prefer not available to the public.

chris-prima · Newbie

hi,

I have a little more information about my problem that you may find useful. It appears (although I am not certain) that the machines where my issue occurs have recently had a windows update installed. I know that there is a forum message about this and I am using Cameyo-3.1.1424.exe which is the advice in the forum but this has not solved the problem with my active-x's.

MarkusM · Member

I have exact the same issue:

I have an old VB6 application where I have to register the OCX files manually.

With the old Cameyo Version (before the problem with the known windows update occured) everything worked fine.

Now, to fix the windows update problem, I rebuild the VB6 application with the current Cameyo Version (311427)

The result:

The new build VB6 app wont start anymore, because the OCX's are not registered.

Ok, than i took my old virtualized VB6 app, which worked fine in the past and just updated the Cameyo Engine.

Same result. The OCX dont seem to be registered.

Is there a solution right now? It's really urgent because we need the application all the time.

Thanks in advance

Markus

chris-prima · Newbie

We are still testing but at the moment I think that we have a solution. The problems for us seem to be around the SysWOW64 directory. Our capture machine was 32bit so activex controls were registered in the c:\windows\system32 - %System%. I assumed (incorrectly I think) that Cameyo would virtualize these in the c:\windows\SysWOW64 if the deployment machine was 64 bit. In the latest version of Cameyo there is a %SysWOW64% virtual directory - This does not seem to be documented. So I tried copying my activex controls into there but that did not work. Cameyo also advised me to do a new capture using the latest version. I think that the Windows update has affected this somehow. To get it to work I placed and registered the activex controls in the same virtual directory as the executable thus bypassing any issues with System32/SysWOW64.

betaleaf · Senior Member

You might find this useful

https://msdn.microsoft.com/en-us/library/aa384187(v=vs.85).aspx