Andy Maskell

I have succeeded in packaging my large standalone into a self-contained VirtualBox by following SourceAudio's excellent instructions in another thread. It was not until I read those that I realised that the "resource" folder had to be created in VirtualBox's %Default Folder% BEFORE adding its contents rather than just adding the whole folder directly. I also noted that the option to "Share virtual system to child processes" needs to be disabled for the standalone to work.

However, I have one tiny issue that I am interested to know if there is a solution for. My app uses a small .txt file to store the contents of a coll that contains two rows of parameter settings for my alarm clock and timer. Despite including the text file in the package bundle in an "other" folder created in the %Default Folder%, my app continues to read and write to/from the text file in its original location OUTSIDE the VirtualBox location. Is there a way to incorporate that file inside the VirtualBox such that it does not get reproduced in its original location?

This is one for @SourceAudio really...
I have succeeded in packaging my large standalone into a self-contained VirtualBox by following ... 

standalone-in-a-"virtualbox"

text file can be included into packed exe file, but it will be read only.

Packed exe will happily read and write it in any external path you specify,

or if you issue standalone path by something like this.

image.png

shows how to get path to patcher while editing, to standalone when run as standalone, to read the file if found or auto create it if not ...

text file can be included into packed exe file, but it will be read only.
Packed exe will happily read and write it in any external path you specify,
or if you issue standalone path by something like this.

shows how to get path to patcher while editing, to standalone when run as standalone, to read the file if found or auto create it if not ...



By carefully following the detailed steps provided by SourceAudio in another post, I was able to successfully package my big standalone into a self-contained VirtualBox. It wasn't until I read those that it dawned on me that adding the entire folder rather than just the "resource" folder's contents directly required the creation of the "resource" folder in VirtualBox's%Default Folder%. I also observed that in order for the standalone to function, the option to "Share virtual system to child processes" must be disabled

https://bestweedandfeed.com/fescue-grass-vs-bermuda/

By carefully following the detailed steps provided by SourceAudio in another post, I was able to successfully package my big standalone into a self-contained VirtualBox. It wasn't until I read those that it dawned on me that adding the entire folder rather than just the "resource" folder's contents directly required the creation of the "resource" folder in VirtualBox's%Default Folder%. I also observed that in order for the standalone to function, the option to "Share virtual system to child processes" must be disabledhttps://bestweedandfeed.com/fescue-grass-vs-bermuda/ 

Standalone in a "VirtualBox"