LabVIEW 32 bit on Win7 OS vs. XP 32 bit

I need to know if it is at all possible to create an installer in LabVIEW 2010 32 bit Win7 that would work on a XP 32 bit target machine.
How do you guys work around this issue if it exists?
I thought I could do it by keeping an XP platfrorm available for development but now that has left me unfortunately due to (I believe)
some upgrades applied via the auto updater.
ALso what have I done to screw this up on XP. I cannot even get XP to create an installer that would work on XP anymore.
The error I get when I try to install the installer I just created on XP LV 2010 SP1 is
"You must install LabVIEW 2010 32 bit or later on the system before you can run this setup."
I have placed an installer on this machine before since the target executable still works on it but now I am locked out from making any improvements
to the executable. If I make an executable it compiles just fine but some of the math functions are lost
"An error occured loading NI_AALPro.lvlib:LinearFit.vi"
Boy I hope the solution is not to re-install LabVIEW on the XP machine. I just had to physically disable the ethernet port on this machine so that it can
never connect to the internet again and a win7 replaceent is months away.
I am open to any and all suggestions. If more info is needed please ask and I will try to provide it.
Thanks Guys.

Thank you Dennis,
The Dll file was not including that Vi for some reason, so that was a good help.
On the first issue I did try to remake an installer from an XP machine to an XP machine and did insure that switch "require labVIEW 2010 32 bit " was not checked. It went ahead and made the installer just fine, but now it appears that the new installer still has this issue of giving the same error as described above.
Fortunately, I found a way to work around this and am not totally stuck (Thank goodness.) 
The only thing I can think of is the source XP machine was hooked up to the NI updater software and some updates were probably applied to this version of LabVIEW (2010) or something is amiss on the target machine(doubtful). However, the 'about LabVIEW' dialog on the source XP machine simply states the version as LabVIEW 2010 SP1   version 10.0.1 (32 bit) .
I have no courage to attempt an un-install of the support on the target machine because it is in production use.  
I think this issue should be looked at by NI if possible. The switch for "requiring LabVIEW 2010 32 bit" seems to be doing something that cannot be reversed once set. I wish I could be more helpful.

Similar Messages

  • Reading fits files in labview 64 bit

    I need to read fits data files in labview on a 64 bit machine. I developed an application in labview 2012 (32 bit version on a win 7 x32 machine). This vi will not run on a win7 x64 machine. The problem is with the gfitsio library I used to read the files (downloaded from http://heasarc.gsfc.nasa.gov/docs/software/fitsio/​fitsio.html). It seems they will not work with labview x64. I installed labview 32 bit on the same machine & tried to run the vi with that, but no luck.
    Any ideas would be appreciated,
    Thanks,
    Joe 

    It appears the FITS libraries are 32-bit, so they cannot be called from 64-bit LabVIEW.  You should be able to call them from 32-bit LabVIEW on a 64-bit machine.  The only difficulty you may run into is locating the DLL.  64-bit versions of Windows put DLLs in different places than 32-bit. Check you system path and make sure your DLL resides in the search path.  You can also load the DLL explicitly using Windows Kernel32.dll calls before loading code which calls it.  This is awkward, but works in some cases.
    Since the source code is available, you may be able to create a 64-bit DLL that 64-bit LabVIEW could use.  I am the wrong person to cousel you on how to do this, but it should be possible.
    If you need more info, please ask.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • Motion control in LabView 64-bit

       I am trying to operate NI Motion with a PCI-7344 card inside LabView 64-bit on a WIN7/64 platform.  At this point, NI Motion will only operate in LabView 32-bit independant of 32-bit or 64-bit OS.  The reason for the 64-bit operation is a 3rd party function generator card that requires 64-bit LabView to work in conjunction with the 64-bit drivers for a WIN7/64 OS. 
       Currently, a system has been configured for WIN7/32 but would like to be able to access the full memory (>4GB) for other data processing. 
       Any suggestions?

    I have about the same problem, I'd like to use the full memory because I use NI-Vision and NI-Motion but I can't.  I really like that NI or anybody could help us on that.
    Jean-Francois  

  • LabVIEW 64-bit - Can I build a 32-bit exe

    LabVIEW 64-bit - Can I build a 32-bit exe

    Hi Gary
    Not at the moment - see here
    You'll need to open your VI up in the 32 bit version and compile from there.
    Kind Regards
    Chris | Applications Engineer NIUK

  • Using both, LabVIEW 32-bit and 64-bit

    Hi Guys,
    I have a requirement where I have to interface with a camera using LabVIEW 64-bit (because the dll provided is for 64-bit system). At the same time, I have to communicate with several variables via OPC Server using LabVIEW DSC, which is only available in 32-bit. I was told that I cannot run one same program but utilizing LabVIEW 32 and 64 bit simultaneously. Hence, I would like some advice, especially on the architecture, on how should I approach this.
    Advices are much appreciated.
    Shazlan

    Are you sure that you can't have a 32-bit compatible dll for your camera? It would really make your life easier.
    Also if you only use the DSC module for the OPC function, maybe you could look for a different set of OPC functions that support 64-bit.
    In the end if you really have not choice but to use DSC module and use the 64-bit dll for the camera, you will need to apps, one in LV32 and one in LV64 and you will have to decide which one is the main one and find a way to communicate between them, TCP comes to mind, also VIServer, I have never tried VIServer between a LV32 app and a LV64 app but my bet is that it should work seamlessly.
    Good luck!
    When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

  • Real-Time Module Labview 64 bit

    I have installed labview 2009 64 bit version to my laptop. And, i want to instal the real-time modul to this labview, but i can not do this since it needs labview 32 bit installed. Is it possible for me to install real-time module to 64 bit labview? Please help me with this problem.

    The LabVIEW RT application will most likely always have to remain 32 bit for now. Most of the RT targets are to resource constrained to gain anything from moving them to a 64bit RT OS, in fact in trying to move them to 64 bit they would loose quite a bit of performance. For the Desktop and PXI RT systems, the problem is that they are based on Pharlap ETS and that is a pure 32 bit solution with no plans of ever moving to 64 bit anytime soon, AFAIK. And NI is not likely going to port that to 64 bit themselves, aside from the question if they could technically do so (not sure they have access to all of the source code) and legally (their license most likely does prevent them from changing the ETS software to run under different target systems than the one it was originally purchased for).
    The only thing you can expect to come from NI in the near future is that the RT system also installs into 64 bit LabVIEW, and the actual cross compilation that happens already will simply target the 32 bit RT target. That however means that the RT application itself is still limited by the 32 bit constraints. Maybe there are some plans to add a 64 bit RT system to the mix for the high end PXI controller. What OS that would use is quite unclear. Pharlap ETS seems out of question for that, VxWorks is probably not a favorite solution at the moment and an Linux RT based system has its own legal and technical challenges.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Labview 64-bit running with 32-bit addons

    I ran into memory problem loading som data files, and I tried a workaround by installing Labview 64-bit, but found that the add-ons was not installed with it. 
    Now I needed to use sound and vibrations toolkit, so (being maybe a little too creative) I copied that toolkit over to the 64-bit Labview folder and everything seems to run.
    I can load the files and do my data analysis with no errors.
    Now the problem is that I don't really get how a 32-bit add-on can access the memory from the 64-bit core Labview. Does anyone have any ideas on why its running and why I don't get a memory access error.
    The results looks ok, but I don’t really trust them, due to the above mentioned problem in accessing memory  between 32-bit and 64-bit.
    regards
    Henrik
    Solved!
    Go to Solution.

    Hi Henrik.
    When using LabVIEW 32-bit on a 64-bit machine, all your VIs would run through the Windows-on-Windows emulation layer (WOW64) and this is also why we still have memory limitations on a 64-bit OS.
    When you are using LabVIEW 64-bit, and using a 32-bit toolkit, what's actually happening is the 64-bit LabVIEW kernel is recompiling the 32-bit VI into a 64-bit VI. Doing this changes the inherent memory characteristics and performance of the Sound and Vibration VI's (and all 32-bit VIs, for that matter). The newly converted 64-bit VI's, then, are being executed in the native 64-bit LabVIEW kernel.
    However, I would strongly advise you to install the toolkit the normal way. In the following document, you can see, that the Sound and Vibration Toolkit / Measurement Suite is in fact supported by a 64-bit version of LabVIEW.
    National Instruments Product Compatibility for Microsoft Windows 7
    After you install LabVIEW, you need to reinstall all your add-ons and drivers in order for that toolkit / driver to work with LabVIEW. When we install toolkits / driver, we only install support for the LabVIEW versions installed at that time.
    I hope this helps.
    Best Regards
    Alex E. Petersen
    Certified LabVIEW Developer (CLD)
    Application Engineer
    Image House PantoInspect

  • How do I install Labview 64 bit support for the labview fpga module?

    see subject.

    Hi,
    The LabVIEW FPGA Module uses the 32-bit version of the Xilinx tools, even on the 64-bit OS.
    There is no 64 bit version of LabVIEW FPGA and you must have LabVIEW 32 bit
    installed on your 64-bit machine to use the compatible version of
    LabVIEW FPGA.
    NI LabVIEW FPGA Module will run within the 32-bit emulation layer, Windows on Windows (WOW64).
    regards,
    Houssam Kassri
    NI Germany

  • Labview 64 or labview 32 bit?

    Hi, I have a new 6 bit pc and an old 32 bit pc and I have to use both of them. If I install on the 64 bit machine labview 64 bit, when I save a vi, can it be opened on the 32 bit machine?
    With this kind of problem, do you suggest me to install labview64 or labview32 in the 64 bit pc?
    Thanks
    Solved!
    Go to Solution.

    For source code control I would use SVN. I have also heard some very good things about git. Both are open source and are independent of LabVIEW. A simple Google search will find the installs for both as well as information specific to using them with LabVIEW.
    There is a setting in the options under the Environment section to configure LabVIEW to separate compiled code from new files. I have attached 2 VIs (very crude since these are just basic utilities and we did not make them pretty) which you can use to list the status of existing files or set the option.
    As for which version of LabVIEW to use I am saying use both. As noted earlier you will need to have copies of whatever drivers you are using for both versions. For the code you develop you should be able to use it in either the 32 or 64 bit version and the seapration of the compiled code should mean that it will easily transfer between systems. Your source code control won't see the files as being changed, unless you actually do make a change, since the compiled code is actually cached on each PC. The source will be the same in either the 32 bit or 64 bit version.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot
    Attachments:
    Enable-Disable Seperate Compile Code.vi ‏25 KB
    List Seperate Compile Code Setting.vi ‏24 KB

  • Does LabVIEW 64 bit included in Developer suite ?

    Does LabVIEW 64 bit included in Developer suite ?
    George Zou
    http://webspace.webring.com/people/og/gtoolbox
    Solved!
    Go to Solution.

    The installer is not included in the Developer Suite Disks.  But it uses the exact same license as the 32-bit.  You can download the installers from NI's site.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Solidwork x64 and labview 32 bits compatibility?

    Hello community.
    I'm with a project where I want to make the connection with Labview 32 bit and 64 bit Solidwork to control motors with LabVIEW, I have been following many tutorials and I get to create everything you need but when you run the VI does not move nothing SolidWork thousand times and reviewed the steps and is desesperate. Ruling out any option and I wonder if these two shows are 32 and 64 bits can be the cause of not getting the communication with these two programs. I hope your help. regards
    Es un placer echar una mano siempre( Base de una sana convivencia). Si mi respuesta te sirve por favor agradecemelo con un Kudo
    Un especial saludo a mis hermanos latinos. Un mundo mejor es posible.

    Does this help?
    http://digital.ni.com/public.nsf/allkb/71E9408E6DE​AD76C8625760B006B6F98
    Q. Can I run an executable built with LabVIEW 64-bit on a 32-bit PC?
    A. You cannot run the LabVIEW 64-bit Development System, Run-Time Engine, or executables on a 32-bit PC.
    Q. Can I run an executable built with LabVIEW 32-bit on a 64-bit PC?
    A. Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development System, Run-Time Engine, and executables can be run on Windows 64-bit.
    Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
    A. Yes.
    Q. Can I build a 32-bit version of an executable from the LabVIEW 64-bit application builder?
    A. There currently is not an option to create a 32-bit version of an executable from the LabVIEW 64-bit application builder.

  • LabVIEW 64-bit support for modules and toolkits

    I've just finished installing the 64-bit version
    of LabVIEW 2009 under 64-bit Windows 7 Professional.  However as noted
    above very few toolkits and modules are available for this
    version. Some of those MIA include MathScript, VI Analyzer, Advance
    Signal Processing Toolkit, etc. I realize development and testing takes
    time but think it's reasonable to ask that NI put up a table or chart
    of toolkits and modules clearly showing which ones are
    available/compatible with 64-bit LabVIEW, as well as timelines for when
    these will be available.
    (Apologies for cross-posting from the Ideas Exchange but that board doesn't seem to get much traffic...)

    Hi Magma,
    The Vision Development Module is currently the only module available for 64-bit LabVIEW.  We currently have not released a timeline for other modules, but we are working on other 64-bit support.  The links below summarize the current functionality of LabVIEW 64 bit.
    LabVIEW 64-Bit vs. 32-Bit Applications FAQ
    http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
    Announcing 64-bit LabVIEW
    http://zone.ni.com/devzone/cda/tut/p/id/10184
    Nick Keel 
    Applications Engineering 
    National Instruments
    Nick Keel
    Product Manager - NI VeriStand and Model Interface Toolkit
    National Instruments

  • LabVIEW 64-bit crashes upon startup but LabVIEW 32-bit works fine.

    Recently had to uninstall and reinstall both LabVIEW 32 and 64-bit versions because the network administrator is dumb.  Now 32-bit works fine but the 64-bit version immediately crashes upon opening.  Getting the following Labview Crash: Exception: Unknown (0xC06D007E) at EIP=0x000007FEFCE1940D.  We're running LabVIEW 2012 on Windows 7 64 bit system.

    Did you try to repair the 64-bit version? Was it working previously fine?
    The best solution is the one you find it by yourself

  • Fieldpoint and Labview 64 bit - why is the LabVIEW Support missing from MAX and the Measurement I/O Pallette?

    I am running Labview 2010 on a Windows 7 virtual Machine, I have installed Fieldpoint 6.0.7 with all the appropriate support. The VIs are in vi.lib. BUT, MAX doesn't show the LabVIEW support as existing, and the Measurement I/O pallette doesn't have the Fieldpoint VIs linked into it.
    Anyone out there with any idea what I might need to do to get these seen? I've uninstalled, re-installed, installed only sections, and so far - no sign of these VIs appearing.
    So, any ideas?

    Not quite. I can see Fieldpoint, but not the LabVIEW support section.
    The first screenshot is from my 32-bit system, the second is the one from the 64-bit system.
    Attachments:
    Fieldpoint Screenshot 1.JPG ‏20 KB
    Fieldpoint Screenshot 2.JPG ‏15 KB

  • Install LabVIEW 32-bit and 64-bit on same computer - doesn't seem to work

    I have the LabVIEW 2011 Development System.  The FAQ at http://digital.ni.com/public.nsf/websearch/71E9408E6DEAD76C8625760B006B6F98?opendocument&Submitted&&...  says that the 32-bit version and 64-bit version can be installed on the same machine.  I would like to do this because some of the targets for executables are 64-bit and others are 32-bit.  I have tried this on two different computers and wind up with two non-working versions of LabVIEW.  The license refuses to activate until I do a complete uninstall of both versions and pick one to reinstall.
    Is there some trick to this or is the FAQ just wrong?

    abikutn wrote:
    Install 32 first and then 64 . But either way both should be installed in the same directory and not in two diff places. 64 uses some shared files from 32.
    Wrong! (Please provide an authorative link to support your outrageous statement)
    LabVIEW Champion . Do more with less code and in less time .

Maybe you are looking for

  • Can no longer connect my B&W A7

    Hello : Recently bought Airpot Extreme and my A7 will no longer connect via AirPlay.  Do not know what to do B&W tech support wrote me this:                       If you are able to set up your A7 but, it will not work wirelessly network can you plea

  • WebGL doesn't work after update

    When I updated from kernel 3.6.9 to 3.8.1 (after pacman -Syu), WebGL didn't work anymore. Now I updated to 3.9.6, but the problem persists. WebGL correctly worked both in Chromium and Firefox, but now their createContext returns null with "webgl" and

  • Acrobat Reader 9.0 PDF - Commenting property "Not Allowed"

    Hi, I saved a document in Illustrator as PDF but unfortunately the Commenting property is set to "Not Allowed" and I cannot mark-up the file in Acrobat Reader. What is strange is all properties are set to "Allowed" when I open the same document in Ac

  • CR Server: Login loop when I run a report

    Post Author: Marcotte CA Forum: General I have CR Server XI installed on my server.  I can log into the Central Management Console and Infoview from the client.  I can load objects and run the sample reports.  I can set up users and security.  I can

  • False Positives?

    A personal friend owns a local heating and air company.  He had an IT friend re-do his website recently.  My wife noticed it and had me take a look.  It's simple and clean and in Firefox text doesn't overlap when one zooms text only.  I took a look a