>>I'm not sure of all the dependencies, Bruce. In checking the wscript.exe, it doesn't reference any of the three files listed above nor wshom.ocx. Obviously, however, there's some purpose to these files. I'll take a SWAG, however...I'll guess that even without wscript.exe, you could still utilize the WSH from within another application like VFP. The wscript.exe would be used strictly for processing the VBScript and JScript files, while the others would handle the interface with the object from other programs.
>>
>>If this speculation is correct, it would mean that you could simply delete the wscript.exe and cscript.exe applications, yet maintain the use of the WSH from within VFP.
>
>You may be right, that something like this is done in the SHS. I know absolutely zero about the Shell Scrap object, but perhaps it can be done there.
>
>When you examine the rather lengthy Life Stages code, about the first thing you see is an attempt to run WScript on a renamed VBS. I know this failed here because we did not have that available - however, there was much more code after that, perhaps a "Plan B" which did something like you suggest. I printed off a text copy, but it's full of gibberish (much of it intentional to confuse the reader, perhaps) and hard to follow, 16 pages in length.

Sounds nasty. I just renamed wscript.exe and tested from within VFP. Worked fine. I didn't bother with renaming cscript.exe because that's strictly for console applications. My guess, at least based on this rather superficial evidence, is that my SWAG is correct. Apparently, once the WSH is installed, deleting the wscript/cscript files only impacts the ability to run the various script file types and not the functionality of the WSH from VFP, VB, etc.

I anyone wants to take this further in testing this, please be my guest. I think we'd all appreciate hearing the results, however.