I appreciate that you've taken the time to read my question and respond. But, that's incorrect. It is very possible that a location could be accessible at a later time, both during the execution of the script ("net use ...") or at a later time if the results are saved in the environment or...

I've attached a BAT test file which demonstrates that CMD works, and produces correct results, with arbitrary paths, whether the drive/path/file exists or not. Executing the same BAT with TCC fails with loud, difficult to suppress, error messages. Any ideas/suggestions how to fix this?

WAD = works as designed? Not to be argumentative, but I've tested this and CMD _doesn't_ error _or_ "mysteriously fail". It correctly parses the string whether the drive exists or not. I have test calls with arbitrary paths that prove it. And so, the question still stands... I can parse an...

In writing a function to parse arbitrary paths, I'm encountering an error for paths with drives which are unavailable (such as a path on a disconnected network drive). An example of the function is: :FN setlocal set p=%~dp1 ... goto :EOF All variations on "%~dp1" and trying to use an...