Sluggish operation of LABVIEW 7.1

[patelbaroda]

1) Regarding continously adding a string or array. Yes, I may be generating a log report after each test on product. I will remove that and see. Couple of more things I want to clear up based on the *.pdf.

2) Third party (IOTech) had supported me good. They are also working on this problem since last two months. They changed me the lower version board with higher version and fixed their memory leak problems (thats what they says) but still when I start the application Labview shows 32-40K in task manager. After an hour or so, it shows 190,000 KB or so. So definately it is going to hang.

They released new version of third party software support based on the investigations.

Thanks.

[patelbaroda]

It says that it is LABVIEW 7.1 full development system. I am not getting memory usage option enabled. (Its grayed out).

[Jarrod_S.]

Regarding your installation problems:

You might consider trying to install something else other than the LabVIEW 7.1 development system to see if this is a general issue with the Windows Installer somehow, or if this problem is indeed restricted to LabVIEW 7.1.

One thing you might try to install would be the LabVIEW 7.1 Run-Time engine. This is available free for download from here. Do you get any errors or warnings when installing this?

[patelbaroda]

I am able to install programs which uses Installshield or their own installer. But including LABVIEW runtime engine, which uses Windows installer are not getting installed. I am getting error of service could not be accessed or windows is running in safe mode. I searched for services and found that Windows installer is running. I also updated the installer with new available installer configuration for XP2. But still installation error. How to find window is running is safe mode or not?

Thanks.

[Jarrod_S.]

The only thing I can think of is that you'd see some kind of warning when you reboot your computer, saying that Windows is booting into Safe Mode. If you're not prompted at bootup, I wouldn't think you'd be in safe mode. You might search msdn.com for this error.