Installing LabVIEW 6.1 crashes MAX

Installing LabVIEW 6.1 on a computer with MAX version 1.0.1 Build 29, Win NT version 4.0.1381 Service Pack 6, and NI-488.2 Version 1.5 causes the system to blue screen when running MAX. Is a limited install the answer ?

I've also seen this crash if the DAQ cards installed comflict. For example
with a image grabber card and two PCI-6024E's MAX would crash whenever it
was opened. Removing the image grabber card solved the problem.
cheers, Alex.
Alexander C. Le Dain, PhD
ICON Technologies Pty Ltd
http://www.icon-tech.com.au
* The LabVIEW FAQ http://www.icon-tech.com.au/thelabviewfaq.html *

Similar Messages

Diadem 9 crashes after installing LabView 8.6

Hello,
I'm searching for a solution to fix a problem that occurred on Diadem 9.0 after installation of LabView 8.6.
The software was working fine until I've installed LabView. Since that time it crashes after few seconds I've already uninstalled it and installed it new, no progress...
Does anybody know what's the problem and how to fix it?
Thanks in advance,
Regards,
Paul
Solved!
Go to Solution.

Hello Paul and Otmar,
I had a similar problem a few month ago:
While installing LabVIEW 8.6, an actual NI-DAQmx driver was installed too. Please double-check the installed version. I guess, that it is something around NI-DAQmx 8.7. You will find this information in your "Measurement & Automation Explorer (MAX)" (Start -> Programms -> National Instruments). In MAX, please browse to 'My Computer -> Software -> NI-DAQmx'.
Please click on this item and you will get on the right side the installed version.
Unfortunately, the latest supported driver version of DIAdem 9.1 is NI-DAQmx 8.1. This information can be found here:
http://digital.ni.com/public.nsf/allkb/53BA46C79DE2786686257249005619A5?OpenDocument
If you have installed a later version of DAQmx, please consider to upgrade your DIAdem to a newer version. If this is not possible, you have to deinstall the actual DAQmx-driver and install DAQmx 8.1. This one can be found here:
http://joule.ni.com/nidu/cds/view/p/id/319/lang/en
I hope, that this helped you.
Best regards and have a great weekend
Message Edited by MarianMO on 04-17-2009 02:46 PM
MarianO

LabView 7.1 and MAX problems after installing and removing LabView 8.2

Hi all,
I came into a research lab and am using computers/programs set up by lab members in the past. We have been running LabView 7.1 on a Fujitsu P8020 laptop (its about 6 yrs old maybe?). Recently, we decided to install LabView 8.2. However, we could not get our program to work properly on v8.2, so we did a system restore to return the computer to its v7.1 settings. This seems to have been a bad idea.
Now, after the system restore, when opening the Measurement and Automation Explorer (it is v3.1), I get a message that "NIMax has encountered a problem and needs to close - we are sorry for the inconvenience". Additionally, when opening the labview script that had been working on v7.1 prior to 8.2 installation, it appears that certain VIs are missing, since it is asking me to "please find the VI named "xxxx.vi".
I would greatly appreciate any thoughts/help with this. I worry that fumbling around witht his by myself would only exacerbate problems.

RubbahSlippah wrote:
Hi all,
I came into a research lab and am using computers/programs set up by lab members in the past. We have been running LabView 7.1 on a Fujitsu P8020 laptop (its about 6 yrs old maybe?). Recently, we decided to install LabView 8.2. However, we could not get our program to work properly on v8.2, so we did a system restore to return the computer to its v7.1 settings. This seems to have been a bad idea.
Now, after the system restore, when opening the Measurement and Automation Explorer (it is v3.1), I get a message that "NIMax has encountered a problem and needs to close - we are sorry for the inconvenience". Additionally, when opening the labview script that had been working on v7.1 prior to 8.2 installation, it appears that certain VIs are missing, since it is asking me to "please find the VI named "xxxx.vi".
I would greatly appreciate any thoughts/help with this. I worry that fumbling around witht his by myself would only exacerbate problems.
Go to Control Panel --> Add or Remove Programs and click on National Instruments Software. Click the Change button. Repair all the stuff you find. (Be sure to have the CDs ready!) Hopefully it will get you back where you need to be.
I'm curious - did you try a mass compile after you upgraded to 8.2? There were fundamental differences between the two versions and a mass compile could've helped...
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.

I need to install LabView RT on a cFP-2010, but I only have LabView RT 2012 (need 8.5.1???)

Hello,
I have a cFP-2010 module that I got ahold of which has a software problem. When I got into the module through MAX, I got a message that said there was no software loaded and that the module was operating in safe-mode. I rebooted the cFP-2010 in user directed safe-mode and reformatted the disk. According to online documentation, the latest version of LabView RT that will work on a cFP-2010 is LabView RT 8.5.1. The only version of LabView RT that I have to work with is 2012. How do I load 8.5.1 on this module to get it working again? Is there a download available somehwere? When I go to load software on the module in MAX, there is no option for installing LabView RT... which appears to be what is required. Thanks!

Hello mdlund0,
If you do not have LabVIEW 8.5.1 and LabVIEW Real-Time 8.5.1 installed on your computer, then you will not see the option in MAX to push that software to your device. In order to optain that software, you will most likely need to contact your account representative. You can reach the NI customer service line at (800) 531-5066.
In terms of version compatibility, newer versions of LabVIEW are not supported on the cFP-2010 because of the limited memory available; the older software does not take as much space. This does not mean that you will be unable to use newer versions, just that the behavior is unsupported and the configuration not recommended. I would also like to inform you that you can interface with a FieldPoint device without having Real-Time installed on that device. You can both install software and pull data programmatically without having Real-Time. Please see these references for more information:
Install Software Without Having Real-Time: http://digital.ni.com/public.nsf/allkb/CE57D76B598AEA878625740C00671AF8?OpenDocument
Use FieldPoint Without Having Real-Time: http://digital.ni.com/public.nsf/allkb/0EFE203B68668366862577CE005654F1?OpenDocument
Hopefully these resources will be useful for you. Good luck working with your device!
Regards
Patrick
CLA

Error 404 causes Labview 2010 to crash but only occasionally

Hello,
I am requesting help to solve a problem with LabVIEW 2010 crashing. I am new to this company and the last Labview developer left without providing
background on this problem. Labview crashes after running project VIs. Labview closes without warning or error messages. The project acquires data from pressure transducers, dP transducers, thermocouples, IEPE, load cells, and voltages through NI real-time system and has digital I/O. NI hardware includes PXI-1050 with modules 6221, 6280, 6224, 6220 and NI PXI-1052, SCXI-1306, SCXI-1112, SCXI-1520, and SCXI-1102. I've reviewed the labview program and the software relies heavily on shared variables, references, and local variables but I cannot find anything that stands out as a problem in the software .
The program crashed again today after running for only 1/2 hour and was not recording data. No error message occurred before the crash and the only error after restarting LabVIEW was the standard message that LabVIEW did not close properly. I went to the Event Viewer and at the time of the crash I received the following information:
Event ID = 3299
Source = LabVIEW
Log = Application
Level = Error
LabVIEW Information: Error 404 "Not found" for "/national instruments/ real-time execution trace toolkit/ 2.0/ trace receiveport", file "Crogram files (x86)/ national instruments /shared/ ni webserver/ www/ national instruments/ real-time execution trace toolkit/ 2.0/ trace receiveport": Can't access URL
According to Event Viewer, this error 3299 occurred 15 times in the last 3 days. LabVIEW crashed today at 10:19 am at the same time this error 3299 occurred but LabVIEW did not crash the other times this error occurred in the last 3 days. I believe this error is related to the crash but does not usually cause the crash. It appears to me from reading the error message that the error is the result of occasional lose of communication with the real-time system (Can't find URL). Any suggestions how to resolve this would be greatly appreciated.
Bill

1. Have you had this code working before on this or another machine?
2. Which operating system and version of LabVIEW are you running? (This can be found in Control Panel >> All Control Panel Items >> System)
3. Which National Instruments Drivers are you using? (This can be found in the measurement an automation explorer under the software tab [a screenshot would be good])
I would look into removing afsetup.exe which is a data collection tool provided by Microsoft which could a) not be installed correctly and/or b) trying to pull data from LabVIEW. I think this may help you out, as even though your programs aren't explicitly calling it, the service is running in the background.
Secondly, I would look into stopping the NI Web Server application that could be polling a web page that's not needed.

Why does LabView 7.1 crash when using "Get Channel Info" vi ?

Hello,
I have written a program to get channel information for all my virtual channels. It worked fine in Labview 6i but when we upgraded to 7.1, it crashes with "Labview has generated errors and will be closed by WIndows". We have a SCXI-1001 with 6 SCXI 1102 modules, 2 SCXI 1102B modules, 1 SCXI-1102C module, and one SCXI-1140 module. Debugging reveals that the program crashes when the 1102C module channels are reached. I have attached the code I am currently using. Any help is appreciated. Thanks, Neil
Attachments:
maxinfo.zip ‏133 KB

Hello,
I have two questions for you please:
1. You mentioned early that debugging revealed that the problem was being originated on the SCXI-1102C module. Can you please try taking this module out and test your program again? Also try testing only one module and see if it works, then keep on adding more and see what happens.
2. I run your program on LabVIEW 7.1 and it didn't give me any problems. In general, anything on LabVIEW 6.1 cab be recognized by LabVIEW 7.1, so maybe the order of installation you did is not correct. Did you first take the board out, uninstall the previous version of NI-DAQ you had, install LabVIEW 7.1, then NI-DAQ 7.3 and then plugged the board in?
Please let me know about this.
Thanks,
LA

LabVIEW 6.1 crash on Windows 98 while performing data acquisition

I've just updated my system from LabVIEW 6.02 to 6.1 on my notebook (DELL Latitude CPi-A). Since then, I have a lot of trouble to perform data acquistion.
In debug mode, it appeared that it performed well the first acquisition (AI-config _ AI-start _ AI-read _ AI-close). And then it crashes the computer at the second loop : have to hard-reboot.
Any clue before I re-install LabVIEW 6.02 ????
Thanks,
Cyrille

Thank for your answer.
Actually, I'm sure (99%) that Ni-DAQ works well, because the test panel works fine. And through LabVIEW, it made the first acquisition in debug mode.
Today, I came back with fresh mind and follow some "common issues" with graphic acceleration.
So, I turned off the graphic acceleration from the windows system performance. And since then, everything seems to work well.
But I would suggest to NI to look a bit deeper on those graphic acceleration compatibility issues because it is not the first time I have to turn off this MS windows feature. In previous cases, the error came when I was modifying a XY graph.
Cyrille

On installing labview I get "error 1638 occurred..."

Hi I am trying to reinstall labview 6.1 on my PC after a hard disk crash. I get kicked out with the message "Error 1639 occurred while installing LabView 6.1". The machine is running Win2000 Professional.
I don't find any info as to what this eror message might mean. Any suggestions?
...Thanks in advance, Peter Grigg

Peter;
Since you had installed the same copy of Labview before, the CD is probably in good shape.
Things you can try:
- Double check if you are logged on with administrator privilegies. If you are not, try to install Labview from an administrator account
- There was a problem with the Labview installer that is reported as fixed, that stated that error 1639 would show up if one tries to type double quotes (") in the Organization Field during the install. Double check if you are doing that
Other than those two, you can try to install the same copy on a different machine to see if the same error shows. If it doesn't, there is something wrong with the installation of the OS on the machine that is giving you the error.
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

Labview 12.0 Crashes while trying to open a VI

Hi,
I've got a problem while opening a file. I did not have any problem opening it like five minutes ago. I tried to reboot the computer and shut down labview couple of times.
The labview 12.0 crashed and left me a message attached. And the problem VI is also attached.
Would you please help me with it?
Attachments:
Crash.PNG ‏21 KB
ClickToGo(RT).vi ‏71 KB

If you have a back up copy of the vi I would suggest going back to that. The vi and error message would indicate that you got what was refered to as an "insane" error, where LabVIEW lost track of some "connections" in the vi. This results in a corrupted vi which can't be loaded.
As was alluded to, a 1Mb+ size vi is pretty large, which, at least in the old days of LabVIEW, would increase the chances of getting "insane errors". If it is possibly to encapsulate some of the code in sub-vi's it might also help.
Sorry I can't fix the vi you had, most of us who have been using LabVIEW for a while have experienced this, good luck.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

How can i install labview in a AMD64Linux machine?

Hello:
I'm a linux user, I have Debian installed and maybe changing for Suse or Mandrake due to the NI's preference on those two OS. But I have only one question: is it possible to install LabVIEW in a linux that's native AMD64, this means, that if there's a 64-bit Linux Version of LabVIEW?
Thanks for reading this.

Hi panthell, your concerns have solid bases. If you want to Learn LabVIEW and get full functionality, I will suggest using Windows. But if you want to use Linux you will find less trouble with the 32 bit OS.
The 32 bit Suse can work with 64bits as if there were 32. So it could work, but you won’t have all the functionality or will have to deal with more small problems. Also there is a version of 64 bits of Suse, it has some compatibility mode to run programs as 32 bits systems. Using this final option you may have the core functionalities running but might have trouble with NI drivers. Still using Linux 64 bit will have some of the limits the Linux and the 64bits.
http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/suse9.0/adminguide-9.0/node14.html
LabVIEW as it works on a Runtime can be used in many platforms the officially supported are the ones that we had made tests and are confident they will work
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

Error while installing LabVIEW on Linux

Getting Error while installing LabVIEW on Linux and unable to use VISA.
Please check the installation Log i Have attached.
nilesh
Attachments:
Installation Log LV2012 Linux.txt ‏25 KB

I could not find a trail version for LINUX.
Its only available for Windows and mac.
Will it possible for you to give just the C++ library and include files??

Blue screen after installing labview 8

I recently installed Labview 8 Professional Dev. Suite on to a Win. XP SP2 system. The image before installation was stable. After the installation and reboot, the system blue screens (I have been unable to read the exact message on the blue screen) and reboots. I was able to boot if I selected "using last know configuration" option in the Windows XP boot options, indicating that the problem is driver/registry related. After I use the last know configuration, I get an error message "nidevmon.exe - Application Error. The application failed to initialize properly (0xc0000142). Click on OK to terminate the application."
I tried to repair all of the installed NI products without any success.
Device manager shows all devices installed properly without any conflicts.
Please advise on how I can resolve this installation conflict.
Thanks.
--Jeff

Hi, I am experiencing the same problem. When my system boots up I receive the "nidevmon.exe could not be initialized" error message. When I try to manually start the program after startup, I still get the same message. I am running Microsoft Windows XP [Version 5.1.2600] and have also updated my system with the latest patches. I have the ni USB-6008 device. My system is an IBM Thinkpad T40, 1.5Ghz Centrino, with 512MB ram, and 80GB hd. I have installed labview 7.1 and then NI-DAQmx 8.0 that came with the card.
Furthermore, the hardware does not succesfully install on my system. After I install the software, reboot and plug the usb device in, the hardware wizard pops up. However, in the end, I get "Windows cannot initialize the device driver for this hardware. (Code 37)". I suspect this has to do with the nidevmon.exe not initializing. The ni hardware appears to be fine, I have successfully installed the devices in another system. I uninstalled and reinstalled the ni-daqmx 8.0 software several times, and even downloaded version 7.5 from the web, however this did not solve the problem either. I would appreciate any suggestions..
Thanks,
Arash

Getting "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine

I am getting a "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine. I already tried running setup.exe as an administrator with the same results. I have Microsoft .NET Framework 4.5.1 installed on the affected machine. Could this be the cause of this issue? Or does someone know the root cause of such error?
Solved!
Go to Solution.

Hi - are you getting it at the start of installation, during or after 100% progress has finished?
Is it just LabVIEW you're installing, or is it drivers too, in which case, what was the last large package that was installing at the time?
This could be caused by the NVIDIA chipset driver :
https://decibel.ni.com/content/message/46299?tstart=-130
Thanks
Sacha
// it takes almost no time to rate an answer

Install LabVIEW on Windows 7 X64

I'm trying to install LabVIEW from NI Developer Suite Third Quarter 2009 on Windows 7 X64 machine. The install program terminates with an unexpected error. I can install LabWindows/CVI from the same DVDs onto this machine.
Solved!
Go to Solution.

I'm adding my own experience in installing LabVIEW 2009 onto Windows 7 (64 bit) in case it helps anyone else, but in fact there's no magic bullet for the problems I had, I did it the hard way.
I saw no error messages at all, just that when the installer wanted DVD no.2, the DVD drive seemed to disappear. Cursor remained as Windows 7 "timer donut", could do very little with PC except "master reset".
I tried:
A different DVD drive
Upgrading to Windows 7 sp1
Compatibility mode for Vista (as suggested above)
In the end I just copied the contents of the 3 install DVDs onto my hard disk. I named the directories as the DVD labels, and was impressed that the installer found all the parts automatically. Until it got to the Device Drivers DVD, which I had forgotten to copy, but mercifully at that stage I could browse to the DVD drive. No special compatibility settings used, but I did run setup.exe "as administrator".
I'll put this down as a Windows 7 bug (and maybe specific to my hardware ?) rather than an NI problem.
Along the way, as part of the sp1 upgrade, I got MS IE9, another great way to drop one's productivity (certainly made posting to this forum impossible, this done on a different machine).

When Trying to Install Labview 8.6.1 on Windows 7 Get Error Code -12

When Trying to Install Labview Deveopment Suite 8.6.1 on Windows 7 Get " *** Error: Windows SDK Function Returned an Error (Error Code -12)"
I assume a compatability issue will Labview installer and Windows 7. Is there a work arround?

I figured as much, but maybe if enough peole are interested NI will be pushed to a solution.
It's not that the programm won't run, it's that the installer fails before it even gets installed.
I am using Windows 7 RC Build 7100. It installs and runs just fine in Virtual XP Mode on Virtual PC for windows 7 (http://www.microsoft.com/windows/virtual-pc/download.aspx) which I find works better than compatability mode.
Thanks for your help.

Installing LabVIEW 6.1 crashes MAX

Similar Messages

Maybe you are looking for