Cameyo

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: could not finalize package!


Member

Status: Offline
Posts: 8
Date:
could not finalize package!
Permalink   
 


I am trying to create a portable version of my personal database software so that I can take it with me on a USB drive. I just downloaded and ran Cameyo on computer. I started Cameyo and after it took the pre install shot of the computer, I installed my software program. Once done, I clicked Install Done. Cameyo started building the package but then stopped with the following message

Cameyo could not finalize package

APIRET=9

I hit ok and Cameyo closed.

What happened?  How do I fix this?

 

UPDATE:

i got Cameyo to create a portable package. I turned off all AV and firewall products and it completed without a hitch.

Now that I have my software program running in a portable exe file, how do I update it?  Once a month I have to update the database in this program to reflect additions and deletions of client information. If I create the portable image to run on other computers, how do I update the database file (.db) when changes are made to it?  The .db file is located in a folder in the program.



-- Edited by Big Dawg on Saturday 30th of April 2016 05:10:32 PM

__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Will your package write any changes to the database or will it only read from it?



__________________


Member

Status: Offline
Posts: 8
Date:
Permalink   
 

I'm not sure because I spoke too soon.

I found out that, yes my Cameyo package worked just fine, as long as it was connected to my computer that had the software already loaded, however, if I took the USB drive with my Cameyo package and tried to run it on a different computer, the package did not run. Evidently there is a part of the database that makes a call to some sql that then loads with the database and for some reason, isn't being picked up in the post scan done by Cameyo.

Is there a way I can have this software program CD sent to be properly built so that it will run completely on its own?



__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Did you package on a clean virtual machine?  Whenever one builds a package in a production environment, there is the risk that the system already includes some prerequisites for the program that won't get installed and included in the capture.  Taking such a package to a computer that does not have the same prerequisites installed could result in unpredictable behavior.



__________________


Member

Status: Offline
Posts: 8
Date:
Permalink   
 

I decided to try to create the package on a known computer that didn't have my business software previously loaded.

And "it appears" to have worked.

Once the package was created, I uninstalled the software from this computer and the package still opened up just fine. I took it to a different computer and it also opened up just fine. So I think I have a working package now.

HOWEVER, I still have the same question of how to update the database in this program once the package has been created.  My software DVD came with my original database file that I used to create the Cameyo package, so I started the Cameyo edit process and went into Files and highlighted the old database file folder and clicked the Red X to delete it and then clicked the Import icon and searched for the updated database file folder and placed it in the program where it should go. I then exited the Cameyo program and save my changes. Unfortunately...the old database file is still coming up when I open the Cameyo package. I went back to edit the folder and it shows the proper (new) database files in it, but these new database files are not being used when I try to open the package normally. 

What am I doing wrong? Was I suppose to delete the old database folder, exit and save the changes and then go back in to import the new database folder?  Is there some cache that needs to be flushed?

Oh, and to add insult to injury, I can no longer edit my Cameyo package on my Computer... I get "Failed to open package.API error: failure."

Even though I have rebooted my computer, thus I find that I have to take my USB drive to another computer just to do any updating. Annoying.

Thanks for any help you can give.

BD

 



__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

The method you used to replace the file within the package is correct if the package has never written changes to the file, e.g. if the package has never been run or if the package has only read the file but not written to it.  

If the package has written to the file that you wish to update manually, you have to copy the updated version to the package's sandbox.  Please note that making changes to the package's repository, including the sandbox, is an advanced user operation.  A careless change could cause the package to behave unpredictably.  Please make changes only to files that are app specific, i.e. it is best to avoid the Cameyo-specific files.

The default location of the sandbox is %AppData%\VOS\[AppID]\CHANGES.  Using a file manager, find your file in the virtual filesystem under CHANGES and replace it with the updated file.  If you have run different packages on the system, please be sure that you are copying to the right package's sandbox.  AppID should be the name of the virtualized software.  Now, your package should read the new file instead of the original or the file updated through Package Editor.

Regarding the Package Editor error, can you successfully open other packages?



__________________


Member

Status: Offline
Posts: 8
Date:
Permalink   
 

I'm not sure I understand your response...

"If the package has written to the file that you wish to update manually, you have to copy the updated version to the package's sandbox. Please note that making changes to the package's repository, including the sandbox, is an advanced user operation."

Are you saying that if I change something in my portable programs files (ie...changed a database entry and then save it) then I can't simply swap the database file in the portable version with my actual updated database file in my regular program, like I have been trying to do? That, instead, I have to go to the sandbox area and swap out the current database file with the updated file from my regular program? Since I can't open the editing feature in Cameyo I'm not sure where to find this Sandboxed area.

I made no changes to a file in my portable program and yet when I tried to updated it using the steps I outlined before, I still couldn't get the update to work.

"Regarding the Package Editor, can you successfully open the other packages?"

When you say Other packages, If you mean can I open and run my portable program package, then the answer is mostly. Like just now, I put my USB drive in my computer with the package and tried to open it...it failed. However, I rebooted my computer and tried again and it opened just fine. So the answer to your question is, I can usually open my package...I just can't use Cameyo for editing on this computer. I can, however, usually open Cameyo editing if I switch to a different computer.

Lastly, can I simply copy this Cameyo package from one USB drive to another without any issues?
And can I use an encryption tool, like Veracrypt to put this package in an encrypted container so that if the USB is lost or stolen, then no one will be able to access this database program but me with a proper password?



__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Big Dawg wrote:

Are you saying that if I change something in my portable programs files (ie...changed a database entry and then save it) then I can't simply swap the database file in the portable version with my actual updated database file in my regular program, like I have been trying to do? That, instead, I have to go to the sandbox area and swap out the current database file with the updated file from my regular program? Since I can't open the editing feature in Cameyo I'm not sure where to find this Sandboxed area.


Yes, that is what I am saying.  To be clear, if you change something through the package's interface, e.g. if you run your database package and make a change through the virtualized database program, all writes will go to the sandbox.  Some programs make changes in the background, so this can happen even if the user does not proactively change anything.  The sandbox cannot be accessed through Package Editor.  The default location of the sandbox is %AppData%\VOS\[AppID]\CHANGES.  If you are running your package from a flash drive, the default location is appname.cameyo.data\CHANGES on your flash drive in the same folder as the package.  You can access with a file manager.  Just be careful that you modify only files that are specific to your database program.

Big Dawg wrote:

When you say Other packages, If you mean can I open and run my portable program package, then the answer is mostly. Like just now, I put my USB drive in my computer with the package and tried to open it...it failed. However, I rebooted my computer and tried again and it opened just fine. So the answer to your question is, I can usually open my package...I just can't use Cameyo for editing on this computer. I can, however, usually open Cameyo editing if I switch to a different computer. 

Lastly, can I simply copy this Cameyo package from one USB drive to another without any issues? 
And can I use an encryption tool, like Veracrypt to put this package in an encrypted container so that if the USB is lost or stolen, then no one will be able to access this database program but me with a proper password?


By other packages, I meant a completely different package from the database program.  I understand you occasionally receive an error when trying to open your database package with Package Editor.  I was trying to ascertain whether the challenge comes from the package itself or Package Editor.  Do you have another package to try to open with Package Editor?

Most packages can be moved from system to system and used without issue.  If the software employs measures to protect licensing, there could be an issue.  Regarding Veracrypt, I would suggest you test it and see once we have the first matter resolved.  Cameyo offers encryption, but it is only for the sandbox, i.e. your changed database file would be encrypted but not the program itself.



__________________


Member

Status: Offline
Posts: 8
Date:
Permalink   
 

Update:

Well I don't really know why or how, but the package is now opening just fine AND with the updated database not the original one...just like I want.
So I created a encrypted container, on my USB drive, to put the Cameyo package in and it works fine in there as well. I don't have any other programs that I have created with Cameyo, only this one.
I can open the Cameyo Package editor with my Cameyo package on the USB drive just fine. I just can't edit it on my PC. However, I must not understand the naming convention you are using, because I can't find where appname.cameyo.data\CHANGES would be located once I open the Package Editor. Some more guidance would be appreciated.

To be clear, I don't change anything in the database file on my portable USB drive...the database program on my USB drive is just to be able to view it if I need information while out of town. The only changes that I would ever make would be the regular database program on my PC.

Considering how flaky this package has been, remember I supposedly updated the database file while in the Package Editor and yet the old database file kept showing up when I would open the package, thus I'm concerned about updating the database file, on my Cameyo package when needed in the future.

I really want this to work, as it saves me a lot of time from trying to install the complete database program on my USB drive, assuming it would even fit.

Thanks for your help in trying to get Cameyo to work consistently.
BD

__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

To access files in CHANGES folder, use a file manager, e.g. Windows Explorer.

mule wrote:


The default location of the sandbox is %AppData%\VOS\[AppID]\CHANGES.  If you are running your package from a flash drive, the default location is appname.cameyo.data\CHANGES on your flash drive in the same folder as the package.  You can access with a file manager.  Just be careful that you modify only files that are specific to your database program.


__________________


Member

Status: Offline
Posts: 8
Date:
Permalink   
 

Mule:
Sorry, but I cannot find "appname.cameyo.data\CHANGES" on my flash drive in the same folder as the package. Maybe how I created my package has something to do with this.
I made my database program portable using Cameyo and then copied my package to a Virtual copy of Windows 7 using VirtualBox Portable. This virtual computer is on my USB flash drive. I also copied the Cameyo edit program. Both are on the Desktop of my Virtual machine when I start it. Once the VM is up and running I can start my portable database and view my client files with no issues (remember...I never make changes to this portable database).
There isn't any folder, that I can find on the VM or residing on my flash drive with appname.cameyo.data\CHANGES. As a matter of fact, there isn't any such file on my regular computer either.
I also tried opening my Cameyo portable program with Cameyo to look in the file section, but there isn't anything like it in there either.
Obviously I'm not understanding what you are suggesting.
All I want to be able to do consistently is update the database program (made portable by Cameyo) on my USB drive with the latest database file from my regular PC whenever there are changes, in order to keep the database program on the USB flash drive current with my regular PC. And as you know, from my previous post, for some reason updating the USB drive database, using the editing tool, didn't work...until now...and I have no idea why it finally updated properly.
So if thisappanme.cameyo.data\CHANGES is the way to go, rather than how I was trying to do the updates with the Cameyo editor, I need a step by step of where to find this file, how to open it and how to edit it...otherwise, I guess I'm left hoping that I can update the database file consistently using the Cameyo editor when needed.
BD



__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

If you are running the package from a VM, the default location of the sandbox is %AppData%\VOS\[AppID]\CHANGES.  You cannot edit the sandbox with Package Editor.  Perhaps if you send me your package, we can understand each other.  Please use a friendly file-sharing site like WeTransfer that does not make the downloader jump through hoops and provide the url where your package can be downloaded.  Use your own email address if you use WeTransfer to get the download url.  If you do not want to make the package available publicly, you can PM me.



__________________


Member

Status: Offline
Posts: 8
Date:
Permalink   
 

OK...I think I found it.
After starting my VM on the USB drive, I found it was under... Users\my VM computer's name\AppData\Roaming\VOS\my package name\Changes\%Program Files (x86)%\my database program's name\my database file folder name\my database file name.

I can see the updated database file. So, in the future, when I need to update this file with the latest revised database file, would it be better for me to simply replace this file with a revised database file (paste the new database file over the current file) in this folder, instead of using the Cameyo edit function?
Thanks,
BD

__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Package Editor will not affect files in the sandbox, i.e. the CHANGES directory (any of its subfolders), so yes, please use a file manager to copy and replace any updated files necessary.  Remember, this is an advanced user operation: do not touch any of the other files; doing so could result in unpredictable behavior.



__________________


Member

Status: Offline
Posts: 8
Date:
Permalink   
 

Thanks for the update and warning.

I've always been quite proficient with computers so I will take your warning seriously.

I'm always interested in learning and knowing how things work so could it be possible that the reason my database was not initially changing to the updated database, while trying to use the Cameyo Editor, was because for some reason the package editor was not over-riding the same file in the sandbox? Thus even though I changed it in the editor, Cameyo still used the original database saved in the Sandbox. 

If this is correct, then how does anyone make file changes or updates to there Cameyo program using the editor?  Or is my situation somewhat unique?

In any case, I appreciate what the Cameyo program has done to make my program portable and especially appreciate your support and help.

Regards,

BD



__________________
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