Windows Script Host Engines in Windows 98
When Microsoft released Windows 98, it introduced native operating system automation through the Windows Script Host (WSH 1.0). Powered by Microsoft's Active Scripting architecture, Windows 98 shipped with two built-in scripting engines out of the box: Visual Basic Scripting Edition (VBScript) and JScript. This integration allowed scripts that were previously confined to web browsers like Internet Explorer to execute directly within the desktop environment for system management and batch operations.
Visual Basic Scripting Edition (VBScript)
VBScript was Microsoft’s lightweight, component-based subset of
Visual Basic. Embedded via the vbscript.dll library, the
engine was designed to be familiar to Visual Basic programmers and
offered native access to Windows objects through Component Object Model
(COM) interfaces.
In Windows 98, VBScript files typically used the .vbs
extension. System administrators leveraged this engine to automate
routine maintenance, modify registry keys, manage files, and interact
with network shares. Because VBScript was tightly integrated with the
Windows shell, it quickly became the standard scripting language for
administrative scripting on the platform.
JScript
JScript was Microsoft’s proprietary implementation of the ECMAScript
standard (commonly referred to as JavaScript), supplied via
jscript.dll. Originally developed for client-side web
scripting in Internet Explorer, WSH enabled JScript to operate as a
general-purpose, stand-alone scripting language running directly within
the operating system.
JScript files ran with the .js file extension. The
language provided a C-style syntax and object-oriented features, making
it accessible to web developers transitioning into local desktop and
network automation tasks.
The Active Scripting Architecture
Both VBScript and JScript functioned through the Microsoft Active Scripting technology. Rather than tying automation to a single language syntax, WSH acted as a language-independent host. When a script was invoked, WSH identified the file extension, loaded the corresponding script engine DLL into memory, and exposed system interfaces through the WSH object model.
Execution was handled by two native host executables:
- WSCRIPT.EXE: A Windows-based host that displayed output and user prompts using graphical dialog boxes.
- CSCRIPT.EXE: A command-line host that directed output and error messages straight to the MS-DOS console, making it ideal for command prompt scripts and batch jobs.
While third-party engines—such as ActivePerl, ActivePython, or Rexx—could be installed and registered with the Active Scripting architecture, VBScript and JScript remained the only two web scripting engines natively pre-installed in Windows 98.