Cameyo

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Cameyo 2.5.1139 problem with MSVCR90.dll error
Tom

Date:
Cameyo 2.5.1139 problem with MSVCR90.dll error
Permalink   
 


Hello,

I tried to create package of Easeus Data Recovery Wizard 6.1 with Cameyo 2.5.1139.

Package was created without any errors but running it on second system ends with runtime error related to MSVCR90.dll.

What is important this error didn't appear with Cameyo 2.0.892.0 and output package was smaller. Something is broken in new release.

Package creation/testing system is Windows 7 64bit.

Greetings,

Tom



__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Hello Tom,

Your package should work if you use Package Editor to change it from RAM mode to Disk mode.

RAM mode was just introduced in Cameyo 2.5, and we are keeping a list of virtualized applications that work only in Disk mode for troubleshooting to improve RAM mode.

For RAM mode to launch faster, less compression is used on the packages; therefore, the size is larger than Cameyo 2.0 packages.  A future version of Cameyo will allow the package builder to choose greater compression, but of course, that will increase the initial launch time.



__________________
Tom

Date:
Permalink   
 

Indeed but there are 2 little problems if I use Windows XP for package creation:

  1. If I want to edit package i need NET 3.5 Framework installed. Is this possible to edit package without .NET 3.5?
  2. Package created with 2.5.1139 is 2 x larger (20 MB vs 11 MB) than same package created with 2.0.889.0 ( maybe because of installed .NET? )

I setup package creation system light as possible without any additional software.

Greetings,



__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Without .NET Framework 2.0 or higher installed, only a basic Package Editor is available.  With this Package Editor, you can delete files from the package, for example, but you can't change Virtualization mode.

The package created by Cameyo 2.5 is larger because less compression is used to enable faster launches.



__________________
Tom

Date:
Permalink   
 

I tested this scenario:

  1. I created package with clean light Windows XP ( without .NET ). Package size is 17 MB.
  2. Run other instance of Windows XP ( with .NET ) to edit RAM -> DISK mode.
  3. Package after saving and changing mode is the same size 17 MB.

Why isn't it packed better? It still has the same size.

Greetings,

Tom



__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Yes, changing Virtualization mode does not affect the package size.  I recommended changing from RAM to Disk mode to prevent the error you reported in your original post.

Cameyo 2.5 is optimized for speed, not size.  A future version will provide the option to increase compression, which will result in smaller packages.  These smaller packages will not be as fast; the user will be able to choose which is more important, size or speed.



__________________
Tom

Date:
Permalink   
 

Ah ok :)

Indeed changing from RAM to DISK solved error problem. Anyway is there any chance that in new version RAM option in my case will work?



__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

We are keeping a list of virtualized applications that work only in Disk mode for troubleshooting to improve RAM mode, so yeah, the aim is for all of those applications to one day work in RAM mode, as well.  No ETAs can be given at this time because there are other things that have a higher priority, e.g. virtualized applications that don't work at all.



__________________
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