Latest WSH engine compatible with NT Option Pack 4.0 ?
You should always install ste51en (or IE5) on an IIS4 server (Option Pack)
to get the latest scripting engines.
I do this on all client sites to fix bugs (memory leaks) and improve
performance.
Only trap is that there are some new reserved words in
VBScript that can
cause errors in older ASP applications but it is not very likely to happen
(only once for me).
Regards,
Ian
Senior Consultant | MSDN Regional Director
ADV E-Commerce | Windows Script FAQ
Advantage Group | http://www.windows-script.com
Quote:
> It's unlikely the a WSH install will (or ever did) break IIS. I've
installed WSH 2.0 on several
Quote:
> boxes running IIS (PWS anyway) with zero problems...
> --
> Michael Harris
> MVP Scripting
Quote:
> Needed to upgrade to latest available WSH. Then had to switch back
> to Interdev, and do some web page work, but local hosting was broke
> - no sure what did that. MS said to reinstall Option Pack, which I
> did, and I managed to get my web work out. Now I find my WSF files
> no longer execute. I take this to mean that IIS installation trounced
> my upgraded script engine. Does anyone know if I now reinstall
> latest WSH will I again break IIS ?
> --
> ______________________________________________________________________
> Lee Gillie, CCP Remove NOSPAM to E-Mail
> Online Data Processing, Inc. - 3501 N. Haven - Spokane, WA 99207-8500
