installer puts program in ProgramFilesFolder

[rickford66]

Hello,

First off, I'm running LabVIEW 7.0.  My installer keeps putting my applications into a folder (that it creates) called "ProgramFilesFolder" and not the pre-existing "Program Files" folder.  When I build the app, the Installer Settings tab shows, under Default Installation Directory, "Program Files Directory".  There is nothing else on the list that looks anything like Program Files, so I would assume this is the correct setting.  Has anyone seen this, and if so, how do I get it to install in the correct folder?

Thanks.

[pincpanter]

I'm also working with 7.0 sometimes, but I never had this problem: your settings should definitely work. You may check possible wrong or strange settings in the Files... dialog.

Another possibility is to try recreating the bld file; in the past I got some errors that could only be cured by creating a brand new bld.

Hope this helps.

[rickford66]

This problem has been posted before, and a number of suggestions were posted with them.  None have worked.  I don't know if this is a bug in the installer or not, but I would think that NI would have a solution by now.  One of the earlier posts for this was back in 2004.

[altenbach]

Have you tried searching the registry for "ProgramFilesFolder"?

What is your OS? Could it be that your OS has some weird environment variables defined? Does the same happen if you install on a different machine?

[rickford66]

Yup.  I saw the comment on an earier post about the registry.  Not in there.  I never had this problem on this machine.  It only started in say, the last few weeks.  I've been building apps on this machine for years.  BTW, it's W2K.  Old apps do the same thing if I rebuild them.

[Eli_S]

Hi,

Have you tried creating a new installer for this same application? If so, do you see the same behavior? I find it very odd that you have created many applications on the same computer and this is the first time you see this happen. If this happens again with the new installer, can you try specifying a different destination from the list and see if then it puts it where it should go?

[rickford66]

After a long phone call with a very patient engineer at National Instruments, the problem has been solved.  One of my registry keys, "

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem, Entry:NtfsDisable8dot3NameCreation was set to 1 when it should have been 0.  The engineer knew almost immediately what to do, but he waited patiently on the line while paranoid (or should I say experienced) me had to make a backup of my registry before I would change this one entry.  Since this was a recent development, the engineer at NI thought that perhaps either a recent program install, or a windows update changed the state of the key.

Thanks for your suggestions, and thanks to David at NI for the solution.