User manual

176
# adapter_instance - number of adapter instance to use if more
# than one adapter is installed in the host system (0 is default);
# adapter_options - options to be passed to adapter (no options are
# defined for the moment - empty string is default).
#
# Note that CHAPI_QBUS can be used both with QBUS and UNIBUS systems.
# In case of QBUS system this is full-functuional BUS adapter, while in
# case of UNIBUS system it works like QBUS<-->UNIBUS converter with the
# only restriction that bus memory locations aren't translated.
#
#load chapi chapi_qbus dll=chapi_qbus.dll trace_level=0
#set chapi_qbus adapter_dll=chapi_hw
#set chapi_qbus adapter_name=bci
#set chapi_qbus adapter_instance=0
#set chapi_qbus adapter_options=""
# ... mentioned above configuration is equal to the following one ...
#load chapi chapi_qbus dll=chapi_qbus.dll trace_level=0
#--------------------------------------------------------------------
# CHAPI_UNIBUS mapped to TLC BCI-2004 bus adapter.
# Just uncomment the lines below to test this kind of CHAPI device.
#
# All options specified for the bus adapter below can be omitted,
# in this case specified values will be used by default.
#
# Options description:
# adapter_dll - the name of DLL library where to take adapter
# implementation from (chapi_hw is default);
# adapter_name - name of the adapter within the DLL library
# (bci is default);
# adapter_instance - number of adapter instance to use if more
# than one adapter is installed in the host system (0 is default);
# adapter_options - options to be passed to adapter (no options are
# defined for the moment - empty string is default).
#
# Note that CHAPI_UNIBUS can be used both with QBUS and UNIBUS systems.
# In case of UNIBUS system this is full-functuional BUS adapter, while in
# case of QBUS system it works like QBUS<-->UNIBUS converter but only
# for non-DMA devices which don't use bus memory locations.
#
#load chapi chapi_unibus dll=chapi_unibus.dll trace_level=0
#set chapi_unibus adapter_dll=chapi_hw
#set chapi_unibus adapter_name=bci
#set chapi_unibus adapter_instance=0
#set chapi_unibus adapter_options=""
# ... mentioned above configuration is equal to the following one ...
#load chapi chapi_unibus dll=chapi_unibus.dll trace_level=0
#--------------------------------------------------------------------
# CHAPI RL01/RL02 disks.
#
# Just uncomment the proper lines below to test this kind of CHAPI
# device with particular configuration.
#
# Options description:
# disk_dll - the name of DLL library to take disk container implementation
# from (chapi_storage is default);
# disk_cfg - the name of disk container implementation within the
# specified DLL library to use (file is default and only available
# for the moment);
# disk_param - the name of container to connect (only disk image is