Search the Community
Showing results for tags 'paths'.
Found 2 results
-
Hi, I'm writing a script to copy a number of files from UNC paths. That bit is pretty simple. However, my users think my script has crashed, which it hasn't, it's only because the UNC path doesn't exist and one of the AutoIt functions is waiting. This is true of FileExists(), FileCopy(), DriveStatus(), etc. Is there a function to check if a UNC path exists that doesn't pause in this fashion? The only way round it, that I can think of at the moment, is to spawn another process and pre-check all the UNC paths and write if they exist in a text file. Then rather than use FileExists(), I use my text file instead. Anybody got a better idea? Thanks, James
-
Normally one uses ShellExecute("c:\foo\bar.txt"). But there are internal uses too. For example, ShellExecute("winword") launches Microsoft Word. However, ShellExecute("foobar") launches an error message. Is there a way to accept only "legal" values? In other words, is the word "winword" registered somewhere and can be verified before it's thrown into ShellExecute? Thanks!
