>Hi George,
> Thanks very much for the help. I'm concerned about using Windows Scripting Host since I can't be sure it will be installed. The first suggestion, using DRIVETYPE() will work. Only one concern: is it possible that some network drives might be mapped to a logical name other than a single letter, such as "W$"? If so, the algorithm would fail.

Chaim,

First, you can always check the registry for the presence of VBScript.RegExp ProgID during a post setup executable and if necessary install it. That's what I do.

Second, if a network drive isn't mapped you might check ANETRESOURCES() to see if that'll give you what you want. Ed Rauh's NETRESOURCES programming can enumerate everything on a network. It would take some modification in order for it to do what you want.

Third, the problem with a lack of a mapping is that there's no way to tell if the user has rights to anything on the drive. That's one reason I prefer to rely on mappings. If I can't map it, there's a pretty good chance I can't use it anyway.