Can I run Labview 4.1 on Win95?

Currently running Win 3.1, but need to get new computer. Can we run 4.1 on Win 95 or higher without any issues?

See this posting on the same subject. I think the biggest issue will be your old drivers for NI-DAQ and GPIB if you're using them.

Similar Messages

Can you run labview on Windows Tablet PC Edition?

Can you run labview on Windows Tablet PC Edition?...or does LabVIEW executable and Run-time engine operate with this OS?

LabVIEW 7.x will run without any problems on a Windows Tablet PC with SP1. There have been documented issues with Windows XP SP2 and LabVIEW subsequently not exiting properly--LabVIEW's window closes but somehow it is still present in the task manager.
Hope this helps.

Can i run labview on Windows CE or embedded XP?

If it is possible, what are the minimum specifications for the PC? And can anyone recommend a manufacturer?

Basically, anything that will run on XP should run on XP Embedded. I am
presently running LabVIEW applications on XP Embedded. Windows CE is a
totally different operating system and will not presently run LabVIEW (NI
should verify this but I'm fairly sure this is true). You'll have to ask NI
when this will change but I think there will be CE support in the future.
XP Embedded should run on any PC that XP will run on but if you stick with
better known brands and components you'll have an easier time building your
XP application. Your speed should be similar to regular XP but your hard
drive space is usually a lot less because you strip out as much of the
operating system as you want. I am running on bootable CDs without any hard
drive.
"stew j" l> wrote in message
news:[email protected]..
> If it is possible, what are the minimum specifications for the PC? And
> can anyone recommend a manufacturer?

Can I run LabVIEW DSC on Fieldpoint real time processor?

I want to use the Fieldpoint real-time processor as an OPC server on the network. Can I run DSC runtime on the Fieldpoint processor?

There are two separate questions here. One, can a FieldPoint Real-Time Controller act as an OPC Server, and two, can the DSC Run-time engine be downloaded into the FP-20XX controller. The answer to both questions is no.
The FieldPoint RT modules are running a Real-Time OS, they are not running any version of Microsoft Windows. The OPC Specification is based upon Microsoft's DCOM model which is built into Microsoft Operating Systems. This does not exist in the built-in OS and thus the FieldPoint unit can not be an OPC Server. However, a host PC running Windows can have an OPC Server on it that in turn publishes all of the data from the FP-20XX module.
Can the DSC run-time be loaded into a FP-20XX? No, it was never designed for it and would not fit in the mod
ule.
Regards,
Aaron

I can't run labview, an error appears : stack overflow.

My system is Windows NT. I use Labview to acquire images. I used Measurement and Automation to calibrate the acquisition card.After that I would to open labview, but an error appeared "stack overflow". I tried to reinstall Labview but the error is always present.

Did you try completely uninstalling labVIEW before attempting to reinstall? Probably would not hurt to clear the registry entries either. It sounds like something became corrupted.

Run labview exe in other way than runtime engine?

Hi guys
This might be stupid question, but can I run labview's *.exe in other way than in the runtime engine? In these days in have done *exe and installer with runtime engine and give it to the end-user. It does not matter how tiny ur code is, user have to install 40 conponents and then restart computer... How annoying. Is there eny other way? Can i use other programming languages some how?
-AA-

If the runtime is only one out of 40 components, it should not make a big difference for you.
I always tell my users to download and install the runtime engine directly from NI. This needs to be done only once per PC and per runtime version, at which point you can distribute a small installer.
There is also an idea to simplify all this. Please support it.
(It is not reasonable to be able to build an executable with embedded runtime, that would make a LabVIEW 2009 executable 100+MB in size. (We had that back in LabVIEW 4.0, where each 20kb VI turned into a 3+MB executable, which was significant in the days of 1GB drives.)
Message Edited by altenbach on 12-16-2009 11:42 AM
LabVIEW Champion . Do more with less code and in less time .

How can I run two independant LabView applications from the same computer, without taking a performance hit?

I have two identical, but independant test stations, both feeding data back to a Data Acquisition Computer running LabView 6.1. Everything is duplicated at the computer as well, with two E-series multifunction I/O cards (one for each test station) and two instances of the same LabView program for acquiring and analysing the data. The DAQ computer has a Celeron processor w/ 850Mhz clock and 512MB memory, and is running on Windows NT.
I have noticed that when I run both the applications simultaneously, I take a substantial performance hit in terms of processing speed (as opposed to running just one program). Why does this happen and how can I prevent it? (In t
his particular case, it may be possible to combine both the tests into one program since they are identical, but independant, simultaneous control of two different LabView programs is a concept I need to prove out).
Thanks in advance for any tips, hints and spoon feedings (!)....

Depending on your application, you may or may not be able to improve things.
Firstly, each task requires CPU time, so a certain performance difference is guaranteed. Making sure you have a "wait until ms" in every while loop helps in all but the most CPU intensive programs.
Secondly, if you are
1) streaming data to disk
2) Acquiring lots of data over the PCI bus
3) Sending lots of data o ver the network
you can have bottlenecks elsewhere than in your program (limited Disk, PCI or Network bandwidth).
Avoid also displaying data which doesn`t need to be displayed. An array indicator which only shows one element still needs a lot of processing time if the array itself is large.... Best is to set the indicator invisible if this is the case.
I think
it would be best if you could give some more information about the amount of data being acquired, processed and sent. Then maybe it will be more obvious where you can optimise things. If you are running W2000, try activating the task manager while the program(s) are sunning to see where the bottleneck is.
Shane
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)

How do you create a program in Labview that can be run as a Windows Service?

I would like to create a Labview program that can be run as a Windows service. I have read the following Knowlegebase articles and have done what they say.
Creating a Windows NT Service Using LabVIEW http://www.ni.com/white-paper/3185/en
Running a LabVIEW Application as a Windows NT/2000/XP/Server 2008/7 User-Defined Service http://digital.ni.com/public.nsf/allkb/21BA0F671A63A60386256CB4004DF99B
When trying to start the service I get an error that says the program didn't respond to the start in a timely manner. I also set the "run when opened" parameter in the VI. I am programming in Labivew 2010, proffesional version. The server is running Windows Server 2008. Can anyone help? Is the ini file important in Windows Server 2008?

I haven't looked through all those links. But I have created Windows Services from LabVIEW executables way back when WinXP came on the market.
The problem with services is that they have no UI. So you can't really see what is going on. Your EXE might be failing or hanging due to some kind of error (most liklely a security/permissions error), but you can't see the error. So my advice is to either:
1. Have your EXE write lots of info to a log file. Write info that log every step in the application. If an error ocurrs, have it write the error info to the log file. That is a very useful debugging tool.
2. Use VI Server functions to monitor the service to see what is going on.

Can you run a window version of LabVIEW on an Apple MacBook Pro using boot camp?

Can you run a window version of LabVIEW 8 on an Apple MacBook Pro using boot camp?

I don't have a mac, but you may want to read this:
http://themacview.blogspot.com/
Should give you more info about what NI is saying.
Matt Holt
Certified LabVIEW Architect

I created an application on a machine with Labview 6.01, can I run this application on another machine that has labview 5?

In the development center we use Labview 6.01, in the testcenter we use labview 5.
Additionally, in the development center we use a unix version of Labview and in the testcenter a Windows version.

You can Save with Option to save VIs as version 5.
Unless your VIs deal with system files in UNIX or Windows (ie. Registry...)
then you have to develop your VI specificly on that OS, since UNIX and
Windows have different ways to deal with system files. Mostly, LabVIEW is OS
independent. I used to have VIs developed from LabVIEW v.3 on UNIX, I can
still open these files from LV v.4 on Windows. Now I can still work with
these VIs on LV 6 on Windows.
Good luck,
Nam.
roybra wrote in message
news:[email protected]..
> I created an application on a machine with Labview 6.01, can I run
> this application on another machine that has labview 5?
>
> In the development center we use Labview 6.01, in the testcenter we
> use l
abview 5.
>
> Additionally, in the development center we use a unix version of
> Labview and in the testcenter a Windows version.

Can I use labview 7.1 run time in windows 98?

I am going on update a too old test system. I use labview 7.1,but I find I can't install labview 7.1 runtime in windows 98.
so should I use labview 6.1 instead of it?
Sonic
Diffrent Strokes for Different Folks

Why cnt you update both ?!
- Partha
LabVIEW - Wires that catch bugs!

When running labview's test executive I recieve runtime error

When running labview's test ( Measurement & Automation Explorer) executive I recieve runtime error ms vc++
win95 labview6.0
<<<<>>>>
Mensaje publicado mediante http://noticias.ipbusiness.com,
las news a través de web.

Hello,
There are any number of possible causes to this problem. Which version of Test Executive are you using? Have you upgraded your Test Executive recently? The latest version is 5.1.1. If you have changed anything about Test Executive on your computer recently, I recommend you perform a mass compile of all your VI libraries, as having different versions of the VIs on your system could often result in the "Call to Step XYZ Failed" errors. Also, are you using any DAQ or Analysis VIs in your steps? We have seen problems where the use of DAQ or Analysis VIs in the sequence can cause intermittent "Call to Step...Failed" errors. There are some KnowledgeBase entries on our website that discuss this problem. Are you using the Test Executive in the VI environment, or
as an executable? Again, there are some problems with using Test Executive as an executable that result in these errors, and there are also KnowledgeBase entries that discuss these problems.
If you have a pared-down application that demonstrates the problem, feel free to send me your VIs and your .seq file and I will try to reproduce the problem.
Alternatively, I would suggest you visit www.ni.com/teststand to learn about TestStand, our state-of-the-art Test Sequencing software that completely outperforms Test Executive. It is very easy to use and much more powerful, and we have a top-notch support team available dedicated exclusively to supporting TestStand. As you are probably aware, we are no longer developing Test Executive, and instead are concentrating our efforts on making TestStand the penultimate solution for all our customers' test sequencing needs.
I appreciate your patience on this issue. Please let me know if I can offer further assistance.
Have a pleasant weeken
d.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Run Labview 6.0 and Labview 8.2 on same machine

I need to do updating for an old PXI system that is running Labview 6.0, Win95/98.
My current workstation has Labview 8.2 on it, can I install 6.0 on my workstation and still have 8.2 operational for other projects? Do I have to remove 8.2, install 6.0 and reinstall 8.2 to get things to path and work properly?
Thanks,

Multiple version of LabVIEW can be installed on machine and they will not interfere with each other. Each version gets installed in its own directory under the main "National Instruments" directory.
The one problem you may have is drivers. LabVIEW 6.0 is several years old now and the drivers that support LabVIEW 8.2 may not support LabVIEW 6.0. DAQmx (any version) is one that does not support LabVIEW 6.0. You'll have to install the "Traditional DAQ".
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Computer running LabView loses time

Running LabView VI on HP Brio pc
Computer clock loses time non-linearly
e.g. after 24 hours lost 5 mins, after 36
lost 20mins. Time stamped log file is therefore wrong.
Happens with both Win95 or Win98 OS but worse on Win95.
The VI is reading data from instruments on serial port
and also a GPIB interface. Very slow
logging though (1 reading/min over many days).
Does this look like a hardware or software issue? Has anyone ever experienced this?
Help appreciated

Mine does too - and I can loose an hour in a day! I posted it on
a microsoft newsgroup and they explained that it was my problem,
my application was too cpu bound to service the time interupt
requests. There is no need to reset the time, just reboot. Windows
it seems only reads the time from the BIOS once at startup.
Call it a feature...?
I call it a bug!
"Mark Hanning-Lee" wrote in message news:[email protected]...
> GP wrote:
> >
> > Running LabView VI on HP Brio pc
> > Computer clock loses time non-linearly
> > e.g. after 24 hours lost 5 mins, after 36
> > lost 20mins. Time stamped log file is therefore wrong.
> > Happens with both Win95 or Win98 OS but worse on Win95.
> > The VI is reading data from instruments on serial port
> > and also a GPIB interface. Very slow
> > logging though (1 reading/min over many days).
> > Does this look like a hardware or software issue? Has anyone ever
> > experienced this?
>
> A general points:
>
> Win98 tends to be worse at this than other OS; not just a LabVIEW issue.
> My Win98 PC used to lose minutes per day; my Win2000 PC loses only a few
> ms per day.
>
> Make SURE that every loop in your code has a Wait or Wait until next ms
> Multiple. That frees the CPU.
>
> If a problem gets worse with time, see whether your memory usage is
> growing with time.
> If so, look for Build Array that is running in a loop, causing a large
> array to grow without limits.
>
> Also make sure there is a Close function for every Open.
> Make sure that you aren't opening & closing inside a loop; correct
> behavior is to Open before a loop, Read and/or Write inside the loop, &
> Close at the end.
> That's true for serial i/o, for VISA, and for GPIB.
>
> Lastly, if you are now using classic GPIB & serial functions, consider
> switching to VISA. Or vice versa!
>
> In general, you can keep the clock sync'd by running the free Dimension
> 4 software from www.thinkman.com . That sets the PC clock at regular
> intervals so it stays more or less on time.
> (But I'd be reluctant to do that when the program is running; might mess
> up loop timing.)
>
> Mark

How many computers can I install labview on?

I have two automated tests that I would like to run at the same time on separate computers.
Increased productivity and the whole 9 yards.
Can I legally install Lab view on both computers and run them at the same time?
Or is it only 1 copy of Labveiw can be running at a given time?
How are the licenses set up? I am running Labview 8 on a basic liscense.

I think that LV 8.0 can be installed on 2 or 3 machines (one might be a home system) but if you are developing a test system you should consider building your system into a stand alone executable which should be able to run royalty free on many machines under the runtime engine. Building and distributing applications is not hard in LV. I would check the licence agreement that came with your version of labview to be safe.
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Can I run Labview 4.1 on Win95?

Similar Messages

Maybe you are looking for