I have a .vi I build into and application and create an installer for using LabVIEW 7.1 and Application Builder. In the "Advanced..." settings for "Installer Settings" I have configured a .bat file to run (run executable after installation) after the install of my app is complete. This works fine and dandy if the install location is a simple path to a local disk. In the batch I register some Active X ocx's, create some folders, etc. If the install location is changed to a mapped drive I run into issues. For example, I have another disk on my local PC that is mapped to the Z drive. If I select the Z drive as the install location, the App installs properly and the .bat file runs correctly HOWEVER the directory I pass to the .bat file (Install Directory) is not passed properly in this scenario. Is this a bug in Application Builder?
Here is what I pass to the .bat (which is configured in the "Command Line Arguments" of Installer Settings>Advanced):
"[INSTALLDIR]" "[SOURCEDIR]" "qm.lic" "[INSTALLDIR]\Support Files\qm.lic"
Here is the relevent part of the .bat file:
cd %1
mkdir Test1
mkdir Test2
cd Test1
mkdir Configurations
cd %2
COPY %3 %4
As you can see, %1 is the "[INSTALLDIR]". When I install normally to a local disk (i.e. Program Files) this gets passed properly to the batch. I know this because the directories "Test1" and "Test2" are created properly in the installed location. However, if I install to a mapped drive, the "[INSTALLDIR]" is not passed properly. The "Test1" and "Test2" folders are created in the system32 folder. It is like it cannot associate the INSTALLDIR with a mapped location so it defaults to the system32 folder. Any insight as to what is going on here would be much appreciated.
Steffan Benamou