Search the Community

Hello, I have to create an installation executable. I have a bunch of old dos programs and supporting files, plus a zip file, and a dosbox executable to install via a LabVIEW VI built into an executable via app builder. The LabVIEW VI needs to copy the old dos programs and supporting files from the project to the user's hard drive and place the files in their correct locations on the users' hard drives. Plus, the LabVIEW VI needs to extract the zip file and launch the dosbox executable to install dosbox. The source of the old dos programs and supporting files, zip file, and dosbox executable needs to be virtual as the users will not have access to my hard drive nor any network mapped drives where the installation files will initially be located. What I cannot figure out is how to call the path and files from the project tree into the LabVIEW VI without getting an error regarding absolute path after I have copied the files from my mapped drive into the a virtual folder in the project tree. Since the user won't have access to my hard drive nor a network drive when this VI is built into an installation application (they will have a usb stick or disk), how do I get around this error? I thought that was the point of the virtual folder so that I did not have to have an absolute path to the source files in the VI. I know that I can include the source files using app builder but that does not address the issue of controlling the installation using the VI. Any thoughts how to accomplish this using LabVIEW, virtual folders, and their project tree?