I am new to the forum and even newer to portable apps I have tried to find information hopefully to point where I have went wrong in creating what I want, countless attempts to sort for myself with a lot of searching on Google.
I have downloaded Cameyo offline v3.1.1446 ran it on VMware clean Windows 7 x86 and Win XP pro x86 I am wanting to create portable chess programs that will work on the computers I have. Now the problem is when I try the built program on non virtual machine odd things are happening, apart from slow .exe opening, which I could live with had this been the only problem. I will try my best to explain, in hope maybe someone else has this software and is familiar with it, maybe came across the same problems as myself.
I would like to make Chessbase Fritz chess 14 x86 into a portable, this builds fine on virtual machine I add several engines, some books and a few databases and then try on another PC this is where the fun begins, most engines which were installed prior to moving some show but are not selectable, clicking does nothing . I cant uninstall engines without running the software back through Cameyo and then its back to square one. I have tried isolated builds, despite this the finished attempt still wants to look into program files, and documents on the non virtual computer. maybe I have misunderstood portable apps, I thought they could be used without any footprint on a PC, ie, self contained.
Can anyone explain why this is happening, apologies for a lengthy first posting.
Thank you
Smokes
-- Edited by Smokes on Sunday 16th of July 2017 10:41:38 AM
Hi
Can anyone tell me how to "Run your app with the "-Repackage" parameter (i.e. "MyApp.cameyo.exe -Repackage")
Keeping the app the same across computers is what I want, and would think this is the whole purpose of making something portable?
I followed instructions on page 15 of pdf manual, this point its obvious,to have something the way you want and make sure it works before final build.Trouble starts when I move to another computer or VM system.
Each package has a virtual filesystem. When it looks inside Program Files and Documents, it checks the virtual filesystem first. You can edit the package to restrict it from accessing the host system if that is what you really need, i.e. Strictly isolated.
Parameters are generally run from the Command Prompt.
Thanks for the reply, there are ton of folders on initial build, are can any files and folders that can be removed before final build which seems very big from initial testing.
Once the package is built, you can use Package Editor to delete any undesired folders and files.
You can prevent directories from being captured by editing Packager.xml to include whatever locations you wish under <PathsToAvoid>. The default location of Packager.xml is %AppData%\VOS\Cameyo\PROG\%Program Files%\Cameyo.
I have tried to find information hopefully to point where I have went wrong in creating what I want, countless attempts to sort for myself with a lot of searching on Google.