Windows Script 5.6 Documentation
Make sure you have the Windows Script 5.6 Documentation installed
and registered in the OnScript Editor. This will enable keyword and
error help using F1.
When you run OnScript for the first time it attempts to find the
documentation and register it. To check if this succeeded, open the
OnScript Editor and switch the Workspace to the Helps tab. You
should see an entry that looks like this:
Double-clicking the entry should open the help file in a separate
If you do not have the help file on your system, then download and
install it. We have set up a link the documentation on in the
Scripting Downloads section of this
site. The installation will ask for a path to store the help file
(the default is fine). It will then copy and register it and create
a Start menu shortcut.
The last step is to tell OnScript about the new help file. You can
do this by manually adding a new entry to the Helps tab (New Help
command on the shortcut menu) and by associating the Help links of
the various script file types with the help file on the Options
dialog (Tools menu).
However, it is easier to accomplish this by using the “Register
Script Help Files” command you can find in the Tools menu. This will
configure all required settings in OnScript.
To test your configuration, open a script file, select a keyword or
place the cursor in a keyword and press F1. A separate window will
show the help file opened on the appropriate page!
See the "Get an error description from online help" topic above on how to jump to the description of errors that occur in your
Microsoft Windows Script Debugger
The OnScript Editor will let you manage breakpoints and jump into
the debugger when your script hits a breakpoint or if an error
occurs. But in order to get some real debugging done OnScript alone
is not enough - you will have to install a script debugger such as
the Microsoft Windows Script Debugger. This is free tool and there
is a download link in the Scripting
Downloads section of this site. Installation is easy and
A while ago the
Microsoft TechNet Scripting Guys published a great article on
how to debug scripts using the Script Debugger, so make sure you
check it out:
Bugs Check in but They Don’t Check Out - September 2004
"Just because we might never be able to get rid of computer bugs
for good, that doesn’t mean we can’t track down and exterminate
individual bugs, particularly those lurking within our scripts."