Les Hammer wrote: > I see the problem too - running LabVIEW 7 on Windows XP, while > starting by clicking on the vi icon. It normally only happens when > the computer is very busy. That is, just after a reboot when all the > services are being started. It's acting as if LV is expecting a > response in say 5 seconds, the computer is busy so it doesn't get the > response - puts up the "file not found" message, 2 seconds later it > finds the file and displays it. If I close LabVIEW and try it again, > it works fine - because the computer isn't busy any more. So the > question is - where is the timeout value being set?
I think this is a Windows shell "feature". I see the same message sometimes under W2K when opening Word documents which are located on the network. Sometimes Word aborts after a while and sometimes it still opens the file after the error dialog has been dismissed. Rolf K
