LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Steve_TDiode

Consistency in downloads installation folder locations

Status: Completed
Implemented in LabVIEW 2012 SP1

Downloads and updates that self-extract to an installation image are often placed into different folders under "\National Instruments Downloads" even for very similar products or even updates to the same product.

 

For example, LabVIEW 2012 extracts to "\LabVIEW English\2012" but the f1 update extracts to "LabVIEW Development Environment\2012 (32-bit) f1"

The 2012 Run-Time Engine extracts to "\LabVIEW Run-Time Engine\2012 (32-bit) f1" while the 2011 Run-Time Engine extracts to different folders depending on which update it is.

The 2011 f2 extracts to "\LabVIEW\Run-Time Engine\2011 f2 32-bit\Standard" but f3 extracts to "\LabVIEW\2011f3\Run-Time Engine\Standard"

 

This can make it difficult when looking at one of the top level folders to know what it contains.  Is it a Run-Time Engine, an update ,or a main program file ?  If the main program and all its updates were under one folder, then by copying just that one folder one would know that all files and updates were included in the copy.

 

Steve

 

8 Comments
Roy_F
NI Employee (retired)

Good point and we can probably consider this a bug. We have a CAR filed (363975) that is closely related to this. I'll add a link to this thread and request a response be posted here when investigated. My expectation is that we will correct this via the above CAR or file another one for this specific issue.

 

Roy

MaryH
Member
Status changed to: In Development
 
heel
Member

May I point to this related idea http://forums.ni.com/t5/LabVIEW-Idea-Exchange/NI-Downloader-should-download-all-the-relevant-files-i... - the download process should allow single-file download and not do media spanning when this is irrelevant.

 

Nowadays you rarely burn DVD's from downloaded installations thus multi-file to enable media spanning is just a nuisance.

Jeff-P
NI Employee (retired)

CAR 363975 has been fixed in LabVIEW 2012 SP1 which just released today.

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

Steve_TDiode
Member

For this LabVIEW 2012 SP1, both the 32 and 64 bit default installation folders are the same at C:\National Instruments Downloads\LabVIEW\2012 SP1 32-bit

 

Run Time Engine default installation folders for both 32 and 64 bit are the same at C:\National Instruments Downloads\LabVIEW\2012SP1\Run-Time Engine\Standard

 

There is an f1 Patch for the 64 bit version, whose download link has a link to Knowledgebase 66EDKHLF which has a link to related info for a 32 bit f1 patch whose link gives an error.  I was not able to find a 32 bit f1 patch on the driver download site.

 

The description for the 64 bit f1 Patch states it should be applied to all versions of 2012 SP1 not just for 64 bit.  I found this to be confusing because it implies it can be used for the 32 bit SP1 as well.

 

Steve

mniedernhuber
Member

Since 13.09.2012 in Development, BUT

 

NI-DAQmx 9.7
NI-DAQmx Run-Time Engine 9.7 - (Configuration with MAX)
NI-DAQmx Run-Time Engine 9.7 (Core)

 

are all extracting to the folder: C:\National Instruments Downloads\NI-DAQmx\9.7.0

 

Steve_TDiode
Member

LabVIEW Run-Time Engine 2012 32-bit and 64-bit install to different folders :

C:\National Instruments Downloads\LabVIEW Run-Time Engine\2012 (32-bit) f3
C:\National Instruments Downloads\LabVIEW Run-Time Engine\2012 (64-bit) f3

 

but the SP1 update to LabVIEW Run-Time Engine 2012 installs both 32 and 64 bit to the same folder :

C:\National Instruments Downloads\LabVIEW\2012SP1\Run-Time Engine\Standard

 

Also note that there is not a SPACE character in the SP1 RTE folder name "2012SP1" instead of "2012 SP1".

Including the SPACE would make the folder name consistant with folder enaming for LabVIEW itself.

 

Steve

 

G-Money
NI Employee (retired)
Status changed to: Completed
Implemented in LabVIEW 2012 SP1