LabView 8.2 et Windows 7

Bonjour,
Je dipose de la version LabView 8.2.1. On développement nos logiciels dépuis belle lurette. Maintenant, on n'a pas mal de retour client concernant l'installation de nos logiciels sur les systèmes comme Windows 7 et les versions 64bits.
Ma question est: est-ce qu'il existe des solutions pour resoudre ce problème (rendre possible l'installation et l'utilisation de mon programme sur tous les OS windows à partir de Win2000).
Pour ce qui concerne la version système 32 ou 64 bits: S'il le faudra, je créerais deux versions logiciels pour repondre à cette demande.
Merci pour vos aides

Bonjour,
Pouvez-vous nous donner plus d'informations sur les erreurs que vous avez?
Voici une KB expliquant un problème connu et comment le résoudre:
Windows 7 or VISTA Error: TARGETDIR is undefined, the Directory table seems malformated
De plus, je vous conseil de mettre à jour votre version de LabVIEW pour une version supportant Windows7.
En effet LabVIEW 8.2 date de 2006 et a était développé pour Windows XP. Microsoft ayant fait de nombreux changements sur son nouvel OS, il est normal qu'il y ai des problèmes d'incompatibilités.
Voici un lien expliquant le cycle de vie LabVIEW:
http://www.ni.com/labview/f/product_lifecycle.htm
Cordialement,
Yann

Similar Messages

  • Charting data from text file in LabVIEW 5.1 for Windows

    I am having some difficulties trying to figure out how to plot a chart with
    data from a file. I would like to be able to read data from a text file
    into a chart using LabVIEW 5.1 for Windows. I have looked in the help
    within the program and online. I have also looked in the user manual and
    the book "LabVIEW for Everyone". Could you please give me specific
    instructions on how I would construct the program to be able to do this.
    Thank you.

    Hi Ellie,
    It depends on how data is stored in that txt file. Usually you load the data into an array either using or , the array if necessary and send it to the graph indicator in required form. If you want a more detailed answer, send me a sample data file ([email protected]).

  • LabVIEW application run on Windows XP Embedded

    I'm doing a Embedded system based on Windows XP Embedded operating system.I want to make a LabVIEW applications which can run on it.I see a lot of paper that show the LabVIEW does not support Windows XP Embedded.I want to know whether the official has already solved this problem?Or someone has done the same thing successful?

    Who is the official? NI?  If it isn't supported, NI is unlikely to be trying to solve the issue as we are a bit beyond XP.  You'd need to find unsupported methods to hack it a bit.  I'm not sure you'll enjoy this process

  • Is it possible to build a project with Labview 2010 on a Windows XP system, that is useful for a system with windows 7 on it?

    Hi there,
    I am planning to use Labview 2010 in a short time.
    But before I'm going to use it I have some questions.
    I know it is possible to run Labview 2010 in an XP environment. But is it also possible to, when running Labview 2010 on a XP system, to build a project to a version that is useful in a Windows 7 environment?
    Or do I have to run Labview 2010, when I want to build a project that is useful on a Windows 7 system, on a system with Windows 7?
    Please give me some information.
    I hope to hear from one of you soon.
    Regards,
    Kenny
    Solved!
    Go to Solution.

    Is it possible to build a project with Labview 2009 on a Windows XP system, that is useful for a system with windows 7 on it?
    Thanks.
    Philippe B.
    Certified Associate Developer / Dépt Moyens d'essais
    www.ingenia-system.com

  • Bug report: on LabVIEW 2011 SP1 and Windows 8 'Open URL in default browser.vi'

    Dear colleagues,
    Here is a bug report.
    Culprit: 'Open URL in default browser.vi'.
    System: Windows 8, Professional. LabVIEW 2011 SP1.
    Abnormal behaviour and steps to reproduce:
    Above mentioned VI doesn't work when LabVIEW was started with administrator privilegies. And it works as expected when LabVIEW running in normal (non-administrator) mode. 
    Looking forward to see this fixed.
    Best regards,
    Igor Titov.
    CLD.
    =========================
    Igor Titov, CLA
    WebPager - put LabVIEW front panels into the web page
    Labicom.net

    Hi Igor,
    Unfortunately LabVIEW 2011 SP1 does not support Windows 8. I tested this behavior with LabVIEW 2012 SP1 on Windows 8 and everything worked correctly. 
    Regards,
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments 

  • Best way to run a LabVIEW VI written for Windows in a MAC OSx environment

    I have written a VI in LabVIEW 8.6 under Windows XP and compiled it into a .exe.  Now I want to run this executable on a MAC OSx machine.  What is the best way to do this without having to purchase a LabVIEW for MAC license or Windows VM software for the MAC?
    Thank you,
    cjl
    Solved!
    Go to Solution.

    cjl,
    Yes, that should run.   Except.... Does your program use any hardware?  Does it use any Windows-specific functions (from the Platform folder)? Does it rely on a particular video driver or soundcard? Does it rely on right click mouse actions?  All of these kinds of things may or may not work because they are closely linked between the Windows OS and the underlying computer hardware.  While the software itself will problaby execute, the programmay not work as expected if some of these dependencies are handled differently by the Apple hardware.
    I have not used VM but running native under Bootcamp works pretty well, again allowing for the issues mentioned above.
    Lynn

  • Problems with installation of system and support files with Labview 5.1 on Windows NT.

    I make installations disks with Labview 5.1 on Windows NT and I need to add some system files and other support files. When I'm in App Builder I choose them in "Add support files" and I mark their "custom directory destination" (c:\winnt\system32, c:\est\base) but, when I test the installation I see that files don't save in this directory, they save in 'C:\c\winnt\system32' and 'C:\c\est\base'. How can I solve this problem?

    Jorge,
    I know there were some problems with the LabVIEW 5.1 Application Builder that were fixed in the LabVIEW 5.1.1 Updater. I recommend you download that update to see if this fixes the problem. Also, double-check to make sure you have typed the file paths correctly. If you continue to have problems after installing the 5.1.1 updater, please let me know, and please attach your .bld file so I can examine it for any problems.
    Thanks for your patience on this issue, and have a pleasant day.
    Sincerely,
    Darren Nattinger
    Applications Engineer
    National Instruments
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • How do i run a Labview file through a windows phone?

    Hello there
    How do i run a Labview file through a windows phone or a tablet? is it possible
    is there any phone specifications required? or steps?
    Thanks alot  

    Blokk wrote:
    na1992 wrote:
    hahaha my baad
    i mean if i have done my labview file on laptop and i want it to connect my file to a microcontroler using usb or any serial connection, i want a way that my labview file will run if i store it on a phone. 
     i searhced about exe  format but i didnt find enough info
    Sorry, but you should define more precisely what is your goal:
    " i searhced about exe  format but i didnt find enough info"
    If you build an exe using Labview, that exe will not run on iOS, or Android, if this is what you ask...
    Nor Windows Phone or Windows RT. A LabVIEW exe is compiled and linked for x86 or AMD64 architecture with Win32 API architecture and will only run on Windows for x86 or x64 systems.
    Windows Phone and Windows RT are despite the similarity in the name technically completely different platforms to the normal Desktop Windows system, just as different as MacOS X or iOS.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Running an EXE from LABVIEW without the 'cmd' window showing

    Hi,
    I am currently using the 'system exec.vi' in a LabVIEW application to open files in external executables (mainly Windows Explorer, Acrobat Reader and Word).  This actually works fine and while my application is fairly sleek (even if I do say so myself) I am annoyed by the cmd window that momentarily appears each time I use the 'system exec.vi'.
    Is there any way to disable this window?  Or maybe there is another way of opening the files altogether?
    I am using LabVIEW 8.0 on Windows XP Pro.
    Any help would be appreciated.
    Bazza

    Bazza wrote:
    Thankyou for your comments...
    I do buy LV as part of a developer suite so could use the toolkit you mentioned.  While PDF's and Word docs are the main files I open they are not the only.  I guess I could open different file types different ways.  I just hoped there was a better all round way to do it.
    As far as Windows Explorer goes...  My application is a file manager targetted directly at the file structures we use for developing functional test applications.  The application handles all the file management requirements (i.e. WIP Backups, deploying, zipping/archiving etc) and its an added feature that you can 'explore' a given folder directly from the application.  The general idea is that all our developers create systems using the same structure and approach.
    Cheers,
    Bazza
    Have you looked at the VI in vi.lib\Platform\browser.llb\Open a Document on Disk.vi. It opens the document passed in according to its file ending and attempts to communicate with the target application through DDE if possible before using the command line. Even then I have not seen a cmd window popup so far.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Labview as the active window disables 1 or 2 concurrent while loops

    I am trying to get familiar with new mutltifunction DAQ hardware from IOtech - a DAQborad/2000.
    I have a simple vi consisting of two while loops which should be running in parallel. One acquires analog input data, the other handles DAC outputs.
    When I run the vi, the analog acquisition while loop runs fine, but the DAC while loop will not run if labview is the active window on the pc (frontpanel or diagram). If I make another window active, both loops will update as they should.
    I can resize a windows explorer window to make it small, run my vi, make windows explorer the active window and see the vi running both loops and updating as it should in the background. If I use the "Highlight Executi
    on" tool on the diagram screen, both loops run as they should.
    Any ideas?
    Thanks,
    Mike

    > I am trying to get familiar with new mutltifunction DAQ hardware from
    > IOtech - a DAQborad/2000.
    >
    Many third party drivers default to running in LV's UI thread, and if
    they put the thread to sleep, other LV threads can run, but not the UI.
    It is also possible that one of the loops is hogging while the other
    is being starved.
    So, I've got two suggestions to try. First try putting a delay of a few
    ms in the busy loop. This might help with the starvation. The second
    thing to try is to open up the IOTech VI and try setting the DLL node to
    be reentrant. This will allow the node to run in any thread and not
    force it into the UI thread. Beware that if the DLL isn't threadsafe,
    this could lead to data corruption or crashes, and before leaving it s
    et
    this way, you should probably contact IOTech to see if their DLL is
    threadsafe. If it is not, contact NI tech support and they can help you
    determine if it is safe in this case to leave it running in other threads.
    Greg McKaskle

  • Very slow performance of LabVIEW 6.1 under Windows XP

    I am using LabVIEW 6.1 under Windows XP. I found that sometimes it takes a long time for the operating system to load LabVIEW. Does anybody have the same experience?

    I have the same configuration on a PC and a laptop and I haven't had any problems. I also have >256MB RAM on both machines.
    My guess is that you have more than the LabVIEW recommended 64MB RAM on your machine but RAM is really the only thing that comes to mind for me. If you have a bunch of other applications running then it could take a while for LabVIEW to load to memory.
    Just a thought.
    -scraggs99
    -scraggs99

  • ERROR: Excel 97, LabVIEW 7.1 and Windows XP

    Hi,
    I began this discussion on another forum but I was mistaken in forum.
    http://forums.ni.com/ni/board/message?board.id=4170&message.id=4919#M4919
    I cannot continue my development.  Christophe S. sent VIs to me which work but I do not manage to open my own Excel file.  As soon as I add a node of property or method not present in his VIs, I have the same error again.
    I need to open an Excel file already filled.  I must modify the value of cells and the name of the various sheets of the workbook. I must also launch macros.  I already did all that at a customer with Excel 2000 under Windows98 and Windows2000 but my program does not work with Excel97.
    I practically tested all the examples codes and took all the advice of the site NI on this subject but they do not work even if they must work with Excel97. I thought that perhaps it was because of the pack 2 of Windows XP but on a PC with the pack 1, I have the same result. I should pass soon on Excel2003 but I do not know yet when and I cannot stop my développment for that.
    Did somebody already encounter this problem?  If so, how did you solve it? Thanks.

    In this moment, I am overloaded of work and I did not have time to carry out the tests which Chritophe S proposed to me.  On one PC, I had Office 97 but also Word2000 and Works2000.  It is possible that LabVIEW saw only ActiveX control 2000 and not 97.  From where my problems with Excel97.  I must uninstalle all that is 2000 and to remake a test with Office97. 
    I think that it will be difficult even impossible to develop VIs compatible with all the Excel versions.  When you call a node of property or a node of method, LabVIEW "looks at" which version of Excel is installed on the PC and, if the test required by Christophe S. is conclusive, that means that it would take into account only most recent ActiveX controls.
    If you create your VIx on PC having each one a version of Excel then that you recover on each one the program and that you finds a solution to see the version of ActiveX controls installed, you can perhaps develop your program.  But is this really useful? On the forum, we can find examples for each version. Nobody use all version in same time (more exactly of the very different versions unit).
    I think that it is better to develop a new program for each version. 
    Rmq:  it can perhaps exist various versions of ActiveX control for the same version of Excel.  You see that your program can quickly become painful to keep up to date.
    I don't know if there are the same ActiveX problems with another programming language.  So not, you can develop a DLL with another programming language and calls it under LabVIEW, if you want to really develop your "universal" VIs.
    I did not understand which complete documentation you sought.  On "Excel and its ActiveX controls" or on "LabVIEW and Excel"?
    Good luck

  • I have a application build in labview 8.5 for Windows XP using NI Visa functions to interact with hardware , how to make is work in Windows 7 32 bit and Win 7 64 bit

    I have a application build in Labview 8.5 which wroks fine with Windows XP , this program uses basic read /write functions of NI Visa to communicate with Hardware . This application doesnt work with Windows 7 32 bit/64 and Vista . What changes i need to do to make it work for the said operating system

    srinivas wrote:
    Sorry for confusion ,
    My question is what changes i need to do in code or while making the installer to make the existing program work with other Windows operating system
    You need to make sure the machine have the corresponding NI-VISA installed. Check in the NI software pages for the right version.
    Also make sure that the com port's can be selected when you first start the application. Eg. if you refer to VISA "COM1" on the XP machine It might be "COM2" on the Win7 machine.
    Br,
    /Roger

  • Labview RT dualboot with Windows 7 (Boot magic doesn't work)

    I'm trying to setup a desktop RT controller with both Labview RT and Windows 7. I can't seem to get the two on one bootloader screen. I have found that I need to boot into the RT partion either through the ready made USB in max external USB (EFI) or set as active (which causes windows to no longer be bootable). Much thanks.

    Why not just boot directly off the partition?  There are 2 rules for working with LabVIEW Real-Time from a partition:
    1.  On IDE, you can only use the primary drive.  It doesn't always work if you're using a primary slave or a secondary drive or secondary slave.  On SATA, use SATA0 for best compatibility.
    2.  It's best if the FAT32 partition you create for RT is located within the first 2GB of the disk.  Actually, it's best if you limit your FAT32 partition to 1GB in size (FAT32 degrades in performance and reliability the bigger you make the partition) and make the FAT32 partition start at the beginning of the drive.  Once you format the FAT32 partition with the USB key, you can boot off it.  Keeping the partition within the first 2GB of the disk is strictly for the 16-bit boot loader, it cannot address beyond 2GB so if your files could end up 4GB into the disk you've got problems.
    The tool I like using is System Commander for dual-booting, the benefit is being able to hide boot partitions from OS's that don't need them (if you want to hide one OS from the other).  I'd imagine you can use other boot systems the same way.
    -Danny

  • SDK error while installing Labview 8.2 on Windows 7

    Hello all,
                      I have been trying to install LabVIEW 8.2 version software on Windows 7. I always see an SDK error - 12. I saw an helpful artcle in knowledge base but i am not clear why this is happening?
    Could somebody explain indetail whether LV8.2 is compatible with Windows 7?
    If it is not compatible then i would like install vista or XP on my new Laptop, to work in LV8.2.
    Regards
    Visu

    Hi Viswa,
    Im afraid LabVIEW 8.2 is not compatible with Windows 7. If you wanted to use LabVIEW Windows 7 you would need a later version of LV, such as LabVIEW 2009.
    If you need to use LabVIEW 8.2 then installing Vista or XP on your machine would mean you could.
    Kind Regards
    Michael
    NIUK Application Engineer

  • Labview 7.1 crashes windows XP when using VI's saved with the 'Save for Previous Version' option available in Labview 8

    I am trying to work with a series of vi's developed in Labview 8 in Labview 7.1.  The code was saved with the 'Save for Previous Version' option available in Labview 8.  When trying to use the code in LV7.1 my entire Windows XP system locks up (cursor freezes).  Are there any ideas what's going on and how to fix this?
    Thanks for your help!
    Mike

    I have seen some problems with the save for previous option in the past. Instead of saving the entire hierarchy, try seperating the code into several different pieces and saving each piece individually. Then, see if you can open the different pieces in 7.1.
    If that doesn't help, you should post some more details, like when exactly does it lock up, does it have things like DLL calls, and maybe attach the code.
    Try to take over the world!

Maybe you are looking for