Delay in starting a LabView 10 executable with mapped drives present in Windows 7.

[Rgenaway]

I am running windows 7 on a peer to peer network without internet access with a LabView version 10 executable.  The executable accesses mapped folders on the network and works fine after it's up and running.  The problem is the time it takes to start the executable when the mapped drives are present.  It takes about 65 seconds to start and in this time, windows displays the "not responding" message.  But it always starts.  If the mapped drives are disconnected, the executable starts within 5 seconds.  The same executable running on windows XP with the same mapped drives does not have this issue.  Any ideas?

[ie.aleja · Accepted solution]

Hello Rgenaway,

Probably this is merely a Windows Issue than a LabVIEW issue. The difference between the time it takes to start when the drives are present and not present could be caused by the time the application and the drives need to connect and start communicating.

[wired]

I've had delayed startup issues in 7 with LabVIEW apps as well.  Try modifiying your <ApplicationName>.exe.config file according to the following Microsoft article.  You may need to create this file and put it in the same folder as your .EXE file.

See the example at the end of the article.  This is a simple thing to try and see if it helps.

http://support.microsoft.com/kb/936707