Labview on Windows 2000

We are trying to install a lab with LabView 5.1 on a Windows 2000 system,
and we cannot get a PCI 1200 interface card to be recognised either by the
system or Labview itself.
Any advice please?
Dave Kleinberg
PC Technical Support
Physics and Astronomy
University of North Carolina at Chapel Hill
http://www.kleinberg.net/david

Thank you for all your help. NIDAQ 6.6 did indeed fix the problem, in
conjunction with version 5.1.1.
Thanks also to the guy who offered me a job, I have forwarded the info to
our lab manager who may know someone with more knowledge of LabView and
interest.
Dave Kleinberg
PC Technical Support
Physics and Astronomy
University of North Carolina at Chapel Hill
http://www.kleinberg.net/david
"Dave Kleinberg" wrote in message
news:[email protected]..
> We are trying to install a lab with LabView 5.1 on a Windows 2000 system,
> and we cannot get a PCI 1200 interface card to be recognised either by the
> system or Labview itself.
> Any advice please?
> ----
> Dave Kleinberg
> PC Technical Support
> Physics and Astronomy
> Uni
versity of North Carolina at Chapel Hill
> http://www.kleinberg.net/david
>
>
>
>

Similar Messages

Dual-boot LabVIEW RT/Windows 2000 on PXI

Is it possible to configure a PXI-based embedded PC (NI 8176) to run both LabVIEW RT and Windows 2000 in a dual-boot setup? I would like to use the same PXI system to do both real-time system prototyping as well as finished product testing - though not at the same time, of course.

Hi André,
Just to clarify, all dual-boot systems use the same hard drive for both operating systems. The floppy drive is used only for configuration. If you do not have a floppy drive, you can use a USB CD-ROM drive to load the recovery CD that ships with the controller. Please note that using the recovery CD may result in the loss of data from the previous Windows-only configuration. All of the important files should be backed-up prior to any recovery. For a better idea of what specific steps are involved, you can check out the following link:
http://digital.ni.com/public.nsf/websearch/227CF36870DB7BDB86256F790057F20F?OpenDocument
In particular, the section at the bottom goes through the process of converting to a dual-boot controller.
David H.
Applications Engineer
National Instruments
David H.
Systems Engineer
National Instruments

Compatibility of windows xp with labview and windows 2000 with labview

I have a very weird situation that I am not sure even I can decribe it clearly. The thing is we have two set of equipments. One: windows 2000 with DAQ card, PCI card, the other is windows xp with same DAQ card and PCI card. All the labview software are the same version. All the program are the same. But the program on windows xp has a really weird problem. Sometimes, the signal is wiped out when I run the program and sometimes it doesn't. I am curious whether the two windows system have different order sequency. Is it clear? I am really sorry about the description since the problem is really strange. Thank you very much!

With more research, I think I probably find the problem but I don't know how to fix it. Here is how the program work. In Calibrate LC.vi, there are four buttons of "set". When you hit set button, the program will aquire 10 data points which will form the signal we need. But the problem is when I hit set button, no signal at all.So I am thinking the program didn't aquire any data in. I uploaded the Calibrate LC vi and also the Aquire Data vi. Does anyone can give a suggestion how on to fix the problem? Also, I double checked the PCI card. The interrupt request for PCI 6036E in windows2000 computer is 19, that in windows xp computer is 21. Will this be a problem too? Thanks!
Attachments:
Acquire LC Calibration Data.vi ‏34 KB
Calibrate LC.vi ‏108 KB

Windows 2000 sendfax bug

When accessing comm1 through labview under windows 2000 os, a send fax wizard keeps popping up. When i create an .exe the program will not even work.

It sounds like your COM port has been configured and linked to your faxing application. I am running Win 2000 also, and don't have this problem, so I'm guessing it's just a configuration issue that you should be able to change. I would check the Wizard itself and see if you can change this configuration and if not, you'll need to look into the Windows configuration for the COM ports (yuck!).
J.R. Allen

How can I disable the access to windows 2000(O.S.) from LabView?

I need to disable the access to windows when an application (exe), created by LabView, is running. When the application is running, the user can not acces to windows (for example, execute another application) until he stops the application.
I am using LabView 6.1 and windows 2000
Many Thanks

Hi Francesc,
There are a couple of options for this. One of them could be calling Windows OS activex components and making the Desktop invisible through labVIEW and then bringing it back on after the LabVIEW execution is stopped.
The other option is to modify user settings on the target machine. I have tried this on windows 2000 and it works.
Run "gpedit.msc" from your start menu. In the Group Policy template choose the user configuration that you wish to make the settings for. Expand User Configuration , expand Administrative Templates , and then expand System. Choose 'Custom user interface'
In this panel select 'Enabled' and enter the interface file name, in this case C:\Program Files\National Instruments\Labview 6.1.exe. (or your own filepath\App
lication.exe). Reboot the machine.
This replaces the default windows shell (explorer.exe) with your LabVIEW executable. When the operator logs on, the only thing on his screen is the Labview application. No desktop, no taskbar, no start button.
This can also be done through LabVIEW using register-level programming. But it would be a more complex approach.
Hope this helps.
Regards,
Pravin Borade
Applications Engineer, National Instruments

Should I be able to reliable automate Excel 2000 on a Windows 2000 PC using Labview 7?

I am trying to automate Excel 2000 from Labview 7. I want to open an Excel application, open an existing workbook or create a new workbook, create a new sheet, save and exit. When using the Labview 7 .vi's I can create a new workbook, etc, and everything works fine. When the case in my program for existing file executes I can start Excel but I cannot open an existing worksheet (error -2146959355). I've selected a file using the labview file dialogue just to ensure spelling, case, etc but it always fails on the "open specific workbook" sub .vi and the first error is on the output of the "invoke node".
Out of curiosity I tried doing this in Labview 6.1 and after a cursory check ev
erything seems to work ok using the exact same sequence of .vi's. I am running Excel 2000 on Windows 2000. Should there be a compatibility issue? Would using the version 6.1 vi's within Labview 7 be a clean solution?
Thanks in advance

Thanks for responding.
I made a little vi to illustrate the problem.
The two sub .vi's I'm including with the main .vi are simply the renamed Version 6.1 and Version 7 "open specific workbook" .vi's. The main .vi was made in Version 7. All the other sub .vi's are V 7.
On my PC (Windows 2000 and Excel 2000) when the switch is set to "Version 6.1" it consistenly runs fine, set to "Version 7" it consistently fails.
I am very stumped! I've gone so far as to copy the V7 .llb from a different installation just in case something got corrupted somehow.
Attachments:
ExcelError.vi ‏44 KB
Open_Specific_WorkBookV6.vi ‏37 KB
Open_Specific_WorkBookV7.vi ‏37 KB

Has anyone encountered a Microsoft Visual C++ Runtime error in Windows 2000 when upgrading from Labview 6.0i to 6.0.2?

When I try to upgrade Labview 6.0i to 6.0.2 by running the setup.exe file I downloaded from the NI site, I immediately get a dialog box with the header "Microsoft Visual C++ Runtime Library" and it says "Runtime Error! Program: C:\setup.exe abnormal program termination."
I'm running Windows 2000, but I've successfully installed it on another computer with the same setup. I'm guess some of the DLL files in system32 has been corrupted or mismatched versions. But I don't know which one...
Anyone know what this means?

Hello,
You can probably solve this problem by going to Start >> Run and typing the following:
Regsvr32 \msi.dll
Where is the folder where the msi.dll file resides on your computer (you can use Start >> Find to find the exact location). Once you do this, the installation of the 6.0.2 update should work properly.
Please let me know if you continue to have 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

Labview 2009 .exe not working with windows 2000

I created a simple vi with Labview 2009 to reset a counter in registry key. I changed it to an exe. The program runs fine on any machine with XP but it does not work on the machine I need it on which is running Windows 2000 SP4. I installed the 2009 runtime but I continue to get an error when it starts up saying the vi is not executable and that I need the full development to fix the errors. But like I said it works every where else. I've tried other exe wrote in LV2009 on this machine and they work. Is there something in my vi that is not compatible with Windows 2000?
Thanks
Solved!
Go to Solution.
Attachments:
Serial Number Reset Cell 2.vi ‏15 KB

There was an issue with building DLLs on Windows 2000 - http://digital.ni.com/public.nsf/allkb/431C9BD8F3482033862576A90073441F. Since you say you are trying an EXE, this may not be applicable.
George M
National Instruments

Bug in LabVIEW 6.1 with Windows 2000 permissions

This is a bug I've discovered when using LabVIEW 6.1 in a multi-user Windows 2000 environment.
After underlying software changes and the like, it is common that when exiting a VI, a message pops up saying that an underlying VI has changed and must be saved. As a regular user, this cannot be done, because regular users don't have write access to the LabVIEW system folder.
When the same thing is done as Administrator, the changes can be saved. In this case, it was a change to a VI residing in the NI-DAQ ai.llb. After the save, the permissions on ai.llb (which by default included liberal access for the Users group) were changed to allow only access by the Administrators group, making it impossible for a regular user
to use that VI or any VI depending on it.
The solution is to manually edit the permissions on the .llb after the save to add the Users group back into the allowed users list.

NI has been keeping fairly up to date on permissions. If you search the entire www.ni.com using Administrator as the keyword, you'll find many of these issues and their resolutions.
2006 Ultimate LabVIEW G-eek.

Labview 4.1 application and Windows 2000/XP

Can a Labview 4.1 application running on Windows Nt 4.0 be moved to an Industrial Computer running Windows 2000 or Windows XP?

Within Windows XP you have the option of running a program as if it was using a different version of Windows. Right click on the program and then change the "Run As" option to whatever version of windows it is designed to work with.

Problems with the installation of LabVIEW 6.1 on Windows 2000!

Windows 2000 crashes while installing LabVIEW 6.1, and the computer is unusable after the installation!

This also happened to me. Hopefully you are attempting to run LabView on a dedicated computer. Ours had "issues" with some of the other software we were running. Here's what we did: We re-imaged the computer (backed up everything and re-loaded the OS). Computer has been up and running excellent ever since. There was a lot of useless software originally on it, we took it all off. If you are able, only run what you need on it. Also, we have found that LabVIEW 6 runs strangely on computers with less than 128 MB of RAM. Our project computer currently has 320 MB of RAM (and 40 GB HD) and it runs perfectly.
Hope this helps. If you have a specific error code, let me know. Otherwise, from what you have posted, I believe this is the answer.

LabVIEW 7.0 utilize the real-time functions in Window 2000 Real-time.

Can an application written with LabVIEW 7.0 utilize the real-time functions in Window 2000 Real-time.

The LabVIEW DATA ACQUISITION HANDBOOK (not sure of the exact title), has examples of simultaneous I/O, which is what I assume you need.
Clock- controlled analog output (to drive the stepper), and analog input (to read your inputs), sound like the ticket for you.
You could load the output buffer with a pattern that drives your stepper, and get multiple input samples for every step, all precisely timed.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Error 1326 while installing labview 6 on windows 2000

I am trying to install LabVIEW 6 on a windows 2000 system. I get an error 1326.Error getting file security
C:\WINNT\system 32\comctl32.ocx GetLasterror:5

I think this is a MS error code. Have you made sure that you have administrator privileges?
Jeremy

PC Crash with Labview 7 and windows 2000

Problem:
the PC does reboot without any prompt when a LV 7 vi is running; the reboot seems to occur randomly (no time dependent); sometimes instead of rebooting, the PC switches to the blue screen with the following message:
Stop: 0x0000001E (0xC0000002, 0x80419292, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED
Xxx Address 80419292 base at 80400000, date stamp 3EE6C002-ntoskrnl.exe
Starting memory download
Configuration:
Intel Pentium IV - 2.66 GHz - RAM 1 Gbyte - Video chipset Intel 82865G;
OS: Windows 2000
DAQ Board: PCI MIO 16 E1;
Labview 7 express - NIDAQ 7.1
Note:
The VI that causes the reboot uses the DAQMX to generate an Analog Output with analog trigger.

> The VI that causes the reboot uses the DAQMX to generate an Analog
> Output with analog trigger.
You probably want to post this problem to the DAQ message board as well
since LV itself really can't cause either of these problems on a
protected OS. Be sure to be very explicit about what HW boards and what
DaqMX calls you are making along with which version of the driver you have.
Greg McKaskle

LabVIEW program will not run on Windows 2000

I need to run parts of a LabVIEW program on a PC which does not contain all the hardware required to run the full version. This used to work on Windows 95/98 but on Windows 2000 I get error message 'Capabilty not supported. VI was stopped at node 0x1BC of subvi "Out Port.vi"'. This program is very large and full of references of this type, is there an easy way around this problem?

Hi,
I might be barking up the wrong tree here, but Windows 2000 is built on top of the architecture of Windows NT. Win NT/2000 treats direct memory access differently to Win95/98.
Have a look at the following link and see if that helps - unfortunately it involves re-writing (well, re-linking) the .vi's that are calling the out port.vi. The link is in reference to writing to the parallel port through direct memory access, but the .vi's are based on writing to any memory location.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/c80752c53094c296862565f3007ac765?OpenDocument
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000110A0000&ECategory=LabVIEW.LabVIEW+General
As you don't say wh
at version of LV you're using, the following link might also prove useful (if you're using LV 6.0.2+)
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000102F0000&ECategory=LabVIEW.LabVIEW+General
Hope that helps
S.
// it takes almost no time to rate an answer

Labview on Windows 2000

Similar Messages

Maybe you are looking for