LV 7 Installer chooses WindowsVolumeDirectory as Default Installation Directory

[waldemar.hersacher]

System: LV7 and Windows XP

I created an Installation package with the App. Builder. The Default Installation Directory is set to "Root Directory". If I ran this Installation Package the Default Installation Directory is set to "D:\WindowsVolumeDirectory\" even on machines which do not have a 😧 drive.

Making the installation wiht the same bld-file under Windows2000 the installation will choose "C:\".

Has anyone else seen this behaviour or knows an solution?

Waldemar

[Liz F]

Hello Waldemar,

Thank you for contacting National Instruments. I researched existing issues with LabVIEW 7.0 and have not been able to find any similar problem. I then tried to reproduce the issue you are talking about. I made a simple VI with LabVIEW 7.0 in Windows XP and set the Default Installation Directory to "Root Directory". The installer then chose C:\ as expected.

Have you been able to try building the installer on more than one computer running Windows XP? Perhaps on the computer you initially build on, the Root Directory is D:\, and that carries over to other machines.

I would be happy to try something else out based on your suggestions if you wish. Please let me know what you would like to do from here.

Have a great day!

Liz Fausak
Nati
onal Instruments

[waldemar.hersacher]

Hello Liz,

thanks for your help.

First:
We have a special configuration on all of our PCs. On C: we have the system with the windows and the programs folder. On 😧 we have the user profile folders (documents and settings) and all other local project data. The project itself is located on a mapped network drive. On our machines we are not allowed to write to the programs and system folders with the exception of LabVIEW.ini, user.lib, instr.lib and Help. Also we cannot write to any registry keys under HKEY_LOCAL_MACHINE with the exception for the file association for LabVIEW files.
I have activated an out of order PC with a standard XP installation on one partition. There the installation package will be built correct.
BTW Windows XP is alway
s the professional version.

Second:
One of my colleagues have contacted NI Support and the people in Munich couldn't reproduce the problem. They said they will forward it to USA.

Third:
The configuration we use seems to be seldom used but not exotic. One of my customers use the configuration with Windows 2000. Since I'm not part of the PC support group I don't know if this is a recommendation from Microsoft installing secure or easy to maintain systems. On this customers machines standard users are not allowed to write to the C: partition. They even do not see it in the Explorer.

Waldemar