>>If you make the WSH available,
>
>A big if, huh? I can't yet depend on it already being there, and if I distribute it, I have to extract it, copy it and register it. What does that?
>

There is a self-extracting executable available from the MS Web site that will install WSH 2.0 in all but a few non-English-language Win95 versions from the MS Scripting site in my sig. It's freely redistributable. Makes its own sauce. I write a RunOnce registry key in case it forces a reboot to restart the install, and delete the key if it doesn't force a reboot. It's safe to install even if WSH is already in place. Admittedly, for my installs, I write the outer scripting with IS Pro and check to see if things like DCOM, WSH, ADSI, the MDAC_TYP and the like which are available as redistributable self-running executables before I begin the real install processing. I install from CD, and the autorun fires the WSH install automagically before I reach a point where I need it. Once it's in place, I can use both the scripting capabilities and the COM objects like Wscript.Network, Wscript.Shell, Scripting.FileSystemObject and VBScript.RegExp in my apps, and inside my IS Pro script.

>>OTOH, it's a lot of work, would need lots of testing and debugging, and by the time you finished getting it to work, the cost of a high-end installer would not seem unreasonable...
>
>Yup...