| Anchor | TopConfigurationPage | TopConfigurationPage|||
|---|---|---|---|---|
| Anchor | ||||
|
| Include Page | ||||
|---|---|---|---|---|
|
...
| Table of Contents | ||
|---|---|---|
|
...
| Include Page | ||||
|---|---|---|---|---|
|
Creation of your own configuration file using a template
...
Note: the lines preceded by the comment sign "#" inside the configuration files will not be interpreted. You can use this sign to debug your configuration.
...
| Include Page | ||||
|---|---|---|---|---|
|
VAX model specification
The first configuration statement is the specification of the exact VAX hardware model to emulate.
...
If you create the CHARON-VAX configuration file from scratch, it must be the very first uncommented line in the configuration file.
...
| Include Page | ||||
|---|---|---|---|---|
|
Configuration name
The next configuration statement is the "Configuration name" option.
...
You can optionally uncomment this line to differentiate this CHARON-VAX instance from all others in a multi-instances environment. The configuration name can be any label that is meaningful. It is reported in the log file and is used to set the log file name for rotating log (see further: Rotatinglog(default) ).
...
| Include Page | ||||
|---|---|---|---|---|
|
Log file parameters
Execution of CHARON-VAX creates one log file or a set of log files reflecting the progress of its start-up and ongoing operation - start and end time of execution, system information, license and configuration details, warnings, reports on problems that may occur, etc. In case of possible problems either with the running CHARON-VAX or the emulated system configuration (such as the absence or malfunction of certain devices), the log file(s) is the primary source to be analyzed for troubleshooting. If it becomes necessary to contact Stromasys for support, the configuration and log files, plus the license number, will be requested to begin problem resolution.
...
|
...
| Include Page | ||||
|---|---|---|---|---|
|
TOY, ROM and EEPROM containers
...
|
...
| Include Page | ||||
|---|---|---|---|---|
|
Emulated memory (RAM) size
...
It is possible to leave the RAM line commented out. In this case the model's default RAM amount is used.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Console
Mapping to system resources
...
It is strongly recommended to uncomment this line to provide CHARON-VAX the ability to exit by pressing the "F6" key.
...
| Include Page | ||||
|---|---|---|---|---|
|
Disk subsystem
The next step is the configuration of the disk subsystem and mapping it to the system resources using the samples given in the template configuration files.
...
Follow this link for details of (T)MSCP controllers configuration.
...
| Include Page | ||||
|---|---|---|---|---|
|
SCSI controller NCR53C94
The VAX 4000 and MicroVAX 3100 have an NCR53C94 SCSI controller onboard for support of different types of SCSI devices including disks and tapes. Optionally a second controller can be added.
...
Follow this link for details of NCR53C94 SCSI controller controllers configuration.
...
| Include Page | ||||
|---|---|---|---|---|
|
Tape subsystem
Some MSCP and SCSI controllers support tape devices, however CHARON-VAX also emulates specific MSCP tape devices such as TQK50 and TUK50.
...
The first line loads a UNIBUS BI adapter "DWBUA". Configure then the "TUK50" tape controller the same way as the TQK50.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Serial Lines
...
Note that additional parameters exist for CHARON-VAX serial lines configuration, follow this link for details.
...
| Include Page | ||||
|---|---|---|---|---|
|
Networking
CHARON-VAX supports DEQNA, DESQA, DELQA, DEUNA, DELUA, DEMNA, DEBNI and PMADAA virtual network adapters.
...
Follow this link for more details of CHARON-VAX network controllers configuration.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Auto boot
...
The CHARON-VAX 6000 models have a similar configuration setting:
|
...
| Include Page | ||||
|---|---|---|---|---|
|
Host load balance for SMP systems
...
| Setting | Description | Example | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| affinity | This setting binds the running instance of the emulator CPUs to particular host CPUs. This should be used for soft partitioning host CPU resources or for isolating multiple CHARON instances on the same host from each other. By default the emulator instance allocates as many host CPUs as possible. “Affinity” overrides the default and allows explicit specification of which host CPUs will be used by the instance. Affinity does not reserve the CPU for exclusive use. |
| ||||||||
| n_of_io_cpus | Reserves host CPUs (of those specified by “affinity” parameter, if any) for use by the emulator for I/O handling. By default the emulator instance reserves one third of available host CPUs for I/O processing (round down, at least one). The “n_of_io_cpus” overrides the default by specifying the number of I/O host CPUs explicitly. |
|
...
| Include Page | ||||
|---|---|---|---|---|
|