Actually, I'm not sure if the scripting language itself has to support enumerated constants. Here is the comment in one of the sample VB Scripts.

' - there should be an accompanying file named 'sample2.wsf'
' It is placed in the same directory as this file during
' product installation. This file is responsible for setting
' up the Windows Script Host environment and loading the
' VmCOM type library, thereby enabling this script to
' reference symbolic constants such as vmExecutionState_On
'
' - in a command line window, type:
' cscript //nologo sample2.wsf


Apparently, by running this script first (code included in my first message), all the symbolic constants are available with the called scripting environment.

I'm not sure whether there is a way to call KiXtart in this way from WSH so these constants are available there. It might just be easier to stick with VBScript?

NMM