Long wait for SAVE dialog, windows

[battler.]

---

smercurio_fc wrote:

I would also caution you against concluding that 2009 is "still very buggy" based solely on one person's comments. One person's experience does not make a product "very buggy". 

---

I base the statement on my own experiences. 

1. I have had several unrecoverable crashes in recent days which I have posted about.

2. I could not get app builder to work, which I also posted about.

3. The properties of the 3D graphs still do not work with SP1 - in several posts.

Just look at the list of bug fixes for 2009:

http://zone.ni.com/devzone/cda/tut/p/id/10829

[battler.]

I have a similar situation where programs hang upon calling a file dialog; this is at work where we run several network drives.  The hanging occurs even when I'm not saving to the network drives.

I do suggest you try disconnect your network connections to at least rule that out.

[smercurio_fc]

---

battler. wrote:
 

Just look at the list of bug fixes for 2009:

http://zone.ni.com/devzone/cda/tut/p/id/10829

---

I've seen that. Given the size and complexity of LabVIEW that's not a very long list. As I indicated, LV 2009 may be very buggy for you, but that doesn't mean it's a very buggy application for everybody else. 

[Pcorcs]

Realizing that many users have many unique experiences, and that everyone is entitled to their opinion...it is my opinion that we ought return to original subject introduced by this thread:

Jed,

We you able to implement any of the performance monitoring tools in Windows 7? Any results? 

Also, was this computer upgraded from XP or Vista  to 7? Or, was is a new system pre-loaded with 7? Custom build?

Just curious on progress. Let us know!

Thanks, 

[Jed_Davidow]

(Sorry, had a family emergency and had to run out of town for a couple days.  Will have to do it again this weekend.)

Very strange.  When I boot the OS and run notepad, Excel, etc, there is no problem- all the Open/Save As dialogs come up quickly.

Then I runLV 2009 SP1 x32 and the dialog takes 60 seconds from the labview menu.

Back to notepad, no problem.

LV 8.6.1: SLOW

Excel: No problem.

OK.  Killing all network drives (3):

LV 8.6.1:  No problem, but I had not restarted it.  After restarting LV 8.6.1, it is slow again.

LV 2009 SP1: Slow.

Firefox: No problem

OK.  It's not the network access.

[Jed_Davidow]

Ran a performance monitor report with LV trying to open the dialog.  Can't see anything funny (no network drives).

OK.  Now I tried diabling the network completely (still no mapped drives).  As soon as I do, the dialog comes up.  So, testing further, I have the problem when the network is on, no problem when off.

So it IS network, but only LV.  (double checked several programs)

How can I deal with that?

[battler.]

We have lots of ppl at work complaining about performance of apps and PCs when it's really just the network.

Have a word with your IT people. Otherwise;

Solution = Do your development offline (disconnected from the network).

Message Edited by battler. on 04-30-2010 03:47 AM

[GerdW]

Hi Jed,

from my experience:

I had a LV installation, where my User directory was located on a network drive. Hence LabVIEW was also using this network drive for it's temp and user specific data. This lead to the same problem of having stalls on file dialog opening.

Redirecting LV to local folders did help...

[GregFreeman]

---

battler. wrote:

We have lots of ppl at work complaining about performance of apps and PCs when it's really just the network.

Have a word with your IT people. Otherwise;

Solution = Do your development offline (disconnected from the network).

Message Edited by battler. on 04-30-2010 03:47 AM

---

This happens a lot with Microsoft office. I believe it is because if a (mapped) network drive is disconnected, it tries looking for it. It takes a while to timeout when not found, and in the mean time you get stuck waiting. I'm not saying this is the problem LabVIEW is having...but it is one possibility. Then again, the OP said he had no network drives. hmmmmmmm

[smercurio_fc]

I would suggest temporarily disabling some of the NI services that get installed with LabVIEW. It's also possible one of those could be causing an issue. Though I don't see how, you never know. Look for those starting with "NI", but there are a couple that don't, like the "Lookout Citadel Server". On most installs about half of those services don't even need to be running.