Page Comparison

#
# Copyright (C) 1999-2019 2018 STROMASYS
# All rights reserved.
#
# The software contained on this media is proprietary to and embodies the
# the confidential technology of STROMASYS. Possession, use, duplication, or
# or dissemination of the software and media is authorized only pursuant to a
# to a valid written license from STROMASYS.
#
#============================================================================
#
# Sample configuration file for VAX 6000 Model 310.
#
#----------------------------------------------------------------------------

set session hw_model = VAX_6310

#============================================================================
#
# Choose a name for the instance, if needed, to differentiate it among other
# instances running on the same host.
#
#----------------------------------------------------------------------------

include configuration_name.icfg

#============================================================================
#
# Use the following commands to disable the rotating LOG files and enable
# a single LOG file. Select either append or overwrite (for each time the
# instance starts) and specify desired log path and file name.
#
#----------------------------------------------------------------------------

set session log_method = append
#set session log_method = overwrite
#set session log = VAX_6310.log

#
# It is possible to reduce the size of the log file using filtering
# possibilities:
#
# 1) Based on message type (info, warning, error)
# 2) Based on repeatetive messages removing.
#
# You can specify which type of messages should be logged using option
# 'log_show_messages' which is a string option containing mentioned above
# message types delimited by comma. Default is "all" which means to log
# all existing message types.
#
# You can specify that repeatetive messages should be filtered out using
# 'log_repeat_filter' "on"/"off" option. Default value is "off"
#

# The same as default "all"
set session log_show_messages="info, warning, error"

# Show only information and error messages
#set session log_show_messages="info, error"

# Show only error messages
#set session log_show_messages="error"

# Filter repeatetive messages out
#set session log_repeat_filter="on"

#
# The following lines tell ============================================================================
#
# The following line tells the emulator where to preserve NVRAM content.
# It will keep The TOY file maintains the current time of the emulated VAX (when you do it is not
# run the emulatorrunning) and other console parameters (such as default boot device).
#
# Both files must be enabled to correctly preserve the saved state of the console settings.
#
#----------------------------------------------------------------------------

#set toy container = "charon.dat"
#set eeprom container = "charon.rom"

#============================================================================
#
# Disable or enable dynamic instruction translation by the cpu (ACE). The use
# of DIT may be also prohibited by the license. If not specified (i.e. when
# both lines remain commented out) the DIT is enabled as soon as the license
# allows to do so and is disabled otherwise ...
#
#----------------------------------------------------------------------------

#set cpu ace_mode=false
#set cpu ace_mode=true

#============================================================================
#
# Specify the size of RAM (default 512MB32MB). Remember Note that the dongle license might
# license might limit the maximum amount of memory.
#
set ram size=32#----------------------------------------------------------------------------

#set ram size = 64
#set ram size = 128
#set ram size = 256
#set ram size = 512

#
# Now assign console built-in serial line. Currently the
# emulator offers three possible ways using serial lines. First
# of them is connection to COM ports (via physical_serial_line).
# The second is to attach a third party terminal emulator
# (virtual_serial_line). And the third one is to connect to MOXA
# NPort 5210 box ports (via np5210_serial_line).
#
# Once desired way of connection is chosen load the interface
# like OPA0 which is expected by built-in console controller.
#

# MOXA NPort 5210 box connection
#load np5210_serial_line/chserial OPA0
#set OPA0 ip="xxx.xxx.xxx.xxx" rs_port=n

# Physical COM port connection
#load physical_serial_line/chserial OPA0 line="COM1:"

#
# Virtual serial line connection listening for the TCP/IP port
# number 10003 on the host system. It is possible to connect to
# this port from any appropriate application (standard terminal,
# user written terminal, etc...).
#
#load virtual_serial_line/chserial OPA0 port=10003

#
# Virtual serial line connection listening for the TCP/IP port
# number 10003 on the host system. Specified program is started
# automatically.
#
load virtual_serial_line/chserial OPA0
#set OPA0 port=10003 application="opa0.ht"
set OPA0 port=10003 application="putty.exe -load OPA0"
#set OPA0 port=10003 application="c:\kea\user\opa0.ktc"

# load DWMBB XMI-to-VAXBI adapter into slot 14 of the XMI
load DWMBB XBA xmi_node_id=14============================================================================
#
# Select the connection method for the console serial line OPA0.
#
#----------------------------------------------------------------------------

#load physical_serial_line OPA0 line = "\\.\COM1"
#load virtual_serial_line OPA0 port = 10003
#load virtual_serial_line OPA0 port = 10003 application = "opa0.ht"
load virtual_serial_line OPA0 port = 10003 application = "putty -load OPA0 -P 10003"

#----------------------------------------------------------------------------
#
# Uncomment to allow 'F6' to terminate the running emulator. Closing console
# satellite application may also be used for that.
#
#----------------------------------------------------------------------------

#set OPA0 stop_on = "F6"
#set OPA0 stop_on = "Application"
#set OPA0 stop_on = "F6, Application"

#============================================================================
#
# DWMBB XMI VAXBI Adapter
#
# Slots 1 - 15 (1 - F) of the VAXBI are able to handle I/O adapters.
#
#----------------------------------------------------------------------------

load KDB50 MSCP disk controller into slot 1 of the VAX BI
load KDB50 PUA DWMBB XBA xmi_node_id = 14

#============================================================================
#
# KDB50 VAXBI Disk Controller
#
#----------------------------------------------------------------------------

#load KDB50 DUA vax_bi_node_id = 1

#
# Attach unit 0 of the PUA controller to disk image (.dsk or .vdisk);
# VMS would see it as "DUA0:"
#
#set PUA ============================================================================
#
# Uncomment to connect the emulator's DUA0 to the disk image.
#
#----------------------------------------------------------------------------

#set DUA container[0] = "..\vdisk\vmssys.vdisk"#
# Attach unit 1 of the PUA controller to physical disk drive (N to be
# replaced with decimal number); VMS would see it as "DUA1:"
#set PUA <file-name>.vdisk"

#============================================================================
#
# Uncomment to connect the emulator's DUA1 to the physical disk drive.
#
#----------------------------------------------------------------------------

#set DUA container[1] = "\\.\PhysicalDriveN"
#set DUA container[1] = "\\.\PhysicalDriveNA:"

#

# ...

#
# Attach unit 9 of the PUA controller to CDROM drive (0 might to be
# replaced with another decimal number, if necessary); VMS would see
# it as "DUA9:"
#set PUA ============================================================================
#
# Uncomment to connect the emulator's DUA9 to host's CD/DVD-ROM drive or
# to an .ISO file (CD/DVD image).
#
#----------------------------------------------------------------------------

#set DUA container[9] = "<file-name>.iso"
#set DUA container[9] = "\\.\CdRomN"

#
# Attach unit 10 of the PUA controller to floppy disk drive ('A' to be
# replaced with 'B', if necessary); VMS would see it as "DUA10:"
#set PUA container[10]="\\.\A:"

# ...

# load DEBNI Ethernet Controller into slot 2 of the VAXBI
load DEBNI/DEMNA

#============================================================================
#
# Load optional DEBNI VAXBI Ethernet Adapter (ETA). Allocate slot 2 of VAXBI.
#
# TIP: You need to uncomment the "load DEBNI ..." line and one of the
# "load packet_port ..." lines below to attach the ETA to host NIC (or not)
#
#----------------------------------------------------------------------------

#load DEBNI ETA vax_bi_node_id = 2 interface = ETA0

# connect the ETA Ethernet controller to host network interfacechoose this one to leave ETA unconnected
#load packet_port ETA0 interface = "(disabled)"

# choose this one to connect ETA to host's NIC (by its connection name)
#load packet_port /chnetwrk ETA0 interface = "connection:<connection-name>"#set ETA interface=ETA0# Load VAXBI to UNIBUS adapter

#============================================================================
#
# DWBUA VAXBI UNIBUS Adapter
#
#----------------------------------------------------------------------------

load DWBUA UBA vax_bi_node_id = 14

# Load TMSCP tape to have the tape instead of non-implemented TBK70
load TUK50 MUA#
# Attach MUA controller to tape image (.mtd or .vtape); VMS would see
# it as "MUA0:"
#
set ============================================================================
#
# TUK50 UNIBUS Tape Controller
#
#----------------------------------------------------------------------------

#load TUK50 MUA

#============================================================================
#
# Uncomment to connect the emulator's MUA0 to the physical tape drive or
# to a .VTAPE file (tape image).
#
#----------------------------------------------------------------------------

#set MUA container[0] = "mua0.mtd"#
# Attach MUA controller to physical tape drive (N to be replaced with
# decimal number); VMS would see it as "MUA0:"
#
<file-name>.vtape"
#set MUA container[0] = "\\.\TapeN"# ...

# this is the end of the configuration file #################################