Download AMOS System Operator`s Guide

Page 4
Section 5 - Chapter 5
5.3.2Adding a SCSI Disk to Your System
FOR SYSTEMS THAT BOOT FROM A SCSI DRIVE:
If the new drive you’re adding is not going to be your system boot disk (the drive your
computer boots from), you have the following options:
1.If the new disk drive is the samesize and bitmap, and has the same number of
logical units as the system boot disk, then you don’t need to make a new disk
driver for it. The same "DSK" device name can be used, but the next disk drive’s
logical units must follow (in sequence) the numbers of the previous system disk
logicals. For example, if the first system drive contains logical units DSK0: through
DSK4:, then the additional system drive must be defined as DSK5: through DSK9:.
With the release of the AMOS 2.3 operating system, three essential initialization
commands have been greatly simplified: DEVTBL.LIT, BITMAP.LIT, and
MOUNT.LIT. Now your entire boot drive and all its logical units can be defined
with these simple statements: DEVTBL DSK, BITMAP DSK, and MOUNT DSK:.
(The colon is required with the MOUNT command only). If your system contains
more than one System Drive (that is, two or more of the same type drive, and
each is defined as a "DSK" device) then you need to define the additional drive(s)
on the DEVTBL line like this: DEVTBL DSK1-n. n is the last logical unit of the last
"DSK" drive, or more simply, the total number of "DSK" logicals minus 1.
(Counting starts from logical unit zero, but DSK0: never needs to be defined.)
You can also use this format for any subsystem SCSI drive(s) for which you’ve
created the appropriate device driver. For more information on the use of these
enhanced commands see the corresponding pages of the System Commands
Reference Manual and the System Operator’s Guide to the System Initialization
Command File.
To use the DEVTBL Dev1-n command format for multiple physical drives, the
drives must be next to each other on the SCSI bus— they must have consecutive
SCSI IDs.
2.If your new disk drive is a different size or has a different number of logical units,
you need to use the FIXLOG program to configure a driver for it. As with other
subsystem devices, you need to give the new driver a three-letter name that is
different from "DSK." For more information on using the FIXLOG program see the
FIXLOG command reference sheet in your System Commands Reference Manual.
Once the new disk driver has been created you need to follow these steps before you
can access the new disk drive:
System Operator’s Guide, Rev. 03