| Anchor | ||||
|---|---|---|---|---|
|
...
| Type of mapping | Description | |
|---|---|---|
| "<file-name>.vdisk" | Mapping to the file representing a physical disk of the VAX/PDP11 system (disk image). These files can be created from scratch with "MkDisk" utility. Data and OS disks backups are transferred from the original system via tapes or network and restored into these container files. Mapping may also include the full path (recommended), for example: " C:\My disks\my_boot_disk.vdisk" | |
| "\\.\PhysicalDriveN" | Mapping to physical disk. Be careful not to destroy all the information from the disk dedicated to CHARON-VAX / CHARON-PDP by mistake!These disks must not be formatted by the host OS. | |
"\\.\PhysicalDrive(DevID =XXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)" | Mapping to physical disk by its WWID. Be careful not to destroy all the information from the disk dedicated to CHARON-VAX / CHARON-PDP by mistake!These disks must not be formatted by the host OS. DevID addresses the target physical disk by its WWID (hexadecimal 128-bit identifier assigned to the disk drive by its manufacturer/originator). Example:
| |
"\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)" | Mapping to iSCSI disks. iScsiTarget addresses the disk by its iSCSI target name. LUN specifies LUN on connected iSCSI disk. Example:
| |
| "\\.\CdRomN" | Mapping to CD-ROM device. | |
| "<file-name>.iso" | Mapping to an ISO file for reading distribution CD-ROM image. Mapping may also include the full path (recommended), for example: " C:\My disks\vms_distributive.iso" | |
| "\\.\A:" | Mapping to Floppy drive. | |
| "\\.\<N>:" | Mapping to some other type of drive, for example magneto-optical drive. |
...
Follow this link for details of (T)MSCP controllers configuration.
Back to Table of Contents
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.
...
| 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. |
|
...