Cameyo

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Parameter Repackage creates an error
Anonymous

Date:
Parameter Repackage creates an error
Permalink   
 


Hi,

i've just virtualized an app and want to integrate the changes in the virtual filesystem (automatically) into the xyz.cameyo.exe. My first try doesn't work as expected but just throw a fatal error

"Could not repackage: APIRET_FILE_CREATE_ERROR"

After a run with changes in the virtual filestucture i've just started the
xyz.cameyo.exe -repackage
as written in the manual. I am using the latest version of cameyo 2.0.831

I don't find anything about this error ... so what i am doing wrong? Are there any prerequisites missing?
Or am i wrong and repackage doesn't mean that the folder xyz.cameyo.data was repacked into the xyz.cameyo.exe and update it for the next run...?

Thanks in advance for any help and thanks for this neat piece of Software.
smile



__________________
Anonymous

Date:
Permalink   
 

It must happen this way.

After starting this thread, i just try it again for a few times. And magically it seems that the repacking-procedure run at last.

But i'm just interested in the meaning of this error and some answer for what could be wrong the times before?

I've like to run this thing as a custon event under "On stop (unvirtualized)" is this the right place for an automatic repackage? Or can't this process be started as custom event?



__________________


Senior Member

Status: Offline
Posts: 268
Date:
Permalink   
 

FILE_CREATE_ERROR is an error creating the file. It means the final executable could not be created. Insufficient space / permissions? Security program blocking it?
You can investigate why it happens with tools such as Process Monitor.

As to "On stop (unvirtualized)", yes, this is where you could insert a command to repackage.

__________________


Member

Status: Offline
Posts: 24
Date:
Permalink   
 

Afaik, when the application is launched, the virtualization software keeps the lock on the file until everything is closed. Perhaps the process in the package wasn't quite finished when you were running the -repackage command?

__________________
Anonymous

Date:
Permalink   
 

Hi and thanks for the answers.

Good to know it's the right way i've tried.

I will test some scenarios to find out what the problem can be...



__________________
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