You might be able to use the environment variable $ComSpec ... I see it here on my Win7 machine, and If you can, it returns (for me):
c:\Windows\system32\cmd.exe Of course there's "the shellcommand", but that just returns "command.com" or "cmd.exe" depending on your flavor of Windows. > The correct way to determine if you have permissions to execute shell > scripts then is probably to find out if you have execute access to > %WINDIR%\system32\cmd.exe. Unfortunately without access to the *shell*, we can't use "attrib" the equivalent, so that leaves launching apps or using a custom-built DLL (or maybe executing VBScript). Monte, if the user doesn't have shell access do you think they also wouldn't be able to execute a VBScript? Because if they *can* do VBScript, I'm sure there's a VBS way to find out shell access permissons. Ken Ray Sons of Thunder Software, Inc. Email: [email protected] Web Site: http://www.sonsothunder.com/ _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
