#-----------------------------------------------------------------------------
#   For MTS Guest SYSTEM
#-----------------------------------------------------------------------------

#   For D6.0, but not for D6.0A you need to create a
#   3380 disk image before you start using something
#   similar to:
#      dasdinit -z -a mts600.dsk 3380-1 MTS600
    
#   In general the Hercules device configuration needs to
#   match or at least be a subset of the D6.0 version
#   of TABLES as described in the following list from
#   the D6.0-NEWSYS.txt writeup:
#
#       Device Type     Address            Device name
#       -----------     ---------          -----------
#   
#       3287            0000               PTR1
#       3270            0001-0007          DS01-DS07
#       3270 (in D5.0)  0009               CON1
#       1052 (in D6.0A) 0009               CON1
#   
#       2540R           000C               RDR1
#       2540P           000D               PCH1
#       1403            000E               PTR2
#   
#       3270            001F               CON2
#   
#       3287            0100               PTR3
#       3270            0101-011F          DS21-DS3F
#       3420            0180-018F          T900-T90F
#   
#       3330            0200-020F          D100-D10F
#       3350            0220-022F          D200-D20F
#       3370            0240-024F          D300-D30F
#       3380            0260-026F          D400-D40F
#   
#       3420            0C70               T920
#   
#       9335            0D00-0D03          D500-D503
#       9335            0E00-0E03          D600-D603

#   Devices 018B through 018F and 0C70 (T90B to T90F and T920) are defined
#   as 9TP (3420) tape drives in TABLES and so could be defined here

#   Disk(s)

#   Shadow files (sf=) won't be used until the Hercules command "sf+"
#   is issued, unless the shadow file already exists or the base and
#   shadow files are read-only in which case a new shadow file will
#   be created.

# D6.0 and D6.0A of MTS support single density (3380-1), but not
# double density (3380-2) or triple density (3380-3), 3380 disks.

# New 3380 disks need to be initialized using dasdinit's -a option
# so that the alternate tracks are included. For example:
#    dasdinit -z -a mts600.dsk 3380-1 MTS600
#    dasdinit -z -a E:\Emulation\VMESA\disks\mts\mtu000.dsk 3380-1 MTU000

0260    3380   disks/mts/mts600.dsk ro sf=disks/mts/shadows/mts600_*.dsk # D400
0261    3380   disks/mts/mtu000.dsk ro sf=disks/mts/shadows/mtu000_*.dsk # D400

# Devices 0200-020F (D100-D10F), 0220-022F (D200-D20F),
# 0240-024F (D300-D30F) and 0261-026F (D401-D40F) are
# defined as 3330, 3350, 3370, and 3380 disks and so
# copuld be defined here.

# Devices 0D00-0D03 (D500-D503) and 0E00-0E03 (D600-D603) are defined
# as 9335 disks in the D6.0 and D6.0A TABLES, but there are bugs in
# the D6.0 and D6.0A 9335 support, so these devices can't be used.

# END
#-----------------------------------------------------------------------------