some apps i create using cameyo request,for admin privilages,when i use it on p.c's with standard account ----But if i use spoon studio to create that very same application,it runs perfectly without needing admin privilages,most apps fail because of lack of admin privilages, "failed hooking cocreate instance",this problem is solved by giving the app admin privliages ,so how is cameyo team,going to address this problem,i need an answer
1)some apps=if they dont get admin privilages on start,fail to start
2)others that do start-up,throw this error "failed hooking cocreate instance",if admin privilges are not given beforehand
Apps created using spoon studio,run without such problems,even for apps that do need admin privilages.
-- Edited by sanji765 on Wednesday 15th of May 2013 04:16:13 AM
These apps dont even need admin rights,even when you install them locally,this is a bug of cameyo
this is a bug in the way cameyo works
-- Edited by sanji765 on Wednesday 15th of May 2013 11:06:37 AM
thank you so much for paying attention,i taught,you were purposefully ignoring me(i stalked your activity a bit) i have created 33 portable apps so far,and i am an advanced user,i like the portability of softwares,i want the platform(cameyo)to be more stable and bug free,thats should be the no 1 priority over perfomance or more functionality.
Thanks for your detailed package. We are not ignoring, just working per priority and attempt to reproduce, among other things.
Btw, the package you uploaded did not include the admin privilege program that this post is about. Can you upload it?
I looked into the other issues you mentioned in your zip:
- Obviously there seems to be a conflict between Cameyo apps and Comodo's guard32.dll. The dumps don't show much, except that it is guard32.dll crashing. Since it's Comodo's module that crashes it seems more natural for them to start checking the issue on their side. I noticed you signaled this on their forum; please let us know when you hear back from them.
- The "Failed to hook CoCreateInstance" is not something general / that we can reproduce here (including on Win 8), so it may be related to something on your configuration. Is there Comodo / other security tools on the machine you got this error on? If so, have you tried it on a machine without it?
- Your other errors could also be related to some kind of interference with Comodo; we don't normally hear about problems with "file deploy errors". It could be something Comodo is preventing Cameyo's engine from doing.
Please try these a machine without Comodo so as to separate Cameyo issues from Comodo issues.
1)- Obviously there seems to be a conflict between Cameyo apps and Comodo's guard32.dll. The dumps don't show much, except that it is guard32.dll crashing. Since it's Comodo's module that crashes it seems more natural for them to start checking the issue on their side. I noticed you signaled this on their forum; please let us know when you hear back from them.
----the problem of comodo is being addressed,by the comodo team
2)- The "Failed to hook CoCreateInstance" is not something general / that we can reproduce here (including on Win 8), so it may be related to something on your configuration. Is there Comodo / other security tools on the machine you got this error on? If so, have you tried it on a machine without it?
---After so much hardwork,i found the problem maker of "Failed to hook CoCreateInstance"=== nvinit.dll of "NVIDIA CORPORATION" is causing the problem of failed hooking co-create,i renamed nvinit.dll ("C:\Windows\SysWOW64\nvinit.dll") to nvinit.dll.bak,the problem gets solved. nvidia version=7.1.740.0
download it here= http://www.techspot.com/drivers/driver/file/information/17223/
3)have you addressed the other two problems(these two problems are not related to firewall or antivirus)=
For the problem "Apps not closing after exit", I would probably avoid using Cameyo to package that app. It is very annoying when I have to eject the USB. One method is to use the -Stop parameter, but it is still very troublesome. Is there a process, XXX.cameyo.exe existing in the task manager?
Mine is different from you. My issue is another serious one. Take a look a this video. I use my eFlip Standard as an example, which I got from GlarySoft giveaway.
http://www.mediafire.com/?ed302si0rzbv6zu
As you see, the process "eFlip Standard.cameyo.exe" is not going to stop. Normally it will stop automatically after the main process (i.e. "FlipPDF.exe") and appear again after I close the application. However sometimes this will fail. I have also just realize that the Cameyo package is going to have the same issue. In the video there is a process "Cameyo-2.0.890.exe" The issue occurs sometimes, but not all the time. For small application, the package works well normally, but fail for large application, for example, my eFlip Standard, nearly 70MB.
But for some packages, they work very well, for example, KMPlayer (52MB), LEGO Digital Designer (320MB). But for some small packages, they "work" with the issue, for example, Toolsoft Audio Player, QuickMark, Helium Audio Converter
But when I launch the package in Win7, there are no any problems. Still I am working in WinXP SP3.
Sanji765, please run -ProcessList parameter to see if SpotifyWebHelper.exe continues after exiting your package. If there are any other processes listed, please advise.
Also, are you encountering the Fatal error running your package from an external drive or from an internal drive?
The failed hooking error is not being ignored. Even though you provided a connection to nvidia, which is very much appreciated, we have not been able to reproduce your experience. Investigation into it continues.
That SpotifyWebHelper.exe continues running after Spotify is exited is by Spotify's design. If you run an installed version of Spotify, you will notice the same behavior. Fortunately, Spotify allows the option to opt out, so to speak, by going to Edit, Preferences, and removing the default check from Allow Spotify to be started from the Web.
""instability arises from programming problems in the Cameo application. Please contact cameyo about this issue.""
My response=
can you be more specific,so I can contact cameyo with more specific information,Thank you.
Their response=
I'm sorry, but I do not have any additional information. I just passed along what QA told me. I believe cameyo should be able to replicate this, and thus determine if there is anything they can do.
I'm sorry, but I cannot help any more than that.
xxxxxxxxxxxxxxxxx
i am not sure what they are talking about,but cameyo is working with comodo now
