Cameyo

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Could not execute C:\Program Files\Mozilla Firefox\firefox.exe (Error=5, MvPID=6256)


Member

Status: Offline
Posts: 7
Date:
Could not execute C:\Program Files\Mozilla Firefox\firefox.exe (Error=5, MvPID=6256)
Permalink   
 


I have Firefox 28 made ​​portable with Cameyo version 2.6.1191.
The
first Call (Deploy) works as expected.

At the 2nd
Calling the program is displayed the above error.

Remark:
I've been working a long time with Cameyo and am generally satisfied.
However, there are, especially for larger programs frequent errors.
Furthermore, the registry entries are often not deleted from the VOS directory.

Dietmar



Attachments
__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Hello Dietmarm,

Did you install anything in addition to Firefox?  I can't reproduce your error with Firefox 28 built by Cameyo-2.6.1191.

Please upload your package to a file-hosting site and provide the url, or you can use WeTransfer, send to yourself, and post a link.



__________________


Member

Status: Offline
Posts: 7
Date:
Permalink   
 

Hello

 

I have Firefox 30 made ​​portable with Cameyo version 2.6.1220 Without Plugins.
The
first Call (Deploy) works as expected.

At the 2nd
Calling the program is displayed the error message:

Could not execute C:\Program Fi|es\Mozi||a Firefox\firefox.exe

 
I've attached a log file that was generated by Cameyo Tracer Utility


__________________


Member

Status: Offline
Posts: 7
Date:
Permalink   
 

Hello,

I downloaded Firefox from http://online.cameyo.com/public

Then I modified the configuration as follows (see 2.jpg)

The first Call (Deploy) works as expected.
At the 2nd
Calling the program is displayed the error message (see 3.jpg)

 



Attachments
__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Thanks for your additional information.  With it, I was able to reproduce your report.  My package before was in RAM mode instead of Disk mode.  In RAM mode, the package launches successfully multiple times.

The Team is looking into it.  Thanks again.



__________________


Newbie

Status: Offline
Posts: 2
Date:
Permalink   
 

Based on settings and outcome, I am experiencing the same issue.
While opting for RAM virtualization prevents the error, it also wipes the app on each exit.

Has any progress been made?



__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Unless you are removing the sandbox, all CHANGES should be retained after exiting the package, whether in RAM or Disk mode.

 

Cameyo_User wrote:

While opting for RAM virtualization prevents the error, it also wipes the app on each exit.


 



__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.



Create your own FREE Forum
Report Abuse
Powered by ActiveBoard