The information in this article applies to:
SUMMARYWhen Windows Script Host finds an error in a script, it displays an error message instead of loading the Windows Scripting Debugger and displaying the error in the text file. MORE INFORMATIONIn Windows 2000, the Windows Scripting Debugger is not started by default when a script error is detected. You can debug the error by setting a temporary switch for the Windows Script Host. At a command prompt, type the following line wscript bad_script_name.xxx //Xwhere bad_script_name.xxx is the script file name and //X is a switch that starts the debugger. Typing wscript /? displays the syntax for Wscript.exe and the available options. Additional query words:
Keywords : kbtool kbui |
Last Reviewed: December 30, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |