>I get an error about "UNC paths are not valid" (or very similar) in a DOS BAT I created to deploy to multi-OS, with multi-versions of multi-vfp apps, via SMS and switches.
>
>However, the UNC paths and installs all work fine, so the error is wrong. It's not a large problem since the installs work fine, but I'm curious why this error exists, and if it's fixable.
>
>I can run the BAT silently (eventually), but for a while I want to observe the BAT processing, with live installs to users in BETA mode. The first thing users see is the error message, and they get concerned. Even the Admins are bothered at first, until I explain about it.
>
>Anyone seen this bad DOS error, know if it can be removed somehow?

Aha, problem isolated much better. It turns out this error only shows on NT4/Win2K, but not XP. (maybe different DOS versions?) Since almost all users will be on XP within the next 6 months, I'm not gonna worry too much, just let the non-XP people know the UNC error is meaningless.