The Avanti Configuration Utility generates a text file containing a script that defines the desired hardware configuration for a virtual Alpha system.  This script can be viewed and modified using any text editor.  Manually modifying a script may introduce errors that prevent the emulator from launching.  Existing configuration scripts are automatically parsed for manual modifications and errors by the Configuration Utility when opened.

A configuration file must contain exactly one top-level control block and may be nested no more than 32 levels. Files larger than 16 MiB or containing embedded NUL bytes are rejected. These checks apply to hand-edited files as well as files opened in the Configuration Utility.

Manually Modified Condifuration Files

There are cases where manually modifying a configuration file is required.  Adding a 5-port serial card is one example.  Entering debug options under the guidance of a Migration Specialties support specialist is another.  The Configuration Utility detects configuration files that have been manually modified with options that are not accessible through the GUI when the file is open and issue a warning message.  Using the Configuration Utility to update manually modified configurations is not advised.

Updating Avanti Path Names

When moving an Avanti configuration file to a new location, the path names embedded in the file may change.  Using the Configuration Utility to update each path reference in the configuration file can be a tedious process.  The path names can be easily updated in one operation by opening the configuration file using a text utility such as Notepad and employing its Replace function.  Manual modification such as path name changes are not flagged by the Configuration Utility GUI.