| Anchor | ||||
|---|---|---|---|---|
|
...
The default VAX CPU mode is determined by the specific CHARON-VAX product license.
ace_mode
| Parameter | Type | Values |
|---|---|
| ace_mode | |
| Type | Boolean |
| Value | true or false. |
This statement enables ACE mode if the CHARON-VAX license permits it. If this statement is omitted from the CHARON-VAX configuration file and the license permits it, "true" is the default. Otherwise "false" is the default. For test purposes the ACE mechanism can be disabled with:
...
RAM
The CHARON-VAX memory subsystem is permanently loaded and has the logical name "ram".
size
| Parameter | size |
|---|---|
| Type | |
| Numeric | size | Numeric
| Value | Size of emulated memory in MB. |
Example:
set ram size = 512 |
The amount of memory is capped at a maximum, defined in the CHARON license key. If the host system cannot allocate enough memory to map the requested emulated memory, CHARON-VAX generates an error message in the log file and reduces its effective memory size.
...
TOY
CHARON-VAX maintains its time and date via the "toy" (time-of-year) component. In order to preserve time and date while a virtual system is not running, the TOY component the TOY component uses a binary file on the host system to store date and time relevant data. The name of the file is specified by the “container” option of the "toy" component.
container
| Parameter | container |
|---|---|
| Type | Description |
| container | Text string |
| Value | Specifies a name of a file in which CHARON-VAX preserves time and date during its “offline” period. This file also keeps some console parameters (such as default boot device). By default it is left unspecified.
|
it is recommended to specify the full path to the file
Example:
set toy container="/path/my_virtual_system.dat" |
The CHARON-VAX time zone may be different from that of the host system. Correct CHARON time relies on the correctness of the host system time to calculate the duration of any CHARON “offline” periods. (i.e. while virtual system is not running). Every time CHARON comes on line it calculates a Delta time (the system time is used if there is no TOY file). Therefore, if the host system time is changed while CHARON is not running, the CHARON time may be incorrect when CHARON is restarted and the CHARON time must be set manually.
...
The System Flash ROM file conserves specific parameters between reboots.
...
container
| Parameter | container |
|---|---|
| Type |
...
...
| Text string | |
| Value | Specifies the name of a file in which CHARON-VAX stores an intermediate state of its Flash ROM. This state includes, for example, most of the console parameters. |
|---|
...
By default it is left unspecified.
|
set rom container=”"/path/my_virtual_system.rom”rom" |
EEPROM
container
| Parameter | container | |
|---|---|---|
| Type | Value | |
| container | Text string | |
| Value | A string specifying a file name to store content of EEPROM. Example:
This command enables EEPROM parameters (e.g., default boot drive) to be automatically saved to a specified file. The EEPROM file is created in the directory in which CHARON-VAX starts and is created or overwritten each time any parameter relevant to EEPROM content is changed.
|
Example:
set eeprom container=”/path/my_virtual_system.rom” |
...
Those models boot automatically if correct boot flags are set (and saved in the VAX console files) using the following command:
halt
| Parameter | Description | |
|---|---|---|
| halt | ||
| Type | Text string | |
| Value | Determines whether the MicroVAX3100, VAXstation 4000, VAX6310 and VAX 4000 boot automatically if correct boot flags are set (and saved in the VAX console files). The value is:
Example:
|
| Div | ||
|---|---|---|
| ||
|
| Warning |
|---|
| Please check that the "toy container" and "rom container" parameters are specified in the configuration file to store the boot flags. |
...
MicroVAX II, MicroVAX 3600/3900 and VAXserver 3600/3900 The ROM of the MicroVAX II, MicroVAX 3600, MicroVAX 3900, VAXserver 3600 and VAXserver 3900 does not allow the VAX console to accept the command setting "auto-boot". Instead, automatic boot on startup can be specified in the CHARON-VAX configuration file as follows:
bdr boot
ParametersParameter Type Value bdr boot Type Text string Value Determines whether the MicroVAX II, MicroVAX 3600, MicroVAX 3900, VAXserver 3600 and VAXserver 3900 boot automatically if correct boot flags are set (and saved in the VAX console files).
The value is:
"auto"
Example:
set bdr boot=auto
| Parameter | Type | Value |
|---|---|---|
| bdr boot | ||
| Type | Text string | |
| Value | Determines whether the MicroVAX II, MicroVAX 3600, MicroVAX 3900, VAXserver 3600 and VAXserver 3900 boot automatically if correct boot flags are set (and saved in the VAX console files). The value is:
Example:
|
| Warning |
|---|
| Please check that the "toy container" and "rom container" parameters are specified in the configuration file to store the boot flags. |
Back to Table of Contents
| Div | |
|---|---|
|
...
| |
|
...
VAX66x0
xmi boot
| Parameter | xmi boot | |
|---|---|---|
| Type | Text string | |
| Value | Determines whether the CHARON VAX66x0 startup procedure stops at the ">>>" prompt after self-tests. The values are:
Example:
The value |
| Warning |
|---|
| Please check that the "toy container" and "rom container" parameters are specified in the configuration file to store the boot flags. |
...