CPU usage of Labview for 16 bit windows

[cincidude]

I am using a Labview version 4 meant for 16 bit windows on Windows 95 and it runs fine each time I run it. But the application crashes frequently when I make a prolonged use of it, for e.g. set it to run on a scheduler. I suspect the problem is due to exhaustive CPU usage by this Labview version. I verified this using the 'System monitor' utility in windows 95. The launch of this labview itself shows a CPU usage of 100% without any other application running. I was wondering whether this is specific to Labview version 4, or any other user might be able to suggest what might be the reason for this.

[Labviewguru]

You may have just made a programming error.

Have you considered upgrading to LabVIEW 6.1? I believe it will only cost you $395 to do so, and is more than worth it.

If you post your code (a screenshot of the diagram would be best in this case), we may be able to help you locate some cause of this CPU hogging. This may not be the case, but needs to be eliminated as a cause before anything else can be done.

Try using the VI Profiler in LabVIEW as well.

Good luck.

[cincidude]

I am attaching my Labview code in version 4. I cannot upgrade to Labview 6 since I have some drivers for the data acqausition system which I am controlling through Labview, which are for 16-bit windows.

Could you also elaborate about the VI profiler that you have mentioned?

[JeanPierre]

LabVIEW 4 (16bit for Win3.1) is a 32bit application that passes thru a needle hole to run on the 16bit kernel of the 32bit OS Windows 95. Don't wonder why it hogs your system. Run the 32bit version of LabVIEW 4 or live with that issue.

[Rolf]

"Jean-Pierre Drolet" wrote in message
news:50650000000500000066970000-1027480788000@exchange.ni.com...
> LabVIEW 4 (16bit for Win3.1) is a 32bit application that passes thru a
> needle hole to run on the 16bit kernel of the 32bit OS Windows 95.
> Don't wonder why it hogs your system. Run the 32bit version of LabVIEW
> 4 or live with that issue.

It is actually worse. LabVIEW is a 32bit application doing exhaustive 16bit
<> 32bit conversion through the Watcom 32bit extender to run on the 16bit
system which again is emulated through a thunking layer on an "almost" 32bit
system which Windows 95 is.
NI never really supported this although as long as you only use LabVIEW
internal stuff without IO drivers such as DAQ, GPIB, DDE and under LabVIEW 4
possib
ly TCP/IP it should work fine.

Rolf