LabWindows CVI 2009 9.1.0 - Build 64-bit Apps?

I have LabWindows/CVI 2009 (version 9.1.0 427). Can I build my apps as 64-bit apps? Do I need a service pack upgrade to do this? Or do I need to upgrade to a higher version of LCVI?
Thanks

LabWindows/CVI 2009 introduced the ability to create and distribute 64-bit executables, DLLs, and static libraries, see e.g. here

Similar Messages

Mysql database connection with Labwindows/CVI 2009 sql toolkit

Dear experienced users,
I am using the following software/hardware:
Windows 7/ Mysql database 5.6.15 64-bit with MySql ODBC 5.2 Ansi driver installed
Labwindows/CVI 2009 with sql toolkit
The user DSN of ODBC Data source administrator have been confiugred to one of mysql database. The test MYSQL Connector/ODBC is succesful.
The Labwindows/CVI build setting is configure to debug64 after trying debug (32)
The source code is from the example readtab.c with changes to the dsn I am testing
hdbc = DBConnect ("DSN=dvd_collection");
The error message I have is confusing me.
(it is in the attachd png)
I thought it was due to the 64 bit mysql database. That's why I tried the 64 bit build from Labwiondws/CVI. I alsow tried Labview DB tools open connect.vi. It shows me the same error.
Any suggestion is appreciated.
Thanks,
Jimmy
Attachments:
Capture.PNG ‏24 KB

Jimmy
I always use connection strings of the form "DSN=datasourcename;UID=database_user_id; PWD=database_user_password".
Where:
datasourcename = The name of the connection defined in the ODBC connection.
database_user_id = One of the user identities created by the database administrator. Obviously the administrator will lock down the permissions appropriate to the task in hand.
database_user_password = The password that identifies database_user_id, again set by the database administrator.
Note that while it is obviously desireable to lock the permissions down as far as possible on the MySQL server, the more you do so, the slower the database will run, because of the way mySQL searches the permissions tables.

LabWindows CVI 2009 Word_Rpt routines: Document is corrupted: Error reported: The MSWORD.OLB file cannot be opened.?

Using WordRpt support routines with a C application in LabWindows CVI 2009 to format Word files, an error sometimes occurs resulting in the document format being corrupted. An error is generated: The MSWORD.OLB file cannot be opened. I don't know why or how to correct this problem.
Any help you can provide would be appreciated!

Hi LPR1,
Do you have an application that reproduces this. If so, do you mind posting it?
Regards,
Hassan Atassi
NI Community Project Engineer

Labwindows CVI 2009 compatible issue with VISA 4.4.1?

Hi,
I would like to understand is there any compatible issue for Labwindows CVI 2009 with NI VISA 4.4.1? If so can you please direct me to the right document where this is document.
Can you also tell me what is the version of NI VISA for Labwindow CVI 2009. Please reply at the earliest.
Regards,
Usha

Apparently HP has stopped updating that application for Firefox. It wasn't available for Firefox 3.6 last year and now - not for 4.0 either.

Introducing LabWindows/CVI 2009

National Instruments released LabWindows/CVI 2009 on Friday, December 4th.
LabWindows/CVI 2009 includes enhanced productivity tools and introduces a new toolkit for run-time analysis and optimization. LabWindows/CVI 2009 also includes support for new technologies such as the Microsoft Windows 7 operating system, 64-bit application development and deployment, and provides a new interface for communicating with NI PXI FPGA-based hardware including FlexRIO and R Series data acquisition modules.
Visit the What's New page to see a full list of the new features in LabWindows/CVI 2009 that will help users create more reliable applications in a shorter amount of time and take advantage of new PC technologies. You can also view the What's New webcast series to get a closer look at the new features in LabWindows/CVI 2009. Some of the new features include:
The new Execution Profiler Toolkit, an application performance measurement and analysis tool
Improved debugging capabilities capabilities with extended information in the variables and watch windows
Easier user interface development with the attribute browser
Integrated support for 64-bit application development and deployment
The C- Interface to LabVIEW FPGA, a communication interface for FPGA-based hardware
Support for Windows 7, the latest Microsoft operating system
Additional Technical Resources Just for LabWindows/CVI Developers
Subscribe to the LabWindows/CVI Quarterly quarterly newsletter to receive the latest product news, tips and tricks, and developer resources. You can also join the LabWindows/CVI user community and start collaborating with users.
Adri Kruger
LabWindows/CVI Product Manager
Message Edited by Adri K. on 12-07-2009 03:28 PM
Adri Kruger
National Instruments
LabVIEW Product Marketing

Turbo,
There isn't a document that covers all the features from 6.0 to 2009, though there are documents that talk about individual upgrades.
http://www.ni.com/lwcvi/whats_new.htm
Also this document covers the upgrades since 8.0 http://zone.ni.com/devzone/cda/tut/p/id/7995
There have been quite a few upgrades, you can always download an evaluation version and test it out for yourself http://www.ni.com/lwcvi/try.htm
Richard S -- National Instruments --Applications Engineer -- Data Acquisition with TestStand

LabWindows/CVI 2009 Run-Time Engine update

I wanted to let everyone know that NI has released an udpated CVI 2009 Run-Time Engine. Information on what bug(s) this update fixes can be found here. If you are currently not using the CVI 2009 Run-Time Engine, you do not need to install this update.
This is an updated installation of the CVI Run-Time Engine, not a patch. If you download and install this update it will upgrade whichever version of the CVI Run-Time Engine you currently have to version 9.1.0.428 (CVI 2009 released with version 9.1.0.427). One way to find out which version of the CVI Run-Time Engine you have installed is to view the version number of c:\windows\system32\cvirte.dll. If you install version 9.1.0.428, any installer distributions that you create from any version of the CVI ADE will include version 9.1.0.428.
If you have not yet installed LabWindows/CVI 2009, it's recommended that you install this update, either before or after you install CVI 2009.
Luis

To be clear, the original problem that you reported ("Attempt to free pointer to memory not allocated by malloc() or calloc()") might very have been the problem that this patch fixed, which was in fact new to 2009. But that problem only happens if there were actual plots in the graph.
However, after looking at the "dynamic memory is corrupt" isse some more, it turns out that it is actually expected behavior, believe it or not. This is a limitation of easytab controls, caused by how they use callback chaining in their implementation. Whenever a panel or a control has its callback chained, you cannot change the callback, or make a copy of it after the chaining takes place. This is described in the EasyTab_ConvertFromCanvas function help ("...For the same reasons, do not call DuplicatePanel or DuplicateCtrl on any of these panels or controls after the Easy Tab control has been created.").
As you probably have read elsewhere, easytab controls are quite obsolete. They were a stopgap "solution" to the problem of there not being a native tab control in the CVI user interface library. Native tab controls were finally added in CVI 8.0, and so we recommend that, if possible, users update their code to use these instead.
Luis

Win 7 64 bit issues building 32 bit app

I am using LV2012 SP4(32 bit) on a win 7 (64 bit) system.
I have a program that uses a 32 bit PCMCIA card and I have built an application. There are no 64 bit drivers for my PCMCIA card, so I can only use it on XP or Win 7 (32 bit) system.
When I launch the application [built with LV2012 SP4(32 bit) on a win 7 (64 bit) system] on XP system, the PCMCIA card will not configure and sends an error.
I've copied my project to 32 bit XP system and built the application using the same [LV2012 SP4 (32bit)] and the executable works fine.
Why can't I build this app on my Win 7 (64 bit) system and get it working on an 32 bit system?
What is different about the compiler?

DSMarcinko wrote:
Yes it does. Win 7 (64) will not use 32 bit drivers.
This is not the problem.
Original problem is why LV won't build and run on 32 bit system when using a Win 7 (64) platform.
I was expecting a NI support tech to explain why I have this problem
I was thinking that you were packaging 64-bit LV drivers with your installation pkg.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

The application uninstaller ,created with Labwindows CVI, doesn´t work after upgrading to 2010 version

Hi,
I have been working with Labwindows CVI 2009 with no problem but after upgrading to 2010 version I have the following problem:
When i´m going to execute the unistaller, either from Windows Control Panel or directly from the uninst.exe icon, it doesn´t work. The PC thinks a few seconds and does nothing, and it happens with all the applications I build with Labwindows CVi 2010.
Thanks,
Asier
Solved!
Go to Solution.

Hello -
Are you installing these distributions on a non-English operating system? If so, the first thing to try would be the workaround listed on this known issue.
The known issue only lists Italian OSs as the troublesome OS, but it could actually happen on many different non-English OSs. I will update the text accordingly the next time I update the known issues list.
NickB
National Instruments

Compiling examples closes LabWindows/CVI

I have a NI USB-5132 module, with NI-SCOPE 3.7. I can bring up the device in "Measurement and Automation Explorer", and sees it as "Dev1". I can bring up NI-Scope Soft Front Panel, and toggle the device, read whatever I want to read. However, I'm trying to run on my CVI/LabWindows 2009 platform, but when I try to compile ANY of the examples, the development software closes. No error message....nothing. When I try to create a new DAQmx task, it sees no available devices for ANY of the possible measurements.
Please help! Otherwise, it would seem my work has purchased a very expensive method to click the exit button.

Hi Chris,
I'm sorry to hear that you are having so much trouble! Could you please provide some more details regarding when you experience this crash? Does this crash occur when you compile all programs or just specific ones? What examples are you attempting to compile? If this is the first time that you are compiling and are experiencing this issue, please refer to the following known bugs in CVI 2009
LabWindows™/CVI™ 2009 and 2009 SP1 Known Issues
LabWindows/CVI may crash if compiling a project that includes LabWindows/CVI header files with a line containing the #pragma soft_reference statement
Compiling a file with a syntax error can cause LabWindows/CVI to crash.
If these known bugs are not relevant to your code, can you please post a WinDbg log. The following explains how to do this. Despite this article being applied to LabVIEW, this is relevant for CVI as well.
Using WinDbg for LabVIEW Error Reporting
If you are running an operating system previous to Windows 7, please refer to the following:
Description of the Dr. Watson for Windows (Drwtsn32.exe) Tool
I look forward to your response. Have a great day!
Regards,
Jackie
DAQ Product Marketing Engineer
National Instruments

Lack of IviDigitizer class driver in LabWindow/CVI

Hello,
I try to create IVI Specific driver in LabWindow/CVI version 9.0.1 for digitizer but I don't see any of this types of instruments. I have installed newest IVI Compliance Package 4.6.1. There is lack of few others IVI class drivers like counter etc. Does anybody know what I should do with this?
Regards
Tomek

Hi Tomek,
The support for IviDigitizer, IviCounter, IviUpconverter, and IviDownconverter was added in LabWindows/CVI 2009. Please contact us at [email protected] and we'll send you the missing template files.
Thanks.

Labwindows CVI install - Windows SDK error

Hello,
I have a problem when I try to install Labwindows CVI 9 on Windows 7.
I had no problems so far, but now the installation doesn't work and the following message appears:
Do you help me please, it's very important and urgent.
Thank you.
Best Regards.
Karine.

Hello,
I don't really understand the issue... you said that you have no problem when you install LabWindows CVI 2009 on Windows 7 - that's good!
And now you have an issue with an installation... with another software (I guess) ?
This error appears when you are installing an incompatible version or your toolkit/drivers/software with your actual OS.
As you are using Win 7, I suggest you to check the compatibility of what you want to install on your computer : http://www.ni.com/white-paper/10383/en
Regards,
Celine
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées Techniques LabVIEW
Du 15 octobre au 7 novembre : Strasbourg - Lyon - Lille - Toulouse - Mar...

Intercept LabWindows/CVI CLOSE event

In my LabWindows UI the user can click the X on the top right to quit the application.
I'd like to intercept that message to do various things before it gets to the TestStand Engine.
I tried to use InstallWinMsgCallback for a WM_QUIT and WM_CLOSE but it doesn't get called.
Thanks,
Ronnie
TestStand 4.2.1, LabVIEW 2009, LabWindows/CVI 2009
Solved!
Go to Solution.

OK - I figured it out - it's the EVENT_CLOSE generated by the MainPanelCallback.
TestStand 4.2.1, LabVIEW 2009, LabWindows/CVI 2009

CVI 2009 menu bar resize problem

In CVI 2009, if you have the 'scale contents on resize' attribute set for a panel with a menu bar on it, the menu bar font resizes with the panel.
Unfortunately, there is a rather severe bug in this. If you do the following repeatedly:
(a) Load a panel with 'scale contents on resize' set and a menu bar
(b) Enlarge it
(c) Display it
(d) Hide it
(e) Discard it
then the menu bar font gets progressively bigger and bigger each time the panel is displayed. Below is an example from the test project attached to this posting (four successive display iterations). To say this is inconvenient is understating the truth: It actually breaks many of my applications. Is there any way to stop this behaviour?
Martin
Certified CVI Developer
Attachments:
TestMenu.zip ‏6 KB

Hello Martin -
I'm very sorry for the inconvenience this bug has caused. Another workaround that may be a little simpler would be to update the font of the menubar with a newly created metafont immediately before showing the panel (and after resizing). This also has the added benefit of the menu retaining it's original size instead of being scaled. You could accomplish this with code similar to the following:
int hNewPanel, hMenuBar;
hNewPanel = LoadPanel (0, "TestMenu.uir", MENUPANEL);
hMenuBar = GetPanelMenuBar (hNewPanel);
SetPanelSize (hNewPanel, 600, 800);
CreateMetaFontEx ("NewMenuMetaFont", "NIMenuMetaFont", 13, 0, 0, 0, 0, 0);
SetMenuBarAttribute (hMenuBar, 0, ATTR_MENU_BAR_FONT, "NewMenuMetaFont");
I also just wanted to add why the behavior of scaling menus with "Scale Contents On Resize" changed in LabWindows/CVI 2009. The problem was that when using scale contents on resize, all fonts are supposed to scale proportionately to the scaling of the panel. However, menu fonts did not scale, and this led to the problems seen in this forum. Because of the inconsistenty and to fix the bug reported on that forum, bug report 134165 was created and then fixed in LabWindows/CVI 2009.
Once again, I'm sorry for the inconvenience this has caused,
NickB
National Instruments

.exe Build from LabWindow/CVI 7.1 run exception under RTE 8.0.1

Below is the source file of test1.exe, which was built using LabWindow/CVI 7.1 environment, OS is Windows XP SP3
Due to some reason(install TestStand, or LabView, or ...), the Runtime Engine cvirte.dll, cvirt.dll (exists in c:\windows\system32\ )is 8.0.1
Executing this file, the GenericMessagePopup() will generate window's exception. But if executing GenericMessagePopup() before LoadLibrary(), it will be ok.
By the way, "cp3245mt.dll" is Borland's DLL. If load other DLL, everything is OK.
Is there any suggestion to solve the conflict between NI and Borland? Thanks!
// test1.c sourcefile
#include <windows.h>
#include <userint.h>
#include <stdio.h>
main()
// If execute the below line first. it will be ok.
//    GenericMessagePopup("Info", "Test","Yes","No",0,0,0,0,
//   VAL_GENERIC_POPUP_BTN1,VAL_GENERIC_POPUP_NO_CTRL,VAL_GENERIC_POPUP_BTN2);
   LoadLibrary("cp3245mt.dll");
   GenericMessagePopup("Info", "Test","Yes","No",0,0,0,0, VAL_GENERIC_POPUP_BTN1,VAL_GENERIC_POPUP_NO_CTRL,VAL_GENERIC_POPUP_BTN2);

Did you ever figure this out. I've set classpaths, the APPCPATH variable several
times with many variations and its not working for me, though the jsp thing is working.

Unable to use external compiler support in CVI 2009 with VC++ 2005

The compiler gives me this error message:
cvisupp.lib(setprec.obj) : fatal error LNK1103: debugging information corrupt; recompile module
Solved!
Go to Solution.

Well, I do call InitCVIRTE in my main, but it doesn't find it in cvisupp.lib, it finds _InitCVIRTEEx@12   this way:
00404808    _InitCVIRTE@4                                    initcls.obj
00404818      _InitCVIRTEEx@12                              initcls.obj
004048FC      _CloseCVIRTE@0                                initcls.obj
The identifier cvisupp.lib is no where in the map of my project.
I do see this library in the NI folders on the PC however.
I think we may be crossed up here in what we're doing - I am building the application from the LabWindows 2009 framework in release mode using the VCPP 2005 compiler as an external compiler ... are you building from Visual Studio or from CVI 2009?
Menchar

LabWindows CVI 2009 9.1.0 - Build 64-bit Apps?

Similar Messages

Maybe you are looking for