64-bit vs. 32-bit Absolute Pathing

[daltore]

I "wrote" some LabView code a few nights ago and sent it to our mentor, who subsequently tried to open it, but was greeted with numerous warnings asking him where files were located. I've figured out that the problem is that I have 32-bit LabView installed on my 64-bit machine, and so it put all of the files in "Program Files (x86)". However, our mentor is running 32-bit Windows, so his LabView installation is just in "Program Files". I'm the lead programmer for our team, but other people will be trying to access and edit these files, and all of our other computers that run LabView are running 32-bit. Is there any way to make the file locations translate automatically short of me reinstalling LabView into "Program Files"?

[Greg McKaskle]

Can you be more specific about where and what files?

LV stores references between files in two ways. If the file is inside of one of the special LIB locations, then the path is stored as LIB/blah/foo/bar.vi. If the VI is not in one of those locations, then it is stored relative to the caller.

So, if you move folders of VIs and maintain the relative path, say using a zip or such, the path above should not matter.

When the relative or LIB path doesn't actually point to your VI, LV starts searching using the search path. You can let it search, show it where they are, put the relative paths back, or update the search path to include some of your code directories.

In general, you do not need change where LV is installed, and in fact putting it in the Program Files on a 64 bit machine may be a bad idea if it isn't actually 64 bit. Not sure.

Does that help? If not, give more info.

Greg McKaskle

[jmanela]

I tried installing labview on multiple 64 bit machines; none of them could get a complete installation. I have tried many things and after hours of trying, i settled for just running on a 32 bit and it worked fine.

[daltore]

Okay, so apparently they fixed the absolute path issue a couple of years ago, and it really IS handled in a registry entry like we thought it should be. The real problem was that our mentor's computer didn't have the LabView update *face palm*. Thanks for the help.

[elmer_fud]

Originally Posted by jmanela

I tried installing labview on multiple 64 bit machines; none of them could get a complete installation. I have tried many things and after hours of trying, i settled for just running on a 32 bit and it worked fine.

I am having no problem running the version of labview supplied with the KOP on a 64 bit machine. I have Windows 7 pro 64 bit with a core 2 duo processor. You might be having a problem with a firewall, antiviris, or something else not liking labview. It also takes a few hours to install LabVIEW in most cases.

Can you post of a screen shot of the error it is giving you when you try and install it on a 64 bit machine