Instruction manual
Page 4-6 Chapter Four
Eagle 450 Installation and Technical Manual, Rev. 00
Display Console Boot Messages
When set to Yes, this option displays status messages on the operator terminal during booting. These
messages are equivalent to each of the front panel status codes normally displayed during booting, and
are normally only needed if you cannot see the status display.
Saving the CMOS Settings
When you are finished making changes press
ESC
. A message will appear at the bottom of the screen
asking if you wish to save any changes made. Type
Y
to save the changes in the CMOS RAM, or
N
to
abandon any changes made. After you enter your response, the system will boot using the new
parameters, if you saved them.
Important Note
If you want to boot from a physical disk device other than device ID 0, you should create a disk driver
for the selected drive ID and MONGEN it into the monitor.
You must do this if you want to be able to
MONTST using your boot monitor
. While a hardware reset will work if the monitor contains the generic
SCZ138.DVR, because it reads the drive ID from CMOS, MONTST does not look at the CMOS settings,
and so will not know which drive to boot from unless the drive ID is embedded in the driver.
MODIFYING THE INITIALIZATION FILE
The modifications you’ll need to make to the default system initialization command file for the Eagle
450 are similar to the modifications for other AMOS computers. You’ll probably want to set the number
of jobs, add programs to system memory, set up AlphaTCP networking, define terminals and printers,
and so on. You may also want to change SCSI dispatcher options, set read-ahead, or disable Super I/O
for some or all serial ports.
The name of the system initialization file for the Eagle 450 is usually AMOS32.INI (though, because of
the CMOS feature, it can have any name you want).
NEVER
change the system initialization file directly!
Always make a copy of it and modify the
copy. While the ability to change the initialization file name through CMOS can make it possible
to boot even if you invalidate the normal initialization file, it is still safer to work in a copy of the
file.
To make a copy of the system initialization file to modify and test:
1.
Log into DSK0:[1,4] and copy the file:
LOG DSK0:[1,4]
ENTER
COPY TEST.INI=AMOS32.INI
ENTER
2.
Use AlphaVUE or another text editor to edit the contents of the test file:
VUE TEST.INI
ENTER