The Microsoft Setup Basic Language

| iMatix home page
| Libero home page | Libero documentation
| << | < | > | >>

Libero
Version 2.32

The Microsoft Setup Basic Language

Overview

What Is Setup Basic?: Setup Basic is the Scripting language used and pushed by Microsoft for MS Windows 3.x setup procedures. It is identical to the MS-Test Basic language, version 1.0.
Portability: Zero. Unless you are heavily into MS-Test.
Pros and Cons: Pros: standard for setup procedures, easily available. Cons: you have to be an experienced Windows developer, and have other visual development tools, such as dialog editors, to use it.
How To Get It: It is part of the Windows SDK.
Libero Supports: MS Setup BASIC / Test Basic 1.0.

Working With Microsoft Setup Basic

Schema: lrschema.mst.
Program model: main .mst program, run using _mssetup.exe driver.
Good for: Win 3.x setup programs, as alternative to writing complex logic directly into program code.
Files used/made: own work in myprog.mst; generates include file mydialog.inc.
Module functions: Static Sub module_function_name ()
Private functions: Sub private_function_name Static (...)
Naming style: any except -style=cobol.
Limits: standard Libero limits. All tables are defined dynamically at runtime.

Example of code

Code fragments:

'****************   MODULE FUNCTION NAME   *****************

Static Sub module_function_name ()

End Sub

Sub private_function_name Static (argument,...)
    the_next_event = ok_event
    raise_exception (error_event)
}

Notes

This schema is still in a beta state; I've not used it in any real program. However, if I ever have to write a setup script in this language, this is the way to go.

When I started writing a setup program for 'Libero for Windows', I got hold of the Microsoft Setup Toolkit, and discovered the joys of writing a setup script. The language is the cut-down Basic that was used in the MS Test product: TestBasic version 1.0. I call this almost-language MST. At least, unlike Visual Basic, MST supports an include statement. So, the MST schema puts the generated code into an .inc file.

The setup toolkit documentation suggests that you draw a flowchart of the various stages of your install procedure, then code this into an MST program. Hmm. :-( I hate flowcharts, for one thing. For another, I have a much simpler and useful technique up my sleeve, so some quick work on a schema, and 'wallop!'. MST, please meet Mr. Turing.

As it happens, I then decided that I did not want to use an MST setup program, did not want to start designing dialog boxes and resources. Now the Libero for Windows installation package is a .zip file that you expand into the directory of your choice, full stop. Still, the MST schema is there and it works, barring the odd lazy bug.