LabVIEW RTE 8.2

Yesterday I installed LabVIEW RTE 8.2 in a PC to make some tests of the new functionalities. Now I want to uninstall it from the computer, which already has LV RTE 7.1, and I can not find it in "Control Panel">>"Add/Remove Programs">> "National Instruments Software", could anybody tell me how can I clean my PC from 8.2
Thanks,
Iñaki

Couple questions for you:
Does it show up as LabVIEW Run-Time under Add/Remove Programs, like Elsa's screenshot?
Did you install any other National Instruments Software that might use RTE 8.2? If you've installed any other NI software with it, it will be hidden in National Instrument Software - and will uninstall with the program that it was installed with.
It wouldn't hurt to have RTE 8.2 on there - did it break any of your programs?
We could uninstall it manually (or atleast remove references to it), but let's make sure there are no dependencies before we go that route.
TheDillo

Similar Messages

Difference between LabVIEW RTE and TS LabVIEW RTE

Ok, this may be an easy one but still I would to have it clear. What is the difference between using LabVIEW RTE and TS LabVIEW Runtime Server to run LabVIEW modules/steps in PC's with TestStand Deployment licences???
Thank you,

Hi,
The TestStand LabVIEW Adapter can run VIs
using any of the following LabVIEW environments, or servers: the LabVIEW
development system, the LabVIEW Run-Time Engine, or a LabVIEW executable built
with an ActiveX server enabled. The Teststand LabVIEW run-time server
(TestStandLVRTS) is a version of the third option written way back at a time before the LabVIEW run-time engine is what it is now.
The only reason you would possibly want to use the TestStandLVRTS is when you
have VIs written with versions of LabVIEW older
than 6.1.
Have a great day,
Ecleamus Ricks, Jr.
National Instruments
Applications Engineer

Using LabVIEW RTE vs. LabVIEW ActiveX Automation Server (TestStand LVRTS) for a TestStand Deployment and experienceing Unabel to Launch LabVIEW.Application ActiveX Automation Server Error 18001

I am developing in TestStand 4.2.1 and LabVIEW 2009, I have accomplished the following:
1. Deployment package is built and deployed on PC
2. PC has activated TestStand Deployment License
3. LabVIEW 2009 RTE was selected as the adapter for the sequence and thus I believe the deployed testexec.ini contains this.
I am experiencing the following error: "see attachment".
Is the LabVIEW RTE the right selection?
Is there something I may have missed in building the deployment?
Do I need to register the ActiveX server.
THere seems to be conflicing solutions based on Version of TestStand and LabVIEW!!
Thanks!!
Attachments:
TS_LV ActiveX Error.doc ‏77 KB

Howdy mobiux,
Please consider KnowledgeBase 4V58058Z: -18001 Errors in TestStand. If you're using Vista or Windows 7, then this may apply as well. You might also consider ensuring you have the proper LV version active in the TS Adapter Options.
Warm regards,
pBerg

Setting Search Directory with LabVIEW RTE

Hi,
I've LabVIEW 8.0.1 run time engine installed on target computer and would like to run LabVIEW executable on target computer. I also have required low level support VIs for developed VIs.
Question is: how do I set the search directory for low level VIs with LabVIEW run time engine installed on the system.
Suggestions/comments are appreciated. Thank you.

If your hierarchy is the same as was in the IDE, then there won't be a need to search for the VIs. If the VIs are not found where they are expected to be, then LV (including the RTE) starts to search for them first in the folder where the VI\application is and then in the folders in its list. To change the list, you need to place the viSearchPath key in your application's INI file. You can copy this key from the labview.ini file and then modify the paths listed in it.
Try to take over the world!

Determine if LabVIEW RTE Installed

We're looking at creating a third party installer for our application, which can exist as both 32-bit and 64-bit LabVIEW executables for Windows. My problem is I'm not sure how to check for the appropriate LabVIEW runtime.
It seems if I peer into the registry under HDLM\SOFTWARE\National Instruments\LabVIEW Run-Time\ I can see a list of RTE version numbers. Are these supposed to reflect what's installed on the system? If so how would I go about distinguishing the different architectures (32- vs 64-bit)?

I don't have an answer, but if you have a virtual machine you could install a couple of the run time engine and see if you could figure it out yourself.
When I've created installers using Inno Setup I still use the NI generated installers for actual program installation. I just use Inno Setup for everything else.

LabVIEW RTE Search Paths Capitalization [LV/TS]

Not sure if this belongs into LV or Ts so I'm posting on both.
I'm getting the following error when I try to run a sequence in TestStand 4.1 with the LabVIEW 8.5 RTE as my adapter.
Is there a flag in the ini config file that I can set to make my paths not case sensitive???
Thanks,
<<-N->>
Message Edited by << - N - >> on 07-01-2008 11:57 AM
Attachments:
Error2.JPG ‏32 KB

Nice Error ; )
For me it looks like a TestStand Error - Did you tried what's written : To find all the steps who call "tkwca200 basic setting.vi" and select load dynamically into the TestStand Step option.
Another idea is to have only one step who call this VI and see if it work..and then add another one, and see what happen.
Hope it will help
Chris (not very good in TestStand..)

LabVIEW RTE Search Paths Capitalization [LV/TS]

Not sure if this belongs into LV or Ts so I'm posting on both.
I'm getting the following error when I try to run a sequence in TestStand 4.1 with the LabVIEW 8.5 RTE as my adapter.
Is there a flag in the ini config file that I can set to make my paths not case sensitive???
Thanks,
<<-N->>

Hi
Jonathan,
We found a workaround moving the folders around and that seems to fix the problem. I talked to a support engineer on the phone yesterday and he confirmed that this was a bug in the TS-LV adapter.
This is the procedure we are following to fix the problem:
Create a new VI in C:\MyProject\Projects\Component\Everything.vi
Add all the VI's within Component as sub-VI's to "Everything.vi"
Close LabVIEW
Move the whole directory of C:\MyProject\Projects\Component to C:\Component
Open Everything.vi. Help find the VI's it is having a hard time finding.
Close LabVIEW
Change C:\Component\Product\Common to C:\Component\Product\xxommon
Open Everything.vi. it should automatically find everything without asking you for help
Close LabVIEW
Change C:\Component\Product\xxxommon to C:\Component\Product\Common
Open Everything.vi. it should automatically find everything without asking you for help
Close LabVIEW
Move Component back under MyProject directory structure
Open Everything.vi. Help find the VI's it is having a hard time finding.
Close LabVIEW
Cross your fingers and see if it works this time.
<< - N - >>

CVI application asks for Labview RTE

Hello,
I have installed an application made with CVI 2010 several times on different computers without any problem but now on 1 computer I get the following error when I try to start the application:
Labview Run-Time Engine 7.1 Configuration failed
Please find attached MSI logs.
How can I solve this issue?
Thanks
Bertrand
Attachments:
Problème DTI.doc ‏152 KB

Hi again
Of course, the installation of an autonomous application should not (and usually do not) require any other component than the RTE of CVI and the drivers used by the applciation (if you call an acquisition board for instance in the program).
Should you want to proceed to a clean deinstallation procedure on the computer causing trouble, you can download MSI Blast from the following link :
http://forums.ni.com/t5/Multifunction-DAQ/i-am-looking-for-MSI-Blast-a-utility-to-remove-NI-DAQ-driv...
Of course, you should use this program with caution.
Removing every acquisition board from the computer before running it is also a good idea.
After that you should install all the programming software you want to use, install the drivers and then reconnect the boards.
An other way to solve the problem would be to make sure that your installer is not requiering useless components.
To repair the installer in this case, you can use the following documents (the procedure is written for LabVIEW, but it should be the same under CVI).
How Do I Stop the Missing Distribution Notification Each Time I Build An Installer?
Why Do I Get A "Missing Distribution" or "Distributions Needed" Error When Trying to Build an Instal...
I hope this information helps.
Best regards,
Guillaume H.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> NIDays 2011, le mardi 8 février au CNIT de Paris La Défense

LabVIEW RTE 6.1 for Linux. HowTo?

I want to use the Plug-In from this package with Netscape
6.0 to access a remote panel. Works fine on a Windows
machine with the RTE for Windows. But every time I open
the same page with Netscape 6 within Debian Linux I get
the following message:
This page contains information of a type (application/x-labviewrpvi) than can only be viewed with the appropriate Plug-In.
Although I installed the RTE for Linux and made a Symbolic link in .netscape/plugins ti LVNPlugin.so this
message will not go away?
What's wrong? Can anyony help?
Thanks in advance,
Armin Herzer

Armin,
Is it OK for you to actually copy the LVNPlugin.so to .../netscape/plugins? This is what I have done on the support machines here in Applications Engineering and it works great. I have Netscape 6.2 installed in /usr/local/netscape so I have the plugin copied to /usr/local/netscape/plugins/LVNPlugin.so. Try updating your Netscape to see if that helps as well. The message you are getting means that Netscape does not even see the plugin.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

LabVIEW 8.0 Run Time Engine

Hi,
I've a question about LabVIEW 8.0 run time engine.
I installed "LabVIEW_8.0_Runtime_Engine" from the NI website, but NI software in Add/Remove Programs does not list LabVIEW 8.0 Runtime Engine. However, LV 7.0 and 7.1.1 run time engines are listed in there.
Did anyone notice this?
I also have installed TestStand 3.5 on the same computer.
When I run an executable created in LabVIEW 8.0, I get the error message:
"VI version is too early to convert to the current LabVIEW version"
Comments/suggestions are appreciated.
Thanks.

CarlaU wrote:
The first thing that I would check is to go into Measurement and Automation Explorer (MAX) and click on the Software Tab. I would then check to see which version of the LabVIEW RTE shows up (if any). In theory, if the RTE shows up in MAX, then it should show up in Add or Remove Programs under National Instruments Software (highlight this and click Change....this should pull up a list of all NI products on your computer).
It's in MAX, but not Add/Remove Programs>NI
CarlaU wrote:
If it doesn't show up there, then there are two other things that can be done. The first one involves modifying the Windows Registry. There are a great KnowledgeBase article that discusses how to do this in order to remove the driver.
Nope - there's nothing to do with the RTE there either.
CarlaU wrote:
The second idea is to use a utility we have that I cannot post on the forum. If you create a service request via email or phone then we would be able to help you get the older versions fully uninstalled. You can create a service request at www.ni.com/ask. I hope this helps!
Thanks Carla - I'll try that avenue.
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

LV RTE cannot open project files that have .lvlib references in Dependencies

I'm writing a LabVIEW DLL to inspect LabVIEW project files, and I've noticed that if a project has a .lvlib reference in its Dependencies, then the Run-Time Engine contradicts itself about whether or not it can find the project file:
Project.Open returns error 7 (file not found)
Project.GetFileLVVersion is successful
Here are snippets from my G and C code that exercise this behavior:
int openStatus = StatusSuccess;
char* projectVersion = createStringWithLength(VersionStringLength);
printf("Analyzing %s\n", pathString);
OpenProject(pathString, &openStatus, projectVersion, VersionStringLength);
printf(" Project written in LabVIEW %s\n", projectVersion);
if (openStatus == StatusSuccess)
printf(" Opened project file.\n");
else
printf("Error: Could not find project file, or file was not a project file (error code %i).\n", openStatus);
However, when running in the development environment, both methods succeed.
Is this a bug, and if so, is it fixed in LabVIEW 2014?
Here is how you can reproduce it:
Prerequisites:
LabVIEW 2013 SP1 32-bit
ConEmu for a good console -- https://code.google.com/p/conemu-maximus5/wiki/Downloads
minGW for compiling a program to use the LabVIEW DLL -- http://sourceforge.net/projects/mingw/files
.lvlib reference in Dependencies breaks Project.Open in LV RTE
Unzip the attachment into a temporary directory (eg c:\xtra\temp)
Open "OpenProject.lvproj" in LabVIEW.
Build "Open Project Library".
Using ConEmu with a bash prompt, navigate to the temporary directory.
Type make
$ make
patching file `builds/platdefines.h'
gcc -std=c99 -g OpenProject.c -o OpenProject.exe -lOpenProject -Lbuilds
6. Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
$ OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Analyzing c:\xtra\temp\OpenProject.lvproj
Project written in LabVIEW 13.0
Opened project file.
7. Notice that both invoke nodes execute correctly.
8. Type OpenProject 'c:\xtra\temp\OpenProjectWithLvlibDep.lvproj'
$ OpenProject 'c:\xtra\temp\OpenProjectWithLvlibDep.lvproj'
Analyzing c:\xtra\temp\OpenProjectWithLvlibDep.lvproj
Project written in LabVIEW 13.0
Error: Could not find project file, or file was not a project file (error code 7).
9. Notice that the version node succeeded while the open one failed.
10. Type diff OpenProject.lvproj OpenProjectWithLvlibDep.lvproj
$ diff -u OpenProject.lvproj OpenProjectWithLvlibDep.lvproj
--- OpenProject.lvproj Tue Nov 4 11:28:28 2014
+++ OpenProjectWithLvlibDep.lvproj Tue Nov 4 11:32:37 2014
@@ -13,7 +13,11 @@
<Property Name="server.vi.propertiesEnabled" Type="Bool">true</Property>
<Property Name="specify.custom.address" Type="Bool">false</Property>
<Item Name="OpenProject.vi" Type="VI" URL="../OpenProject.vi"/>
- <Item Name="Dependencies" Type="Dependencies"/>
+ <Item Name="Dependencies" Type="Dependencies">
+ <Item Name="vi.lib" Type="Folder">
+ <Item Name="NI_MABase.lvlib" Type="Library" URL="/<vilib>/measure/NI_MABase.lvlib"/>
+ </Item>
+ </Item>
<Item Name="Build Specifications" Type="Build">
<Item Name="Open Project Library" Type="DLL">
<Property Name="App_copyErrors" Type="Bool">true</Property>
Here is another way to trigger this behavior, which also shows that LabVIEW only sometimes tidies the Dependencies item:
Open "OpenProject.lvproj" in LabVIEW.
Add a new VI to the project and place the "Application Directory" file path constant its block diagram.
Select "File » Save All (this Project)" and use the default name for the new VI.
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is an error again, as is expected.
Remove the "Application Directory" file path constant.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice the problem is gone, as is expected.
Re-add the "Application Directory" file path constant to the block diagram.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is no problem, which is surprising as there should be an error since the Dependencies item hasn't been tidied.
Close the new VI and remove it from the project.
Select "File » Save All (this Project)"
Open "OpenProject.lvproj" in a text editor.
Notice the Dependencies item has been tidied.
Re-add the VI back to the project.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is an error again, as is expected.
Solved!
Go to Solution.
Attachments:
LVRTE_OpenProject.zip ‏10 KB

NInjaneer_wow wrote:
The same behavior occurs in LabVIEW RTE: a new project with an Application Directory constant in a blank vi will return error 7 - file not found, but still return the correct version of LabVIEW in which the project was created.
I've been experimenting with workarounds for this behavior, and I found one.
When I provide the LabVIEW path for libdir in my executable's ini file, the run-time is able to load and inspect the project file.
libdir="C:\Program Files\National Instruments\LabVIEW 2013"
While it's expected that a stand-alone executable may be placed on a system that doesn't have the LabVIEW IDE, it's still surprising to me that the Run-Time Engine cannot find LabVIEW's standard library without some explicit guidance. What other considerations contribute to that behavior?
References:
LabVIEW configuration file/Paths -- http://labviewwiki.org/LabVIEW_configuration_file/Paths

NI-MAX/NVIORef.dll and RTE 8.2.x nightmare. pls someone sends me a RTE 8.2.1 dll?

hi there
i just installed LV 7.1 PDS 2005Q3 (default installation), and after that LV 8.5 PDS 2007Q4 (default installation). all works fine except the NI-MAX panels (e.g. devices test panels etc.). see attached ni-max (sorry for the german version..). this is annoying because i cannot add any devices etc.!
LVBroker needs the RTE 8.2.1 , well OK, i downloaded the RTE 8.2.1 and ran the installer. the installer says "8.2.1 already installed", and so does MAX (see rte attachment). so the installer does nothing at all. the only content of the \Shared\LabVIEW Run-Time\8.2 - directory is the NVIORef.dll with version 8.2.0.131. i assume this is the 8.20 dll version, and not the 8.2.1.
i'd like to replace this single dll with a "real" 8.2.1 dll. can someone please send me this dll?. or does someone have a better idea?
the NVIORef.dll can be found in the directory \Shared\LabVIEW Run-Time\8.2, you can find out the version number in explorer with right click on the dll and then click the "version" tab page.
thanks in advance
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"
Attachments:
ni-max.JPG ‏18 KB
rte.JPG ‏72 KB

Chris,
I just checked my LabVIEW 8.2.1 installation, and the version of the NVIORef.dll in the Runtime directory is still 8.2.0.131.
BUT: this is not the only content of the Runtime directory, as you can see in the screenshot attached to this post.
What OS are you using? If it is Microsoft Windows 2000, be sure to have at least SP3 installed before running the LabVIEW-RTE Setup.
Regarding the broken Test Panels in MAX - do you have any drivers installed (VISA, DAQmx, ...)? If so, did you reinstall them after running the LabVIEW 8.5 setup?
From my personal experience, I dare recommend you a clean new installation of both LabVIEW versions and the 8.2.1 runtime engine, best performed in the version order (7.1, then the 8.2.1 RTE, than 8.5.
There is a forum entry with a download link to MSI blast and a very good PDF which points you to the Windows Registry keys that you need to delete after deinstallation, which you can find here:
http://forums.ni.com/ni/board/message?board.id=250&message.id=34373&requireLogin=False
I think it's worth giving a try.
Attachments:
version check1.gif ‏59 KB

Increased Installer Size in LabVIEW 8.5

I have an installer for an application I wrote in LabVIEW 8.5.1 that includes nothing but the application itself and the LabVIEW RTE. It used to weigh in at ~75 MB, but since I installed LabVIEW 2009 the installer now takes up ~115 MB. I poked around some and it appears as though some of the extra space is being used to include 64-bit compatibility, but is there anything else going on here? Can I set any options to reduce the size to something closer to the original or is this something I'm stuck with?
Message Edited by Casey May on 09-03-2009 02:12 PM

Did you test that on a machine where no LabVIEW 2009 was installed?
When I build a LabVIEW installer in 8.5 on a machine where only LabVIEW versions up to 8.6 are installed I get a size for the installer volume of about 69MB (and everytime I do a build, also a prompt to insert the disk drive from which I installed the LabVIEW 8.6.1 update!)
What I guess happens here is that LabVIEW 2009 installs various shared component installers onto a machine that get picked up as dependencies by earlier LabVIEW runtime installers. For me this is not an big issue as long as this causes no problems when installing, due to binary incompatibilities between component versions.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

What files do I send to be upgraded from LabVIEW 5.1.1 to LabVIEW 2012?

OK. Just to be clear. I am a complete newb to ANYTHING LabVIEW or LabWindows related. I am a programmer, but I have never used any version ever. That said, I am responsible for the upgrade process of getting our old LabVIEW 5.1.1 system up to date. The old system (still running and doing it's job everyday), is an old Windows NT v4.0 SP6 system running LabVIEW 5.1.1. You can just imagine how ancient this is by today's standard.
Have I set the stage properly? I hope so. Newb, Ancient LabVIEW version 5.1.1, Windows NT 4.0, upgrading from 5.1.1 to 2012.
Now here is what I "think" I know about what is required. Because LabVIEW 2012 will not directly read in, process and /or compile LabVIEW 5.1.1 files, I must first open and save the files using an intermediate version of LabVIEW (specifically 8.2.1) to bring the files up to a version that 2012 can handle. I have noticed in reading the Version Conversion forum, that I can attach a zip file of my LabVIEW files and one of the resident Gurus will convert it for me and give them back - quite nice I think.
Now, I have what I think are all of the required LabVIEW vi and llb files that make up this system we have in place, but I want to be sure before I just post a bunch of stuff.
What exactly do I need to zip up and what can I leave out?
Are there LabVIEW vi and llb files in a "project" that are not needed?
Are there any setup/configuration/project specific files I need to include?
Are there any limitatations to this conversion process that I need to be concerned with - such as various toolkits/suites/modules that may have been used but are no longer supported?
Secondly, I am not really comfortable with posting my vi and llb files for the world to see (and possibly use) as I am not the owner of said modules, just the user/future developer who will be responsible for insuring they stay up to date. Is there any way I can send my files to a specific NI guru via email instead of just posting them?
Solved!
Go to Solution.

So if I understand you correctly, all I really need to do is to get LabVIEW 8.2.1, and update my .vi, .lib, and any .ctl files to that version.
Is it a simple matter of just opening the files and hitting something like SAVE AS, or just SAVE and it will do this? Once done, LabVIEW 2012 will then allow me to open them and do what I need to do? Do I have to save them into LabVIEW 2012 first, or is that automatic when I try to recompile them?
When I get a copy of LabVIEW 8.2.1 (eval version), do I have to get all of the pieces (modules, toolkits, etc.) in order to update the 5.1.1 files? Based on what is installed on that NT v4.0 system, we have the following items installed:
NI VISA
NI ComponentWorks 3D Graph
NI DataSocket
NI LabVIEW 5.1.1 Advanced Analysis Library
NI LabVIEW RTE 5.1.1
NI LabVIEW v5.1.1
NI Measurement and Auto Explorer 1.1
NI-488 2.1.60
NI-DAQ 6.6
NI-PAL 1.3.110
NI-Reports
NI-VXI/VISA
You mention DAQ. Our program uses NI DAQ v6.6 now. I have LabVIEW Developer 2012, so I just download the DAQ files for it and it will replace the NI DAQ v6.6 library files we use now?
Thanks for your help so far. If we had a support contract in place, this wouldn't be an issue. However, as I stated, I am not the owner of the files, just the currently assigned caretaker, and part of my task is to get from where we are now on this ancient hardware/software platform, to the latest and greatest. However, I am specifically not allowed to just place the files on a public forum for all to see. It just isn't done. We can send them to a known location and a known entity, but not to just anyone/anywhere as a public forum is by its very nature.
I know there is nothing you guys can do if I cannot give you the files, but thanks for helping me to do it myself. Getting an eval copy of 8.2.1, et. al is probably what I have to do here.

LabVIEW RTE 8.2

Similar Messages

Maybe you are looking for