LabVIEW Run-Time Engine 8.2.1 - Windows XP 32-bit

Hi,
Which version of the LABView runtime should i donload to work on 32bit ?
there is only 64bit .....
Kobi Kalif
Software Engineer
Solved!
Go to Solution.

Kobi_K wrote:
Hi,
Which version of the LABView runtime should i donload to work on 32bit ?
there is only 64bit .....
The naming of that download mentioned by Eduard may have somehow mislead you, but LabVIEW 8.2.1 was only available as 32 bit version ever. The download says that it works for Windows 2000/XP/Vista 32 Bit and also the Windows Vista 64 Bit platform, but no tests have been made on Windows XP 64 Bit for instance and you would be on your own trying to run it on there. As Vista and Windows 7 are mostly the same it should also work for Windows 7 32 and 64 Bit although since Windows 7 was not available when LabVIEW 8.2.1 was released it was never tested and might have minor issues.
32 Bit applications will usually install just fine under 64 Bit Windows versions.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

  • Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

    With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
    -install using the plugin
    -install using LVRTE.exe
    -install after rebooting the server
    But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
    Is there any compatibility issues with the new Run-Time Engine 6.1 ??
    Thanks for your help
    Cyrille

    Cyrille,
    What is the error that you get when trying to install the run-time engine?
    Are you installing it from the LabVIEW CD, or did you download it from the web site?
    To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
    Also, try running the installer from the command prompt window, and use the following syntax:
    setup.exe/l*v
    This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
    Thanks
    Zvezdana S.
    National Instruments

  • LabVIEW Run-time Engine 7.1.1 installation failure on Windows 7 SP 1 32-bit

    I am attempting an installation of LabVIEW Run-time Engine 7.1.1 on my Windows 7 SP1 32-bit OS computer and the installation hangs.  This happens near the beginning.  Is there a compatibility issue?  The window does not have any error messages.  It says: "Updating System, The features you selected are currently being installed."  The progress indicator blinks periodically, but does not move forward.  Please help.  Thanks!

    I recently tried to install the LabVIEW 7.0 runtime engine on my Windows 7 (64 bit) machine to try out an old software. Ended up removing it quickly again, since any LabVIEW version I started up after that, including LabVIEW 2013 showed an installation dialog on startup about (updating installation information, please wait!).
    Basically there are so many possible problems why it could fail. Apparently the runtime engine installer had played with some other NI component that he had no idea would ever exist when it was created and caused that component to always think it needed to update itself to finalize its installation. In your case it could be anything from a missing Visual C runtime version framework that the installer simply expects to be present but doesn't since Microsoft has in the meantime released about 5 versions of Visual C and doesn't install all runtime versions anymore on newest Windows. Or it could be a conflict with your hyper-duper .Net Framework 4.5.x.y that the installer does not be prepared for. Maybe that or something else was not present on your 64 Bit machine where you could install the runtime engine.
    Basically the reasons for the install to fail are legion, and trying to figure it out is always more hassle than moving on and let old software be old software.

  • Why does "NI LabVIEW Run-Time Engine 6.1" window appear when I start LabVIEW?

    it also prompts "insert the 'NI LabVIEW Run-Time Engine 6.1' disk.
    Attachments:
    windows.jpg ‏26 KB

    Hi,
    There can be many reasons why this error would appear. Most probably, you have a broken installation of the Run-Time engine.
    Just reinstall the run-time engine from the LabVIEW 6.1 CD. You can also download it from our web site:
    LabVIEW Run-time Engine Version 6.1 for Windows 95/98/NT/2000/ME/XP
    Zvezdana S.
    NAtional Instruments

  • Is Labview Run-Time engine 2009 SP1 compatible with Windows 8

    I potentially need to install a Labview executable and Run-time engine 2009 on a Windows 8 OS.  From looking at the run-time engine support, it only looks like it only shows windows 7 down to XP.  Does anyone have any experience using Runtime 2009 on Windows 8?

    Hi Awhite144,
    The first version of LabVIEW to officially support Windows 8 is LabVIEW 2012 SP1. That being said, I would expect LabVIEW 2009 to work fine on Windows 8, and if you run into any trouble, feel free to post it here. LabVIEW 2012 SP1 installs a number of older LabVIEW run-time engines (including LabVIEW 2009), so it will install on Windows 8.
    I have not personally used LabVIEW 2009 on Windows 8, maybe if someone else has experience with it they can weigh in, but I expect it to work.
    As an important consideration, I assume you are talking about the full version of Windows 8, not Windows 8 RT. 
    Regards,
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments 

  • Error involving Report Generation Toolkit and Labview Run Time Engine

    Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

    I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
    Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
    I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
    I displayed my App.Property of APP.DI
    R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
    Any ideas ?
    Greg Klocek

  • Unable to locate the LabVIEW Run-Time engine

    Using LabVIEW 2011, I have built an executable and installer including the LabVIEW Run-Time engine. I built the app on a 32-bit system. I'm deploying it to a Windows7 64-bit system. When I ran the installer, rebooted, then tried to run the app, I got an error messsage stating "Unable to locate LabVIEW Run-Time Engine", stating that the LVRTE 2011 was needed to run the app, and asking if I want to download from NI. I have tried downloading the RTE and re-installing it, but when I try, I get an error message from the installer stating that there is a newer version of the RTE already installed, and the installer exits! I have tried un-installing the application, but have had no luck removing the RTE. Now I'm stuck. The re-installed executable application says it can't find the RTE, and the RTE installer says there's a later version already installed!
    I can't go forward or backwards!
    Prior to running the installer for this app, I had a working LVRTE for 2011, and was running some other executable LabVIEW programs on the target box. However, since this new application had additional components not included in the original install of the RTE, I built the new installer which included the additional components. Once I ran that installer, my problems began.
    In my frustration, I've tried downloading from NI both the 32 and 64-bit versions of the RTE, and installing them. I realize that the app was built on a 32-bit system, so the 32-bit RTE SHOULD have run it fine, but didn't.
    At this point I have removed the 64-bit RTE using the NIUninstaller. I believe I need to completely remove all 32-bit RTE components and start over, but I have not been able to. The 32-bit RTE does not show up in any un-install utilities I've found.
    What could be causing this problem, and how do I get past it??
    Thank you.

    One thing I did discover in my struggles is that the RunTime engine on the target box needs to be based on the environment of the development box. So if you built the app on a 32-bit machine, you would need to install the 32-bit RTE, even on your 64-bit target box.
    The RTE Uninstaller might not show up in the Windows Add/Remove Programs utility. In my case the 64-bit RTE uninstaller showed up, but the 32-bit did not. The NiUninstaller (C:\Program Files\National Instruments\Shared\NIUninstaller) did list both RTEs for uninstalling, but still didn't get me past the problem.
    I was finally only able to get past the problem by doing a system restore to a point in time prior to my changing of the RTE.
    Good luck.
    Dan

  • Include LabVIEW Run-Time Engine in C# Project Distribution

    I have written a software package in Visual Studio using C# which calls a number of functions from a dll which I have built in LabVIEW. I am now trying to produce an installation program for my C# package but can't quite work out how to include the LabVIEW Run-Time Engine in this installation.
    I am creating the installation program by defining a Visual Studio Deployment Project and I have added my LabVIEW dll to this. However, the dll requires the LabVIEW Run-Time Engine to also be installed on the target PC. I was hoping that there would be a set of files to implement the installation of the LabVIEW Run-Time Engine that I could include in my Visual Studio Deployment Project and do the installation of both my C# code and my LabVIEW dll (inc Engine) in one operation. Is this possible? Or do I need to produce a LabVIEW installation for my dll separately from the C# installation?
    Info:
    Development OS = Windows 2000
    Target OS = Windows XP
    C# Development Environment = Microsoft Visual Studio 2005 V8.0
    LabVIEW Version = 8.5
    Also, I am using the Order Analysis Toolkit and noticed that there seemed to be an 'Order Analysis Run-Time Engine' installed on my PC. Do I need this too?
    Thanks for any help.
    CAS

    Hi CAS,
    One way of automating the installation of the LabVIEW run-time engine is to use commands in a batch file (*.bat). These commands would be executed automatically at the same time as your distribution installer to install LVRT with your C# application. For more information on command line options, have a look at this KB. I don't have so much knowledge of C# distributions, though, so there may be a better way to approach this that someone else in the community could advise you on.
    With regard to the order analysis toolkit, you will also need this runtime engine installed. A point to note, though, is that the toolkit requires a run-time licence to be deployed in this fashion. It is now part of the Sound and Vibration Measurement Suite and needs to be licenced accordingly.
    I hope this helps!
    Best regards,
    Tom
    Applications Engineering, NI UK

  • 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

  • Error on installation of LabVIEW Run-Time Engine 8.5.1: "This application has requested the Runtime to terminate it in an unusual way"

    Hi,
    a colleague in India cannot install the LabVIEW Run-Time Engine 8.5.1 on Windows XP. On attempting to install, an error box is shown, which says:
    (window title)
    Microsoft Visual C++ Runtime library:
    (message box text)
    Runtime error!
    Program: C:\National Instruments Downloads\LabVIEW 8.5.1\Runtime Engine\setup.exe
    This application has requested the Runtime to terminate it in an unusual way.
    Please contact the application's support team for more information.
    http://img529.imageshack.us/my.php?image=runtimeerrorvt7.jpg
    I didn't find any relevant clues for this in NI forums. A search at Google brought me to http://support.microsoft.com/kb/884538/en-us, offering a HotFix to solve the problem. Unfortunately, the installation of this HotFix does not solve the problem.
    Do you know this behavior and do you have any ideas how the problem can be solved?
    Thanks in advance.
    Best regards
    Manuel
    Message Edited by Manuel Häderle on 10-07-2008 10:41 AM
    Solved!
    Go to Solution.

    Hi there
    log in as administrator and kill all processes not needed and try again. I've seen cases where one of these free download tweak applications (like "Memory Defragmentation" and stuff like that) caused that error. 
    Best regards
    chris
    CL(A)Dly bending G-Force with LabVIEW
    famous last words: "oh my god, it is full of stars!"

  • LabView Run-Time Engine 2009 installation failure

    Hi,
    I have problem to install Labview Run-Time Engine 2009.
    This error occur:
    Die Installation von NI VC2008MSMs x86 ist auf Grund des folgenden Fehlers fehlgeschlagen.
    Auf den Windows-Installationsdienst konnte nicht zugegriffen werden.
    Die kann vorkommen, wenn Sie Windows im abgesicherten Modus ausführen oder der
    Windows-Installer nicht korrekt installiert ist. Wenden Sie sich an den Support, um Hilfe zu erhalten.
    (The installation of NI is VC2008MSMs x86 failed due to the following error.
    The Windows Installer Service could not be accessed. That can occur when you run
    Windows in Safe mode or Windows Installer is not installed correctly.
    Contact your support personnel for assistance.)
    I've tried to reinstall and reregistrate windows installer, I've even tried to upgrade windows installer to version 4.5
    I've installed Microsoft Visual C++ 2008 Redistributable x86.
    Im runing Windows XP Service Pack 3
    (Microsoft Windows Version 5.1 (Build 2600.xpsp_sp3_gdr.100427-1636_ Service Pack 3))
    I have no problem installing other programs, I can for example install labview runtime engine 7.1.1.
    So my question is:
    How to solve this problem, how can I make an installation of Labview Run-Time Engine 2009 on this computer that gives me the error described at the begining?
    Best regards
    Simon
    Solved!
    Go to Solution.

    Hi,
    I have already looked at that forum issue.
    So I have already tried to delete all keys in regedit.
    The problem is, if I continue with my installation, about 10 other new issues will appear.
    And my installation will not complete, it will fail.
    The installer does not install, it will tell me that the installation failed, and it will only install a few things.
    Not all the things that I need to run my program.
    See attached pictures ibn zip file to see some errors I receive, I only picked a few of them out.
    So when I then tries to start my program I will recive the error in picture program error. (Run-time engine error)
    So it's not only that the installer tells me that the installation doesn't go through, it doesn't.
    Best regards Simon
    Attachments:
    Pictures.zip ‏414 KB

  • Error 1334 (in LabVIEW Run-Time Engine 7.1.1 setup) when launching VB6's IDE

    What's going on here?  I have LabVIEW 7.0 and Visual Basic 6 installed on this Win-XP computer.  When I open VB6, I always get what looks like a Windows Installer error:
    First, it asked me for the location of "lvruntimeeng.msi", which I located for it.  The next progress-window says:
    NI LabVIEW Run-Time Engine 7.11
    Please wait while Windows configures NI LabVIEW Run-Time Engine 7.11
    Finally it fails with this error-message window:
    NI LabVIEW Run-Time Engine 7.11
    Error 1334.  The file 'NIMDFManifestFileId.53736431_DBEC_4582_B072_2F1F0A2C4EA6' cannot be installed because the file cannot be found in cabinet file 'lbruntimeeng_mft'.  This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
    [OK]
    The two windows repeat twice each time I launch VB6's IDE, and that causes a long delay.  What can I do to prevent this error?
    Message Edited by citizenDAK on 04-23-2008 01:34 PM

    Yes it occurrs every time I launch VB6.
    For a long time now, at least many months.  It's not every day that I need to open good old VB6.  I was hoping it'd just 'go away' but it hasn't.
    I don't know what changes lead up to it.  LOTS of things have been updated, security-patched, etc...  (It is XP.)  I've even un-installed the runtime, then re-installed it when I kept getting the same prompt.  Don't have any idea why, I was hoping you could tell me from the specific file named in the error.  (Google didn't find it for me, and neither did searching ni.com)
    p.s.,  Sorry I left out a decimal and copy/pasted it several times...  should've said "NI LabVIEW Run-Time Engine 7.1.1"

  • NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

    This problem seems similar to the post "Resource not found error in executable on developmen​t machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
    I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards. 
    I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010.  The code was using a custom executive and my task was to rewrite the test using TestStand 2010.  I reused the majority of the old code.  The old code used NI-5660 to control the 5600 and 5620.  When I run my sequence using the LV Development System and TestStand, it runs without any issues.  When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues.  It warns that the nipxi5600u​.dll was not initialized correctly.  Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter.  The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again. 
    I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace.  I also used Dependency Walker to track down the problems with the nipxi5600u​.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32).  I have also performed a Mass Compile to make sure everything was running in LV 2010.  If I skip the steps involving the 5660, my entire sequence runs fine. 
    The previous code was running with the LabVIEW Run-Time Engine without any issues.  Is there just a step I am missing?  Has anyone seen anything like this before?  I can send screenshots of errors to provide more detail if necessary. 

    I have tried some more things and still can't get it to work.  I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs.  This did not change the results. 
    When I try to run my sequence, The first error I get is shown in Error 1445.bmp.  This happens when I try to use the NI 5660 initialize.vi.  If I click ignore, the next error I see is shown in Error -20551.bmp.  When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp.  When I close TestStand, I get the error LabVIEW Fatal Error.bmp. 
    Attachments:
    Error1445.JPG ‏164 KB
    Error -20551.JPG ‏174 KB
    Error loading nipxi5600u.JPG ‏9 KB

  • Installer Error of LabView Run Time Engine 6.0.2 "premature"

    I cannot Install the LabView Run Time Engine on a Computer which runs on Windows 2000.
    The Installation breaks on start with the Error Message: "Installation ended premature, because of an Error!"
    Does anyone know what to do is ?
    Thanks for Help

    It's rather difficult to guess why since the error does not give any more information, but there are a few things you can try. First, if you are installing from a CD, try downloading the installer to your desktop first and then run it. CD-ROMs can sometimes run slower that the installer and this can cause problems. Also, check to see what other NI software may have been installed on this machine and determine if any of it could conflict with the 6.0.2 Run-Time Engine. Just possibilities but hopefully they can get you going!
    J.R. Allen

  • Are LabVIEW VISA functions supported by LabVIEW Run Time Engine?

    I have an executable file that I created using LabVIEWS Application Builder. When I run the application on another computer that does not have LabVIEW installed, it crashes with a Windows message stateing the my application has generated erros and will be shut down by Windows. I have isolated the problem as having something to to with VISA Reasource Names.
    Does anyone know if there has been any issues regarding the use of VISA function in LabVIEW Run Time Engine? The version of LabVIEW that I have is 6.0.2. The version of Run Time Engine is 6.0 .
    Dan

    Yes there are issues with the RTE 6.0 and VISA. Use the RTE 6.0.2
    LabVIEW, C'est LabVIEW

Maybe you are looking for