VISA runtime with installshi​eld

How can I include VISA runtime install with my Visual c++ (Install Shield) installer?
Instead of asking user to execute VISA RT installer seperately.
Appl: Win32 platform
Tools: Component Works++ w/VISA for RS-232 Serial Comm.

This is not supported at this time. The only way to install the NI-VISA run-time is through the separate, standalone installer. National Instruments is aware that this is not the best way to redistribute driver software in all circumstances. National Instruments researching ways to allow customers to incorporate drivers more seamlessly into their installers.
Note that NI-VISA is not freely redistributable. You must ensure that each machine on which you install NI-VISA has a valid license for NI-VISA.
David Rohacek
National Instruments

Similar Messages

  • Runtime Error building Installer with NI-VISA Runtime

    Greetings,  I'm getting this error whenever I check the "NI-VISA Runtime" option in the installer app builder.
    Everything builds fine when I check only the Runtime Engine.  Shown below is what causes the RUNTIME ERROR and closes Labview Unexpectedly.
    Any help you could provide would be very much appreciated.
    Regards,
    JD

    Hi JD,
    This is a relatively common error with the Application Builder that can happen for several different reasons, namely registry keys pointing to installations that no longer exist. The easiest way to identify the problem is to get detailed information about the installer build. Here are directions:
    LabVIEW has the
    ability to create a very detailed log of the events that occur when
    building an application or installer. To enable this feature, open up
    the LabVIEW.ini file and copy "CDK.EnableLog=true" to the bottom
    of the file. Save the changes and close the ini file. The LabVIEW.ini
    file is usually located in C:\Program Files\National
    Instruments\LabVIEW X.X
    Enabling this feature will create a log file in the %temp% directory of your computer (%...% means a computer variable) .
    To
    find out where this temp directory is located, go to Start>>Run.
    Type in "cmd". Then type "set". This will return all of your computer's
    variable names.
    Look for TEMP in the list of variable names. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp".
    Navigate to this directory using Windows Explorer.
    You
    should see a file named "Name.log" where "name" is the name of your
    build specification. For example, you might see "My Installer.log" if
    the name of your build specification is "My Installer".
    This will give you a more detailed log of the attempted build and, if I'm correct about why this particular build failed, show you which installer is expected at that registry. If the registry points to a directory without the necessary installer (i.e. VISA), simply delete the registry and allow the App Builder to prompt you to to point to the correct location.
    Michael K.
    | Michael K | Project Manager | LabVIEW R&D | National Instruments |

  • NI-Visa Runtime 5.4.0 Fails with error status 1603.

    I'm trying to install the NI-Visa runtime 5.4.0 in a Windows 7 embeded PC after some investigation I can see in the windows log the error status after the installation it's 1603.
    What it's the meaning of this error? did anyone succeed in install the foftware in a similar platform?
    Thanks and best regards.

    I ran the verbose log for the NI install file, in this case:
    ...\NI-VISA Runtime\setup.exe /acceptlicenses "yes" /log c:\InstallVISA.log    , looking for "Return Value 3", like indicated here, show this:
    DIFXAPP: ENTER: ProcessDriverPackages()
    DIFXAPP: ERROR -The operating system you are running on isnot supported.OnlyWindows2000,Windows XP,WindowsServer2003andWindows codenamed Longhorn are supported.
    CustomActionMsiProcessDrivers returned actual error code 1603(note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s)(D0:E0)[12:31:25:671]:Machine policy value 'DisableRollback'is 0
    MSI (s)(D0:E0)[12:31:25:671]:Note:1:14022: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3:2
    Action ended 12:31:25:MsiProcessDrivers.Return value 3.
    Note that this installer works on another WES7 machine...
     

  • Missing installer component NI-VISA Runtime

    We use the LabWindows/CVI 2010 Version 10.0.0 (360) and have installed the new runtime from the installer package 5.0.3.31.
    With different projects on different computers we have the same problem: The NI-VISA runtime can not be included in the installation package. With older projects which have been already distributed we get the error message when opening the tab "Drivers & Components" and click on the red entry for the visa runtime: "This component is not installed on this system, and cannot be included in distributions built on this machine". Reinstallation of the NI-VISA runtime does not help. The installation is visible in the MDF File and the registry (distributions and products). With a new project the entry NI-VISA runtime does not appear on the "Drivers & Comnponents" tab.
    What went wrong? We are not able to create any distribution at this moment.
    Solved!
    Go to Solution.
    Attachments:
    ScreenInstallerError.jpg ‏334 KB

    The items shown in the Drivers & Components tab are enumerated from the contents of the <program files>\National Instruments\Shared\MDF\Manifests directory. If you have NI-VISA 5.0.3 installed, you should have a file in that directory named 'NI-VISA Runtime 5.0.3 {85BA3FCF-AA00-4151-B97D-84A221E8198A}.xml'. From your experience, I would guess that maybe this file is somehow missing. That would be especially strange, given that you have uninstalled and reinstalled, but it seems to be the most logical explanation. I am attaching a zipped copy of that file here as a replacement, in case you are missing it. If you already have the file, or replacing it does not solve your problem, it will be handy to look at the debug build log. You should attempt to build the distribution, then after it prompts you and you abort, look for the file <user temp dir>\distBuildDbg.log and post it in your reply.
    Mert A.
    National Instruments
    Attachments:
    NI-VISA Runtime 5.0.3 {85BA3FCF-AA00-4151-B97D-84A221E8198A}.zip ‏5 KB

  • NI VISA Runtime engine

    When "Building" a LabVIEW program containing NI-VISA sub VI's (e.g. to communicate with USB), I have had problems getting the "Built code" to find my NI VISA devices, even though the NI VISA USB  Drivers are correctly installed on the "target machine".
    (The "built" code WILL run if the target machine has a LabVIEW installation on it, including NI VISA)
    So - will the NI VISA runtime engine be automatically included in the "Build" (Because of the NI VISA sub VI's), or do I have to specify this myself - And how?
    Thanks. Peter.
    Solved!
    Go to Solution.

    You specify installing the NI VISA Runtime Engine when you build and installer for your built executable. Look on the Additional Installers tab of the Installer Properties Dialog Box.  The NI VISA Runtime Engine should be selected automatically but if it's not you can uncheck the Automatically select recomended installers checkbox and select any other installers you want to include in your install.
    If you're not using an installer then no runtime engines are installed and you'll have to do that manually on each machine you copy the executable to.
    This all assumes LabVIEW 2013.  The selection process is slightly different in earlier versions but all the options are still available.
    Kelly Bersch
    Certified LabVIEW Developer
    Kudos are always welcome

  • Do I need "NI-VISA Runtime 5.1" visa in the install package?

    I have applications that use the serial port communications. The install package has grown from 109mb with v8.0 to 150mb with v2011. Do I have to install the NI-VISA runtime 5.1 if I am only using the serial communications?
    Solved!
    Go to Solution.

    Yes.

  • Looking for a VISA Runtime Merge Module

    I am building an installer with install shield. I have been able to find a LabVIEW Runtime Merge Module and that seems to work great. But, I need one for the VISA RunTime.

    You can download the VISA RunTime Engine from NI's website ( click here ) and have your installer also install the RunTime engine. This link will take you to an NI Knowledge Base which describes how to do this.
    J.R. Allen

  • Why U. S. Store refuses my Visa card with it's official and with the global science I can buy from Bahrain store    and now my account stoped with reason owe ..

    Why U. S. Store refuses my Visa card with it's official and with the global science I can buy from Bahrain store    and now my account stoped with reason owe ..

    You can ONLY use the itunes store of your country of residence ( proven by the billing address on your credit card) AND ONLY while you are physically located inside the borders of that country.
    You would have to live in the U.S and physically be located in the U.S in order ot use the U.S tunes store.  The same is true for each countrys itunes store.

  • Labview 8 Application Builder and VISA Runtime Engine

    Hi,
    I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
    What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
    Is this possible?
    Ken

    Hi,
      this How-To explains about making those selections and including the different drivers :
    http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
    and this tutorial covers the screenshots a little more step by step.
    http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
    Hope that helps
    Sacha Emery
    National Instruments (UK)
    // it takes almost no time to rate an answer

  • Sharing VISA Resources With Multiple Application Instances

    I have noticed a strange behavior when attempting to communicate with a
    slow, single shared VISA resource (GPIB device) from multiple
    stand-alone LabView 5 applications.
    Initially, I developed some code which first attempts to acquire
    exclusive access to the device using VISA lock with a reasonably large
    timeout. After the lock is acquired, the code performs its IO, then
    releases the lock.
    I then wrote some wrapper code which basically tries to enter the (lock,
    IO, unlock) code as fast as possible. I built a stand-alone application,
    and ran 3 seperate instances. Basically, I could see that each
    instance would eventually acquire a lock, perform its IO, and unlock.
    However, some of the instances "starved" for access to the device,
    enough so that the timeout was sometime reached (each IO would take
    perhaps 2 seconds, and I set the lock timeout to say 10 seconds).
    Ideally, each instance should receive the lock in the order by which the
    lock was requested. It appears that VISA is doing something else.
    I've verified that this issue also exists with "faster" GPIB devices
    (say 200ms IO turnaround), but is less noticable because the
    communications are faster.
    To get around this, I wrote another application which basically acts as
    a resource server. Using VI server, each instance which wants access to
    the resource sends a "lock" request to the server. Specifically, the
    "client" calls a re-entrant "Interface" VI via VI Server. The
    "interface" VI then adds the "lock" request to the queue, and then waits
    for "Notification" from the server process. The server parses the
    request queue, and when the resource is available, it sends a
    notification to the appropriate "interface" VI. This whole time, the
    client is waiting for the interface VI to return, just like when it's
    waiting for a normal lock. When the client is done with the device, it
    sends an "unlock" message to the interface VI. The server then gives
    the resource to the next item in the queue.
    To me, this is a bit kludgey. My solution requires that this "server"
    application is running at all times, and it is a bit slower than the
    usual manner. Has anyone come up with a better solution?
    Thanks,
    Andy

    My answer depends how stand alone your applications are. I don't know what happens if you have several independant executable files but the simplest solution in the development environment is to have one vi that handles all send/receive requests to the instrument. In this way, without extra overhead, you guarantee single parts of each program access too your instrument. (don't make this vi reentrant naturally)
    This approach has another advantage. You separate in a better way the instrument and your aplication, so changing to another instrument is easier to do.
    greetings from the Netherlands

  • Packaging AIR runtime with app?

    Would it be possible to have an option to package the AIR runtime with the APKs
    created through Flash Builder?  Say, a ride-along package that would detect if the
    given or higher runtime of AIR is installed, and if not, install it before launching the
    app.
    For the foreseeable future (the next year, at least), most new users of any given app
    created this way will not already have the AIR runtime on their phone.  This would
    spare them having to initiate another download when they thought they were about
    to enjoy the product.  (No matter how you disclaim it, many customers are going to
    think you can start an app right away after downloading it from the Market, because
    this is how practically all non-AIR apps work.)  Waiting for an install is okay if the app
    automatically launches afterward: this will not take nearly as long, and (importantly!)
    requires no further customer action to actually launch the app.

    I'm sure it would possible, but consider that as soon as someone downloads
    an AIR Android app, they've already got the runtime, and with notifications
    for updates already a common thing, they'll be notified from the Market
    whenever there's an app update (runtime or your app).
    I think it would be nice as an option, but just today I got an email from
    the Android Market explaining important changes to the store, and
    specifically they say no .apk larger than 50 mb. So I'd rather not have the
    runtime packaged with the app, as that adds to the overall filesize. We
    already have to deal with that on iOS devices, since Apple won't let us
    download compiled code. So you get an automatic 3-4 mg overhead with all iOS
    apps. Luckily there's no real limit on iOS app sizes.
    I do agree though it'd be nice to have the install process worked out so the
    app prompts for the runtime if needed (as it works now) but have the runtime
    know to launch the app again once it's installed.
    iBrent

  • Crystal XI Runtime with Windows 2008 Server

    Hi all
    We have been using Crystal for many years with our application, distributing Crystal Runtime with it.
    We have our own DLL which interacts with Crystal to display a setup screen to get the user to enter values for the parameters within the report and then runs the report.
    All works fine except for running on Windows Server 2008. We have Crystal Reports 11.5 and the runtime on the server is also built with the 11.5 merge modules.
    Where the application fails is during a call to the TApplication.OpenReport. Windows isn't giving much information apart from an error has occurred.
    Can anyone tell me if there is a known issue running under Windows Server 2008 and whether there is a fix.
    I have posted in a different forum, but trying here as well. Getting desperate.
    Many thanks.
    James

    Please re-post if this is still an issue to the Legacy Application Development SDKs Forum or purchase a case and have a dedicated support engineer work with you directly

  • Macbook air 2011 so slow speed to visit Internet with WIFI

    I bought Mac book air 2011 13' inch core i5 last week. Recently, I found it is sooooo slow to visit
    internet with WIFI, even I cannot open the any website with Safari..........
    Is there anyone the same to me?????

    Hi,
    i solved the problem this way,
    first reset PRAM (google for "reset PRAM lion" if you don't know how = restart and immediately push these buttons simultanously  [option] [cmd] [P] [R] )
    then
    in network prefs, uncheck "ask for confirmation when connecting to other networks"
    (or something of that kind, i don't use the english version)
    this solved my problem
    hope it will help you as well
    give peace a chance

  • NI-VISA Runtime 4.3 Additional Installer problem

    Hello,
    I am using Project Explorer and I'm trying to include NI-VISA Runtime 4.3, but during the build I get a message that says:
    Locate the "Activate" distribution. LabVIEW needs to copy a component installed or updated by the distribution to continue building the installer.
    I don't know what the "Activate" distribution is or where to find it! Please help.
    See attachments. 
    Message Edited by Sidd on 10-09-2008 02:02 PM
    Solved!
    Go to Solution.
    Attachments:
    additional_installers.JPG ‏87 KB
    activate.jpg ‏25 KB

    Thanks for the suggestion but I solved the problem a different way.  I downloaded NI-VISA Run-time 4.3 from http://joule.ni.com/nidu/cds/view/p/id/989/lang/en then extracted it to a folder.  I pointed Project Explorer to this folder and it found it properly.
    I was then able to build the project successfully. 
    Sidd 

  • Firefox freezes when i visit websites with videos on the background or i watch videos.I have windows 7 and the laatest version of mozilla.

    I have windows 7 and the latest version of firefox.When i watch videos on youtube or visit websites with videos on the background mozilla freezes. I tried to disable all the extensions and plugins but it had no result.I didn't had this problem with versions of mozilla previous to 4.

    I have had a similar problem with my system. I just recently (within a week of this post) built a brand new desktop. I installed Windows 7 64-bit Home and had a clean install, no problems. Using IE downloaded an anti-virus program, and then, because it was the latest version, downloaded and installed Firefox 4.0. As I began to search the internet for other programs to install after about maybe 10-15 minutes my computer crashes. Blank screen (yet monitor was still receiving a signal from computer) and completely frozen (couldn't even change the caps and num lock on keyboard). I thought I perhaps forgot to reboot after an update so I did a manual reboot and it started up fine.
    When ever I got on the internet (still using firefox) it would crash after anywhere between 5-15 minutes. Since I've had good experience with FF in the past I thought it must be either the drivers or a hardware problem. So in-between crashes I updated all the drivers. Still had the same problem. Took the computer to a friend who knows more about computers than I do, made sure all the drivers were updated, same problem. We thought that it might be a hardware problem (bad video card, chipset, overheating issues, etc.), but after my friend played around with my computer for a day he found that when he didn't start FF at all it worked fine, even after watching a movie, or going through a playlist on Youtube.
    At the time of this posting I'm going to try to uninstall FF 4.0 and download and install FF 3.6.16 which is currently on my laptop and works like a dream. Hopefully that will do the trick, because I love using FF and would hate to have to switch to another browser. Hopefully Mozilla will work out the kinks with FF 4 so I can continue to use it.
    I apologize for the lengthy post. Any feedback would be appreciated, but is not necessary. I will try and post back after I try FF 3.16.6.

Maybe you are looking for