VI backwards compatibility with older engines of execution

Currently, I have developed a VI in Labview 8.6.1.  I also created an exe file to make it so that I can run on a different computer.  However, the other computer has an older version of the Run-Time engine installed, and so my program cannot be run on this computer without upgrading the runtime of 8.6.1.  But... this computer also has some programs that run on this version of the runtime.  I have two options here, but I do not know the effects or how to do it.

(1) install a newer version of the runtime engine (8.6.1) - this will break the current functionality of the programs already on it?

(2) is it possible to have my VI run on earlier versions of the Runtime Engine?  If so, how do I?

Thank you.

As dennis said simply install the new runtime. We have machines that have 5 versions of the engine runtime on them and we have not encountered any problem.

Tags: NI Software

Similar Questions

  • Nexus 1000v VSM compatibility with older versions of VEM?

    Hello everyone.

    I would like to upgrade our Nexus 1000v VSM 4.2 (1) SV1 (5.1) to 4.2 (1) SV2(2.1a) because we are heading of ESXi 5.0 update 3 to 5.5 ESXi in the near future. I was not able to find a list of compatibility for the new version when it comes to versions VEM, I was wondering if the new VSM supports older versions VEM, we are running, so I must not be upgraded all at once. I know that it supports two versions of our ESXi.

    Best regards

    Pete

    You found documentation, transfer of the station from 1.5 to latest code is supported in a VSM perspective.  Which is not documented is the small one on the MEC.  In general, the VSM is backward compatible with the old VEM (to a degree, the degree of which is not published).  Although it is not documented (AFAIK), verbal comprehension is that MEC can be a version or two behind, but you should try to minimize the time that you run in this configuration.

    If you plan to run mixed versions VEM when getting your upgraded hosts (totally fine that's how I do mine), it is better to move to this enhanced version of VEM as you upgrade the hypervisor.  Since you go ESXi 5.0 5.5, you create an ISO that contains the Cisco VIBs, your favorite driver async (if any), and the image of ESXi 5.5 all grouped together so the upgrade for a given host is all of a sudden.  You probably already have this cold technique, but the links generated by the Cisco tool below will show you how to proceed.  It also gives some URLS handy to share with each person performing functions on this upgrade.  Here is the link:

    Nexus 1000V and ESX upgrade utility

    PS - the new thing takes clones your VSMs offline.  Even if they are fairly easy to recover, having a real pure clone will save some sauce secret that otherwise you may lose in a failure scenario.  Just turn off a VSM, then right click and clone.  Turn on again this MSM and failover pair HA, then take to the bottom of it and get a clone of it.  So as a security measure, this upgrade, get your clones currently out of the current 1.5 VSMs, then some time after your upgrade some clones offline, saved from the new version.

  • Workstation 12 Pro backward compatibility with previous versions.

    After having been informed on a cat to support Workstation 12 Pro is fully compatible with all previous versions, I buy the product.   After installation, I try to open a virtual machine created in Workstation 8 without success.   I went to the preferences box and configure the product for 8 x compatibility, with the same results.

    After double clicking the VM vmx file, the product does absolutely nothing, no errors, no message, nothing.   I want to know if this product really is backward compatible and if this is the case, what should I do to make it work with the virtual machines created in WS 8 x?

    Your help is appreciated.

    Reynaldo Nunez

    Thanks a lot for your answer.   What technical support is suggested:

    Through our discussion, we did the below steps, and this has helped us to solve the problem:

    1. from the VMX file, we have deleted similar entries to:

    Policy.VM.mvmtid = ' 52 6f 36 0f 31 9f f3 f9 d6 da 9f f5 90 7B this 76.

    policy.vm.managedVMTemplate = 'TRUE '.

    policy.vm.managedVM = "FALSE".

    2. we have built and rebuilt the two files 'VMware political' outside of the virtual machine and then we were able to power on the virtual machine.

    Now, everything should continue to be stable and we should not have problems.

    THIS MARKET!

  • webOS a backward compatibility with the PalmOS programs

    Is webOS backward compatible with third-party programs PalmOS?  I have several third-party programs of PalmOS 3rd that I like and do not want to lose.  They also have versions for Windows, but not for webOS.  I've been using Palm for many years and doesn't want to leave him, but I love these 3 third party programs.  Thank you.

    No, webOS is not compatible with PalmOS programs.

    There is a program of emulator for PalmOS on sale that offers limited under the name of Motion Apps 'Classic' compatibility

    It allows many old PalmOS programs to function normally, while those with complicated synchronization routines may not.

    WyreNut

  • Remove the compatibility with older Versions of Adobe Acrobat

    I'm trying to scan hundreds of documents as PDF files using Adobe Acrobat Pro 9.5.5. I'm on Mac, the latest version of El Capitan and find that Preview 8.1, the PDF Viewer integrated for OS X, has difficulties to open a portion of my scanned documents. Interestingly, the only ones who have color in them. Black and white analysis open very well. I think it's an Apple problem, and not what I'm here for.

    Anyway, I went back to PDF it wasn't opening and Acrobat to remove compatibility with earlier versions of Acrobat. I kept compatibility with "Acrobat 4.0 and later versions. After that the file opened without problem in the preview. I noticed that the quality of the new PDF degraded slightly when I removed the compatibility. I guess that's because Acrobat must perform a new rendering of the PDF file.

    Is there a way I can create a PDF file to a JPEG file that is only compatible with versions 4.0 and later? I rather do pretty early in my workflow, and then go back and remove the compatibility and degrade image quality.

    Thank you!

    Hi Link648099,

    First thing, Acrobat 9 is not compatible with Mac El Capitan.

    The PDF created in Acrobat 9 shouldn't be compatible with version 4, please check the levers of the compatibility of the https://acrobatusers.com/tutorials/understanding-pdf-compatibility-levels PDF

    Kind regards

    Nicos

  • compatibility with older games

    Currently under XP but think moving to Windows 7, but LIKE my games "MYST" (Riven, etc.).  These games can run on Windows 7?

    Hi fuguestate

    To verify the compatibility of hardware or software with Windows 7 Windows Compatibility Center is the best place. Link: http://www.microsoft.com/windows/compatibility/windows-7/en-us/default.aspx

     

    If the program is not compatible, then you try to install and run the game in compatibility mode. Steps to follow:

    i. right click on the program

    II. click on properties

    III. click on the Compatibility tab

    IV. Select run this program in compatibility mode and select windows vista

    Link for reference below: make sure to run older programs in this version of Windows: http://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows

    Thank you, and in what concerns:

    Samhrutha G S - Microsoft technical support.

    Visit our Microsoft answers feedback Forum and let us know what you think.

  • Compatibility with older versions of workstation

    can I open in the latest version of workstation the vmx file in the directory of the virtual machines of an older version of workstation for example version 9

    who is first uninstalled?

    With a more recent VMware Workstation, you can open virtual machines created on old VMware Workstation without problem, but you will not be able to open a virtual machine created on a newer VMware Workstation in an old VMware Workstation if you have created the virtual machine using a new version of virtual hardware that is not compatible with the old VMware Worksation.

    See the virtual hardware version compatibility: VMware KB: versions of virtual machine hardware

  • Windows 7 compatibility with older programs

    Only older games of 64-bit Windows 7 run as Links 2003 (Microsoft Golf)?

    Most games should work correctly. If they are not it is possible to activate the compatibility mode (right click-> properties-> compatible) for a specific game to run properly. Microsoft Student Partner

  • Is it possible to make the InDesign files created in CS5.5 backward compatibility with CS4 and CS3?

    I recently installed CS5.5 on my iMac running Mac OS x Lion. I have some documents that have been prepared in CS3 and CS4. They read OK in CS5.5 but I can't then save them to read in earlier versions. Any ideas please?

    You will need to export to IDML to open in CS4. If you need it in CS3 you will need to open the IDML in CS4 and export to INX. You can open the INX file in CS3.

    ATTENTION: New features will be lost or badly deformed and because of changes in the text engine text will be redistributed throughout your document.

    This has been discussed to death in the InDesign forum. Please post followed it.

    This forum is for questions specific suite only.

    Bob

  • SmartView 11.1.1.3 backward compatibility with provider Services 9.3.1

    Hello. Does anyone know if it must establish a connection of data between these two? (11.1.1.3 SmartView requires shared services?). Thank you.

    As far as I know Smart view is specific version

    If any customer of SmartView can 'talk' to the same version of the APS.
    However, you can then have several APS installed versions (for example, on different machines) pointing to the same server Essbase

    Hope this helps

  • Backward compatibility of Javamail version 1.4.4

    Hello
    Is the version 1.4.4 has backward compatibility with version 1.3.1?

    Yes.

    Now define what exactly you mean by "compatible". :-)

    It is not impossible to write a program that works as expected with 1.3.1 and fails with 1.4.4.
    Sometimes this happens when a new feature in 1.4.4 exposes a bug in your mail server.
    for example.

  • Compatibility with software OR related issues

    Q1.
    GUARANTEED OR the fact that several (based on several engines of execution) LabVIEW EXEs wun simultaneuosly ono the same Windows XP computer, without fault?
    If not, what are the constraints?
    ex.
    LabVIEW EXE application created with version 7.1
    LabVIEW EXE application created with version 8.2
    LabVIEW EXE application created with version 6.1
    LabVIEW EXE application created with version 8.6
    all at the same time?
    I know that it works in some applications, but NEITHER GUARANTEE, it will be always be under Windows XP?
    What about Vista?

    Q2. As that NEITHER customer for several years, is it legal to have copies of several versions of the computer on the same labVIEW development environment at the same time?
    I am aware, it works at least on the machine, but is it legal?

    Q3. LabVIEW is really independent of the platform? What are the constraints that must be considered when porting an application LabVIEW between Windows, Linux or MAC?
    Seek not the entire list but the wise application design?
    some bulletpoints keys can be useful on the top links from document.

    Q4.  I have a software EXE that uses the API of VISA sandard calls. If I upgrade my NIMAX, it will replace library VISA was using my EXE?
    In both cases, this will affect the work of my EXE? If it does not, how to avoid this. My EXE can use old calls of VISa for years.

    Sandeepvd wrote:

    Q1.
    GUARANTEED OR the fact that several (based on several engines of execution) LabVIEW EXEs wun simultaneuosly ono the same Windows XP computer, without fault?

    I'm not sure it works flawlessy, but it shouldn't be a problem. Make sure you don't access the same resources (material, tcp ports etc.)

    Q3. LabVIEW is really independent of the platform? What are the constraints that must be considered when porting an application LabVIEW between Windows, Linux or MAC?

    Yes, they should be portable, but the Panel before may need to be redesigned. Also daqmx is limited on linux/mac. No activex or .net. When it comes to dll and you have a compatible library linux/mac, make sure that the extension is not specified in the VI call the DLL and have in the same folder (check out the screw daqmx for an example)

    Q4.  I have a software EXE that uses the API of VISA sandard calls. If I upgrade my NIMAX, it will replace library VISA was using my EXE?
    In both cases, this will affect the work of my EXE? If it does not, how to avoid this. My EXE can use old calls of VISa for years.

    I doubt that VISA is modified AND not to be backward compatible, I've never had a problem with that.

    Tone

  • Backward compatibility of NIDAQmx version?

    I would like to get a better understanding of how backward compatible are NOR-DAQmx drivers.

    Currently, my software has been compiled using version library C/C++-OR-DAQmx 9.0 and supports several cards (for example, PCI/PXI-6225) M Series multifunction.    If my users to install the latest version of the NOR-DAQmx driver (which is the version 9.0.2) then can I safely assume that my software will work without any problem?   The question I ask is what is the driver OR-DAQmx library backward compatible with software written for an earlier version of the library?

    Thank you

    Ian

    Hi Ian,

    Your assumption is correct, the software should work without any problems. You are referencing a dll file and header DAQmx and this location does not change, no matter what your users have installed the version of the driver.

    You could see a problem if they have a version earlier than 9.0 because each new driver version includes additional features and new features. If they have an older version, it may not include support for something that makes your code.

    However, you should be good to go.

    Kind regards

    Frédéric

  • Backward compatibility - migrating the members of 11.1.2.4 to 11.1.2.3 contour?

    Good snow shoveling day everyone!  I hope that you have found the right higher training!

    Our production ASO cube lies in 11.1.2.3
    Our test ASO cube lies in 11.1.2.4
    We want to migrate members in the outline of the ASO cube production ASO test.

    There is backward compatibility of the migration of members of the contour (migration of members of 11.1.2.4 to 11.1.2.3 contour)?
    In other words, we can migrate 11.1.2.4 describe 11.1.2.3 members? Is it a 'backward' migration utility that would allow us to migrate 11.1.2.4 a glimpse back at 11.1.2.3?

    Psalm, we know that when we move 11.1.2.3 State to 11.1.2.4, 11.1.2.4 ASO would we require to migrate 11.1.2.3 briefly 11.1.2.4 front.

    We have the planning and LCM, but tech support said 11.1.2.4 LCM is not compatible with 11.1.2.3 (aka there are a few bugs).

    Otherwise I guess we can use the contour of the OLAP Underground to migrate Extractor.

    Thank you.

    No alcoholic Cheers!

    If it is before 11.1.2.3.500, then there will be such issues as pointed out 'Essbase Administration Services (EAS) outline 11.1.2.3.500 to 11.1.2.3.000 empty file Migration Wizard creates (Doc ID 1927334.1).

    Migration of a glimpse through earlier versions is certainly risky and you're only going to be clear if it is rebuilt.

  • Backwards compatibility of the CC Lr Lr 5 for temporary subscription

    Hello

    I bought Lightroom 5 in November 2014 and I hope temporarily to CC (Lr and Photoshop). This is to make use of the panorama of Lightroom CC and HDR features but also using photoshop to merge images. I only have the demand for these functions to a handful of images, however, and so I'm likely to use the software temporarily for one month subscription.

    My concern is the backwards compatibility of the software, and how my Lightroom 5 software is affected by the CC. Will I be able to use CC with my current library and after use it simply continue with Lr 5 and the new images? CC will be autonomous and does not affect my purchased version?

    Thanks a lot for your help.

    Matthew

    LR CC is not available for a monthly subscription.  You purchase a subscription of $120 / year with a plan to pay $ 10 / month, but for all 12 months, not only for one.

    The only way to get a monthly subscription would be to a Single App to the month PS CC subscription for $30 / month.  PS/ACR will be able to do the same HDR and Panos LR, so my suggestion would be to get a subscription in single-app in PS, then make your HDR and Panos and save those 16-bit TIF, then import these objectives into LR 5.

    Information on what plans are available here: https://creative.adobe.com/plans

Maybe you are looking for