Runtime LabVIEW 8.2.1 - Windows XP 32-bit

Hello

What version of LABView runtime should I donload to work on 32-bit?

There is only 64-bit...

Hi Kobi,

Runtimes are not compatible, you need the same version that you have developed the VI in.

Tags: NI Software

Similar Questions

  • Excellent black screen when running LabVIEW 12.0 on Windows 7 (32 bit)

    I've migrated just a LabVIEW 8.0 on a Windows XP-based computer program to work with LabVIEW 12.0 on a Windows 7 computer (32 bit).  I've converted all the Excel 2000 (.xls) files in Excel 2010 (.xlsm, .xlsx) files.  When I run the program LabVIEW, I notice that the Excel icon that appears is "yellow" for a 1/2 second intermittently.  This sometimes causes the LabVIEW program hang up.  When you hover over the icon, you do not see the Excel file.  All you see is a black (or white) screen where data must be and the file is not closed properly.  If I close the file, then the LabVIEW program errors.  I will attach a screenshot.  This program retrieves data to Oracle every 20 minutes to update products in the wafer fab queue.  It works 24 / 7.  I went in Excel and set Options, centers of confidentiality, macros settings - enable all macros and checked access approved to the the_VBA project object model.  (Suggestion of our IT tech).  When I restart the LabVIEW program, it works very well.  When he is going to update the first time, Excel goes into vapor lock!  (white screen).  I downloaded the TDM Excel Add - In, but the notes said it was already installed on LabVIEW 9.0 and later versions.  Any ideas?  Mark


  • Labview 2010 8.1 Windows executables

    Greetings,

    My development computer is a Windows 8.1 with LabView 2010 Professional machine. I created a project and published an executable with success. Obviously this works on my development system.

    However, I have another machine Windows 8.1 (new installation, nothing about this). First, I installed the runtime Labview 2013 because (a) I thought that it would be compatible for older versions, and (b) it says it supports the Windows 8 operating system. Unfortunately when I tried to run the executable it gives me the following error:

    Could not locate the LabVIEW runtime engine.

    .. .requires a 2010 version (or compatible) Labview engine of execution. Contact the seller to [name of program] to correct this problem.

    Okay, so I uninstalled the runtime of 2013 and restarted. Then I installed 2010 thought that is what it takes.

    Gives me the exact same error as above.

    I saw similar problems of windows 8, but nothing I could find about it.

    What I am doing wrong?

    Thanks in advance.

    Why install the runtime 2013 when you have an application of 2010? You must also install the appropriate number of bits of the runtime.

    Why not simply create an installer?

  • Runtime LabVIEW 2013

    I want to start a .exe file, written with LV 2013 SP1 on a windows 7 64-bit PC.  I downloaded and installed the Labview 2013 SP1 runtime.  When I try to run the .exe, a message box appears indicating that I need to install runtime Labview 2013!

    I tried to "Reinstall" to verify that it has been installed and I was unable to install the software becaue what is already installed.  I don't know where to go from here...  Help please!

    Are you sure THAT you have installed the 64-bit version of LabVIEW and created the .exe from that?  I ask because the vast majority of people use LabVIEW 32-bit even on Windows 64-bit OS.

    My theory is that you have 32-bit LabVIEW.  You have created an .exe with which would be also 32-bit.  Then download the 64-bit version of engine performance by mistake because you have the 64 bit version of Windows.  In this case your .exe 32 bits will complain of not installing a run-time engine.

  • LabView 8.5.1 embedded works on Windows 7 64 bit or 32 bit?

    I would like to install LabView 8.5.1 on Windows 7. Is it possible with 64 or / and 32-bit? Thank you!

    Thanks a lot for your help.

    So I just installed LabView
    integrated Blackfin 8.5.1 on Windows 7 64 bit and it still works
    without 'XP mode' also with the USB-emulator and VisualDSP ++ 5.0. Notice: the
    DVD - the installation program is not running on W7 (error-12) but you can install all
    module separately by using the configuration of modul of the DVD files.

    I'm happy, thank you...

  • Runtime LabVIEW Developer Suite DVD

    Hello!

    I need to install runtime Labview on a PC.

    Where can I find it on my DVD of Developer Suite?

    (I would like to avoid downloading LV RTE Web site NOR)

    Thanks in advance for any help,

    Marco

    I'm sure it's for MS-DOS device drivers.

  • LabVIEW stopped working after windows update

    Windows XP 32 bit with Labview 2012 Service Pack 1 - Windows Auto-implementation to date 11 may 2013.  After update, Labview crashes at startup, nothing suits him.  I tried to restart and all the usual nonsense.  You can open the screw, but then the CPU enters a State of usage of 50% or 100% (which seems to be random) and Labview hangs just w / of the hourglass icon and never answers.  I can open NI MAX and querry various instruments, but crashes just Labview itself (start or any what VI).

    I need fix as soon as POSSIBLE, very tight edge scientist, cannot wait TO open their doors Monday morning.

    Help, please!


  • labview 6.1 with windows system error 7

    I use vi Labview 6.1 to control an oscilloscope Tektronic and a universal pulse BNC via GPIB-USP connection generator. The vi worked very well with the windows XP system. The system was changed to Windows 7. Then the error (Trigger signal is not recognized. Check the connection between "Trigger out" and "at the ins') comes every time I started running vi. The link between "Trigger out" and "at the ins' works under mannual mode, so it's really ok.

    Compatibility between Labview 6.1 and windows 7 would be the reason? If so, are there tips for using Labview 6.1 on windows 7?  Thank you.

    Thanks for your help.

    The solution turns out to be very simple... The new Windows system is the German version so that the old windows English version.           , is used for decimal in German instead of .

    Thank you all!

  • LabVIEW 2011 32 bit, fully ER3000, Windows 7 64 bit

    I currently have Labview 2011 32 bit installed on a machine running Windows 7 64 bit.  I am trying to run the screw in the attachment below, but I get the error that the function called in the DLL has failed and that FULLY. DLL may be used.  A reflection as to why this is happening?  I already checked to ensure that the referenced path in function call of the nodes of the screw is correct... any help is appreciated!

    ~ Avi


  • Install runtime LabVIEW CVI?

    Hello

    who runs the Update Service NOR suggest to download a patch of 226 MB for runtime LabVIEW 2012... (everything I installed knowingly was CVI2012)

    --> How can I check if the computer has this engine installed, which is the name of the file to look for (and it takes the CVI)?

    Thank you!

    Wolfgang,

    The LabVIEW run-time engine is not necessary for any CVI program to run, but it's an addiction of some of the tools ADE, such as the Finder of the example and the Manager of distributed system (used to configure network variables).

    Luis

  • LabVIEW 8.5 on Windows Vista

    Hello

    LabVIEW 8.5 is Windows Vista compatible? Also I have problems with devices and hardware drivers DAQ - mx? I use NO-USB6008.

    Thank you

    Have you tried a search? This question has been asked a number I don't know how many times. No, wait, don't bother, let me you type words into the search bar for you...

    Compatibility of the versions of Windows with LabVIEW

    NOR-DAQ and LabVIEW (for Windows) version compatibility

    EDIT: I see that LV_Pro had already posted the same answer.

  • How to read the tag bluetooth data in labview 2015 running on Windows 10

    Hi all

    I have a Development Board Nordic semiconductor nr51. This card is programmed as a tag bluetooth which simply announces his address with 16 bits of data appended to the end.

    My laptop came with loan materials smart bluetooth. I installed an app interactor lighthouse to bluetooth on my laptop and the software is able to detect the tag as if shown on the image below.

    I wanted to write a LabVIEW program that will simply be careful bluetooth headlights and notify me in my computer every time a lighthouse with the specified address is detected. This mobile application below is provided by the manufactuerer of the Board of Directors and I wanted to develop a LabVIEW program something similar to what will read the given data and extract values.

    Somehow, all the sample applications provided data only shows how to read and write in a connected bletooth device but not analysis for tags. I also tried using the Bluetooth ' discover ' and it does not detect the bluetooth beacons.

    Could someone provide me with the necessary information or example program for detecting / reading of tags bluetooth in LabVIEW 2015 running on Windows 10?

    Do I need to install a third-party software to read data from bluetooth?

    Bluetooth in LabVIEW function nodes using the Winsock interface to access bluetooth resources. This works very well for Bluetooth 2.0 devices but not Bluetooth 4.0 devices WHEAT aka. Microsoft has created a completely different interface for these resources API as the model of overall service for WHEAT devices has radically changed.

    The API to use WHEAT devices is the API of the GATT (generic attribute profile) in Windows. There is supposedly a .net interface available that you can try to use (Windows.Devices.Bluetooth.GenericAttributeProfile). The WinAPI to lower level (https://msdn.microsoft.com/en-us/library/windows/hardware/hh450825(v=vs.85).aspx) is a C DLL API and does not lend at all to be called directly by the LabVIEW call library node, since some of the parameters of the function are quite complicated and you need to also access the SetupDI APIs to enumerate resources WHEAT and even harder to function parameters. In order to access this low-level API to write an intermediate DLL which results in low level API C a more acceptable API for LabVIEW.

    Another possible problem is that Windows don't at least in Windows 8 not allows devices to pair per program. Microsoft wanted to force developers in the use of the "inbox" experience, which means that all users must go through Microsoft provided service pairing, instead of each request for implementation of his own matching technique.

  • Runtime error! Program: C:\windows\LIVING-1. SCR

    ASK FOR HELP WITH THE EXECUTION ERROR

    Recently, I received an error message on a frequent basis.  It's: Runtime Error!  Program: C:\windows\LIVING-1. SCR this application has requested the execution to terminate in an unusual way.  The section on States of error message "Microsoft Visual C++ Runtime Library" Cany anyone help me with this problem?

    What version of Windows are you using?

    What is your current screen saver on?

    Is it one that you have installed?

    You can try to change the screen standby and if necessary, uninstall it.

    http://Windows.Microsoft.com/en-us/Windows-Vista/change-screen-saver

  • Runtime Labview 8 coexisting with Labview 7

    Hello everyone!

    I have 2 questions about the coexistence of the different versions of Labview:

    First question: we have several machines with Labview 7 runtime engine, and where this Labiew version executables are running. Now, I was new software to develop using Labview 8, and I want to run them in the same devices. I guess for these new programs I install runtime Labview 8. Pourrait that affect running the old software? Because for us, the good performance of the oldest is crutial.

    Second question: in the other machine, installed 7is Labview. Also in this machine, we would launch an executable of Labview 8. We want to keep there Laview 7. So, if I install runtime Labview 8, could that affect Labview 7?

    Thank you!!

    Just install runtime LabVIEW 8. It does not come into conflict with the former engines of execution or the facilities of LabVIEW.

  • LabVIEW application developed on windows can be installed under linux?

    Hi all

    I use suite developer LabVIEW 2009 on windows 7 PC. I was wondering if the application created with labview on PC can be deployed on the linux platform? If not, is it possible to develop the LabVIEW application on windows to deploy on linux platform?

    I was also wondering if computers single-board as Beagleboard, Raspberry Pi are loaded with linux, labview application can be deployed on these computers?

    (in simpler words, I wonder, with existing suite of Labview 2009 developer on windows, can I develop a data acquisition application and deploy it on single-board computers that have linux installed on them.)

    Thank you!

    Nilesh-

    To create an exe on a Linux platform, you need LabVIEW for Linux with its application builder. You can open the source on the Linux machine.

Maybe you are looking for