System Speed Affected by LabeVIEW Project Being Open

[xlAutomation]

Hi again, folks,

LabVIEW 8.2 is kicking my butt. In addition to block diagram edits being slow, even my mouse and keyboard responsiveness is being affected when the project and block diagram for a VI is open. This is most noticable with the mouse: clicks are often missed, and when panning the mouse across the screen, the speed varies dramatically as (i assume) mouse movement interrupts are being missed. This problem goes away as soon as I close LabVIEW and rebooting doesn't seem to help. It doesn't seem to matter if the mouse if actually over the block diagram or not. In fact, to start this posting, I had to click several times on the "Post this question" button (LabVIEW is open at the moment). My computer is a workhorse with good memory (2GB), good processor P4 3GHZ, and very good graphics card (NVidia GeForce 7600GT on dual monitors). OS is XP SP2.

Any recommendations?

Michael Hampson

[altenbach]

How's the CPU use and memory footprint of your various programs when the problem occurs (In task mananger).

Does it only occur with your old VIs or even if you open LabVIEW freshly and just create a small new VI?

What antivirus are you using?

Do you run any kind of firewall software or have the windows firewall enabled? Is LabVIEW allowed to use the network?

[xlAutomation]

Hello,

The CPU use stays very low (0 - 5%) when just moving around and clicking things with the mouse (all the while the mouse is being erratic). CPU usage goes up to 30-50% if I actually perform an edit on the block diagram; for the 3 to 7 seconds I get an hourglass, the usage is in this area, and then goes back to normal.

The paging file usage stays aroung 640MB. Physical memory use is around 2G with 1.3G available.

I am using BitDefender antivirus. I have installed it recently, but have had no other problems related to it.

I appreciate your help and suggestions.

Michael

[xlAutomation]

I have no firewall software, and Windows firewall is off.

Michael

[xlAutomation]

I will check to see if the problem is there with a new or small vi. I haven't check that.