LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview installation - not compatible directory

You are confusing the posts.  There are two different people here.  I am the one that butchered the system two days ago.  The other guy used the "OFFICIAL" uninstaller.

0 Kudos
Message 11 of 20
(1,529 Views)

@hartzde wrote:

You are confusing the posts.  There are two different people here.  I am the one that butchered the system two days ago.  The other guy used the "OFFICIAL" uninstaller.


Ah, sorry about that. So why did you hijack an existing thread instead of starting your own? (especially since the problem is different!)

0 Kudos
Message 12 of 20
(1,527 Views)

Because we might have the same solution and my thread isn't getting any response.

0 Kudos
Message 13 of 20
(1,519 Views)

And what post would that be?  I only see you posting to this thread and something about the installer.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 14 of 20
(1,500 Views)

Ill write whats happening again, since there seems to be some confusion in here.

 

I change default install directory to manage free space on partitions.

I have my convention that all esseintial programs go to C, all other applications go to other partition. Ive been doing this for long time, not only with small programs but also with complex applications like Autodesk software family, Matlab and even other applications from National Instruments and none of them ever had any problem with that.

This helps me  with system backups  (only critical data in C, faster operation, scanning) and helps with keeping C drive empty (especially when you for example when you have small SSD disk just for system files for fast boot and regulad disk for all other data. Letting all installed do what they want would quickly lead to filling C drive).

 

 

So yeah, instead of default C:\Program Files (x86)\National Instruments installation path for LabView 2014 32bit i changed it to partition where i install all my applications D:\National Instruments .Installation was completed but it was 32bit instead of 64bit. As i said i used official uninstaller from Control panel-> Programs and features then i selected National Instruments application and picked "Change" there i picked remove and selected all contents. After that i rebooted my computer just like i was told by uninstaller.

 

 

Everything went without errors. The directory D:\National Instruments have been removed by uninstaller. And any traces of LabView in control panel->programs and features were gone. LabView 2014 32bit supposedly ceased to exist. 

 

 

Then i downloaded LabView 2014 64bit and started installation. I set installation directory again to D:\National Instruments (because i can, if old program was removed why would i think that i wont be install it again in place where there is nothing left) and here to my suprise installer tells me that "There is incompatible application installed in that directory already"....

0 Kudos
Message 15 of 20
(1,484 Views)

You didn't try to install both 32 and 64 bit to the same directory, did you?  They are separate programs and should be installed into their own directories.

 

Oh, and they can exist side-by-side because of this.  You don't have to have one or the other.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 16 of 20
(1,474 Views)

Logically thinking, i didnt try to install them in same directory. Because before installing 64bit version in same directory as 32bit version i use official National Instruments Lab View uninstaller that was supposed to remove 32 bit version. Logically thinking, after uninstalling 32 bit version there should be nothing preventing me from installing 64 bit version in that directory.

 

Theoreticaly thinking i did install it in same directory as 32 bit version but as i said, the 32 bit version is no longer there since uninstaller removed it and all its files.

 

And the problem is that 64 bit version installer still thinks that "there is something in that directory", in directory that actually no longer exists and is supposed to be created by installer.

0 Kudos
Message 17 of 20
(1,461 Views)

It is not thinking that there is still anything in there! It simply refuses to install a 64 bit applciation in a directory that is inside Program Files (x86) which is reserved for 32 bit applications on Windows 64 bit! That is a Microsoft imposed Windows limitation not an installer error!

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 18 of 20
(1,448 Views)

He's not installing to the x86 directory, rolf.  So that's not the issue.

 

Try changing the folder to D:\National Instruments\LabVIEW 2013 64

 

I know this isn't the exact folder you are trying to use for your organization.  But, if you install any other NI software you will likely want it in the same folder.  You could also try to change "National Instruments" to NI.

 

If neither of these work, we can try something else.  But, may I ask why you want the 64-bit version of LabVIEW?  Most users, including myself, prefer the 32-bit version due to a wider range of toolkit and module support.  I have only had one application I've ever worked with where I could use the 64-bit processing.  But, that was likely a product of bad architecture than it was a need for 64-bit processing.  I was a LabVIEW beginner when I put together some terrible code.

0 Kudos
Message 19 of 20
(1,436 Views)

The only time I ever used LabVIEW 64-bit (other than just fooling around) was something about a dll that the 32-bit version refused to work in WoW64 mode, so they had to use the 64-bit driver instead.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 20 of 20
(1,420 Views)