CVI 6.0 install build of my software is being put in wrong directory

[judyh]

I have a software package that, when it installs, puts the executable and support files into the "ProgramFilesFolder" rather than the "Program Files" folder in the Windows C drive.  It does not get added to the start menu.  The setup.exe creates the "ProgramFilesFolder" in addition to a "ProgramMenuFolder" and puts the .exe and .uir file into the "ProgramFilesFolder".  The resulting directory is "C:\\ProgramFilesFolder\MyTestAppFolder\" that the install defaults to when I'm running the installer.  This is true for any build I try regardless of the project.  I've checked the build options and they are the same as previous builds that I have done without any issues.

The only things I can think of that happened recently that may have affected this are:

1.  I was trying to build another application recently that was written in CVI 8.5.  I was unable to do the build because of the version differences - got a popup telling me that.

2.  I have recently run some registry clean up tools to try to solve a totally different issue I'm having with VB6.0 software.

Any ideas?

Thanks,

Judy

[judyh]

Hi,

Forgot to mention I am using CVI 6.0 on Windows XP.  The 8.5 version is installed on another developer's computer in my workplace.

Judy

[LuisG]

Hi Judy,

Make sure that your distribution settings look like the screenshot I attached below. Those two controls listed under "Install Location" at the top of the dialog should determine the default installation location for your application. In addition, make sure that the "Group Destination" control on the bottom of the dialog does not override the installation location for a given group of files.

Luis

[judyh]

Hi Luis,

I followed your instructions.  Still no luck.  It's doing exactly what it did before.

Judy

[LuisG]

Judy,

Would it be possible for you to zip up and attach the installer files here in a forum post, so that we could take a look at them?

Thanks,
Luis

[judyh]

Hi Luis,

I'm putting it up here now.  This is pretty much a dummy program, but it illustrates the problems with the install directory.

Thanks again for your time,

Judy

[LuisG]

Thanks, Judy.

Can you check the following setting in your system registry?

Key: [HKEY_LOCAL_MACHINE]\System\CurrentControlSet\Control\FileSystem
Value: NtfsDisable8dot3NameCreation

My guess is that this value is set to 1 (it is normally 0). There was a bug in CVI 6.0, 7.0 and 7.1 that caused it to build the installation location incorrectly in the installer when this value was set to 1. If it is set to 1, try changing it to 0, then rebuild the distribution kit and see if it fixes the problem.

Luis

[judyh]

Bingo!!! That did the trick Luis.  Thank you so much for your help.  I'm still not sure what caused this and, since we have an open version 8.5 license, I'm getting the upgrade put on my machine just in case the mix of code files across the different versions is what caused the issue in the first place.  I have been making builds for couple of years with this version with no problems, so something we did to my machine last week changed that registry value.

In any case, you are a gentleman and a scholar and I appreciate all your help!

Judy Harrigan