Running VI's on Labview 7.1 with Windows 7

Hi,
So I know that Labview 7.1 is not support by Windows 7, but I have noticed people on these forums have been getting it to work (sort of).
I have managed to get our PCI 6221 card to work on our Windows 7 x86 machine with NI-DAQmx 9.4 installed, and I have installed Labview 7.1 on the machine as well. But my issue is when I try to load any of our VI's (ones that we run from Windows XP) it starts to load them but it then wants to find various VI's such as "DAQmx Create Task.vi", "DAQmx Create Virtual Channel.vi" etc. And when I hit cancel and then stop (as I cannot locate these VI's) Labview will not operate properly.
Is there something I am missing or are our VI's not compatible with Win 7?
Cheers,
Tim

nathand wrote:
DAQmx 9.4 does not include support for LabVIEW 7.1. You could try uninstalling, and going back to a much earlier version of DAQmx.
But that version is likely not able to support Windows 7. DAQmx contains a lot of kernel space components, and a kernel driver originally written for Windows XP, quite likely won't work without issues under Windows 7.
What I have gotten away with once, was to install LabVIEW 7.1 on an older XP PC, then a DAQmx version that supports 7.1, and then do the same on the Windows 7 PC but with the newer DAQmx, and then copy all the DAQmx VIs from the XP PC into your new LabVIEW installation. A tedious work and with a high chance that some of the VIs won't be compatible with the new DAQmx driver. It worked for a simple DIO application but your mileage may vary greatly.
Another approach might be to backsave the VIs in a supported LabVIEW version to 8.0 and then using LabVIEW 8.0 to backsave it to 7.1 but that is even more tedious if you want to get all DAQmx VIs backsaved, and likely will require some additional editing on the VIs to cater for unsupported features in 7.1.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

Premiere Elements 12 will not run after installing on my HP laptop with Windows 7.

Premiere Elements 12 will not run after installing on my HP laptop with Windows 7. HOWEVER, PE11, PE10 & PE 9 all run without a problem. I contacted HP, and there are NO NEW or ADDITIONAL video drivers available from HP.
I have NEVER had a problem running ANY software on this laptop -- except for PREMIERE ELEMENTS 12!

Premiere Elements 12 will not run after installing on my HP laptop with Windows 7. HOWEVER, PE11, PE10 & PE 9 all run without a problem. I contacted HP, and there are NO NEW or ADDITIONAL video drivers available from HP.
I have NEVER had a problem running ANY software on this laptop -- except for PREMIERE ELEMENTS 12!

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

Is labview 8 compatible with windows XP

Is Labview Version: 8.0.1 compatible with windows XP?
How do I take a back up of the current data and transfer it to a new machine?
-Mat

Mat J wrote:
Is Labview Version: 8.0.1 compatible with windows XP?
Yes
How do I take a back up of the current data and transfer it to a new machine?
Um...... copy the files to a CD/DVD/flash drive or copy over a network connection?

Is labview 5 compatible with Windows XP home and professional version?

Can i install labview 5.0 on a windows XP environment- home and professional version?
Also is labview 5.0 and 7.0 compatible with Celerons? Or is there any difficulty?
Please clarify

They all work fine in these environs. The only trouble you may run into is temporary files not being accessible if the user logged in is not an administrator or the vi was created by an admin and a limited user tries to run it. This can easily be fixed by giving lower users permissions to use these files. The legacy versions of NI-DAQ do not run on XP though, you'll have to use a more recent version of them.
2006 Ultimate LabVIEW G-eek.

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

How do I restore my backup (.wim files) after running HP System recovery on a G62 with windows 7

I had to do a system restore after getting a blue screen and I backed up the files on my external drive. after restoring the system I tried to restore my files from my external with Recovery manager but it didn't see my external so I couldn't restore. I copied and pasted the backup folder on my g62 desktop and tried again with no results. As far as I can tell the restore was done because my free space on the g 62 decreased by the same size as the backup, but when I open the c:\ drive I can't see the transfer. these are .wim files and I even tried to call tech service (my warranty juse expired) and they were trying to sell me extended warranty for the next year to help me. the problem exist with HP if they had good programs that follow up what it was meant to do maybe Today I wouldn't be here looking for help. when I restored the system, recovery told me the it would install my backup, but nothing happened leaving me hanging.NEED HELP!!!!!!!!!!!!!!

If you call AppleCare they will be more than willing to help you. Use the appropriate phone number on this page. Tell them you need a support related fulfillment - replacement disks. As shldr says there will be a small charge, but you will be able to install your system again.
Best of luck.

Text runs of the page / doesn't resize with window

Hi,
I have seen this before but cant figure out how to fix this:
In Mail and other applicaitons that involve typing text the sentenses run off the "page".
When I resize the window the lines dont' adapt to the window.
I am stumped, please help :-)
Rogier

Howdy. See if this helps:
https://discussions.apple.com/thread/5298047?tstart=150

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.

I am running FireFox on a new HP laptop with Windows 8.1. My email program ATT yahoo.mail is constantly showing error message "Mozilla Firefox is not responding

Only happens with the email program

Hello,
Sometimes antivirus extensions cause browsing issues in Firefox. Try disabling McAfee while on your email program to see if it still crashes.
If after disabling McAfee the site still crashes, enable that plugin again if you wish. Please follow the steps below to provide us crash IDs to help us learn more about your crash.
#Enter ''about:crashes'' in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
#Copy the '''5''' most recent Report IDs that start with '''bp-''' and then go back to your forum question and paste that into the "Post a Reply" box. (Please don't take a screenshot of your crashes, just copy and paste the ID's. The below image is just an example of what your Firefox screen should look like)
[[Image:aboutcrashesFx29|width=520]]
<br><br>
Thank you for your help!
More information and further troubleshooting steps can be found in the [[Firefox crashes - Troubleshoot, prevent and get help fixing crashes]] article.

Labview 2012 Installer builder issues with Windows 7 64 bit

I have a clients project application program I am working on and am having a lot of trouble getting installed applications to work on Windows 7 properly. The Labview Installer sets the default installation directory to "c:\Program Files\" on Windows Xp and on Windows 7 64bit this defaults to "C:\Program Files (x86). When I install the application on Windows 7 and run it, because Windows 7 64 bit unreasonably protects this directory and every folder under it, if you try to write file to any subdirectory under it (like a reports directory), windows 7 will not let the file write to the directory and the file(s) disappear and you get permission errors. This has been difficult to address. Even logging in as administrator, I have difficulty changing the folder permissions. In addition, when I am in the file write process, if the default directory is coded to come up in the file Open/Save dialog, will not properly
go to and display these protected directories. So thinking that OK, I'll just chage the install directory to something direct to the C: drive and not the Program Files (x86) directory, so I have better control of the folder permissions. Now the Installer build gives errors. It built, but the install fails. Looks like National did not test this for Windows 7 very well. I have run into just about every issue possible with Windows 7 and Labview. Clearly Labview was not very well tested with Windows 7 6 bit. I do not have the Internet toolkit added to the application, only the VISA 5.2 driver. Anyone else having application issues with Labview and Windows 7 and have ideas how to work around this??
Attachments:
BuildErrors.txt ‏11 KB

It's no NI's fault and has nothing to do with 64 Bit either. It is something MS changed starting with Vista, namely tightening security of the whole system to a similar level as was usual on more professional OSes like Unix 20 years earlier. A user has not rights anymore to write into the location where applications are installed. This is for one reason to protect installed applications from being modified by malicious code.
Instead every application should write its runtime data in one of the user writable loacations such as the user's Documents directory for data files, or in the user's or the machine's configuration directory for configuration settings. For single installations you could always set the directory which your application got installed into to be user writable by changing the rights of that directory afterwards but for applications that get installed on normal user computers this is a VERY hacky and discouraged move. Same about installing your application into the root of your system drive. I think it was an oversight by MS to not protect that directory too from user modifications, but was most likely unavoidable to allow DOS application installations to still work.
LabVIEW has functions to retrieve a whole bunch of those preconfigured and user writeable locations and you really should change your application to make use of those locations, instead of trying to write into the installation directory or installing the application into the root location of the system drive, if you want to be compatible with Windows Vista/7/8.
Windows 7 also requires for a number of actions such as installing programs or drivers so called elevated rights. This means that even if you are logged in as administrator you have to explicitedly provide the admin password again to be able to perform the action. This can be done by starting the program as administrator, when this is available in the right click pop-up menu, and is also sometimes done automatically for applications that Windows determines to need those rights such as setup programs for installations.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Will Labview 6.0 work with windows 7 32 or 64 bit

We have a machine here at work which is set up running labview 6.0 with windows 98. The pc on the machine is WAY too old. We are looking to replace it and I need to know if this version will run on windows 7 (32 or 64 bit OS), or do we need to run an older OS.
Thanks in advance for any help.

Did you try a search? http://zone.ni.com/devzone/cda/tut/p/id/10383#toc1
So, the official answer is no. The practical answer? Maybe. If you can get it to install, that is. Please do a search on installing previous versions of LabVIEW on Windows 7, as this question has also been asked many times.

Using the isight camera in the bootcamp setup with windows 8.1

Hi
I am running OSX Maverick in a bootcamp setup with Windows 8.1 and have played around with the isight camera but I would like to know what folder the photo's/video's are sent to?
Also, are there any settings or user guide for the isight camera in Windows 8.1?
Thanks

I don't use Boot Camp, but does anything here help you? Boot Camp - Apple Support.
My look there did not show anything about the new Windows 8.1. The latest I saw was Windows 8.
Brave01Heart wrote: ... what folder the photo's/video's are sent to?...
The answer will be wherever the app you are iusing for the capture stores them unless you change the default location. This answer is the same for either Windows or Apple operating systems.

Using ipod with windows millenium

Hi
I am having problems with installing ipod mini with my computer. Aparantly ipod requires min of windows 2000 or XP however my computer has windows millenium as operating system.
Having tried to upgrade to XP this resulted in my computer crashing and me having to use the computer recovery disc.
I am scared of trying to upgrade my computer. Is there any way that ipod mini can be used with windows millenium.
Hoping for Help
Shane

It can be done, Shane, but it's not easy.
iTunes won't work under ME, so you'll need a replacement. The iPod Updater, also required to prepare the iPod for Windows use, won't work either under ME. You'll need to install and run the iPod Updater on a computer with Windows XP to get your mini ready.
See this:
Guide to iPod and Windows ME

Running LabView 7.1 with PCI-6251 in Windows 7

I am very new to Labview, and would appreciate any assistance on this issue. I was tasked with solving it and while I have made some progress I have now hit a wall.
A computer with a PCI-6251 data capture card, some custom built (external) hardware and LabView 7.1 has been used for many years for a single, specific task, to do verification testing in a manufacturing environment. The system works well and no additional features or functionality is required.
The computer failed and a new one with a PCI card slot was purchased to replace it. Of course as a new PC it has Windows 7 and hardware drivers for XP don’t exist. I therefore need to run LabView 7.1 on Windows 7 with a NI-DAQ card.
I installed the NI-DAQmx 9.5.1 driver and then installed LabView 7.1 (as discussed here). The driver would not install if LabView was already installed since it gave the “unsupported on this version of windows error”. MAX recognized the card, which it couldn’t when trying to use the 7.5 NI-DAQ driver.
Now LabView opens but when I try to run the .vi used for testing it complains of 19 missing sub .vis which I cannot locate and I can’t find on the old computer to try to point LabView towards.
I think something weird is occurring with trying to use the 9.5.1 driver with LabView 7.1. Are there any suggestion or is there any advice on getting a PCI-6251 working with Labview 7.1 on a Windows 7 machine?
Solved!
Go to Solution.

After much greif and trying a half dozen various drivers with various settings and other ideas the following procedure based on Caraval's advice worked first time with no errors and seemingly no functional issues. The system so far appears to be running in Windows 7 just as it was on Windows XP.
1. Install LabView from original install CDs, by opening the folder and right-clicking 'setup.exe' and clicking 'run as administrator'. Selected 'do not install drivers' during the install procedure. Rebooted computer.
2. Installed NI-DAQmx 8.9 from the self-extracting .zip file available here. Shutdown computer.
3. Removed power, pressed power button to completely discharge power supply. Installed PCI-6251 card.
4. Booted computer, and logged in. Waited a long time, Windows eventually saw new hardware and installed drivers. Verified MAX could see card.
5. Opened LabView and everything worked.
Looks like we bought the system a few more years. Will probably have to upgrade everything next time around though. Many thanks to everyone who commented on this thread.

Running VI's on Labview 7.1 with Windows 7

Similar Messages

Maybe you are looking for