Table of Contents
Advertisement
The EISA Configuration Utility need only be run if there is a PCI to EISA
bridge and EISA devices on the system. Manufacturing will have run ECU
prior to shipping the system, so running it again may not be necessary.
The EISA Configuration Utility comes on a floppy, has online help, and
configures the EISA bus. The arc_enable environment variable must be
on and in effect for ECU to run. There are two versions of the utility, one
that runs on graphics terminals, and another that runs on character cell
terminals. Both versions are on the floppy; the console determines what
kind of terminal is on the system and chooses the correct ECU version to
run. Example 7-6 shows how to run ECU.
Place the EISA Configuration Utility floppy in the floppy drive.
Power on the system or initialize.
1
After self-test, if the EISA bus is not configured, the console displays
2
the message shown here.
Use the set command to turn on the arc_enable environment vari-
3
able.
Initialize the system to make the set command take effect.
4
After self-test enter runecu, the console command to invoke ECU.
5
The console loads ECU from the floppy drive and passes control to it.
If ECU is not run and OpenVMS is on the system and booted, OpenVMS
prints the following message:
%SYSTEM-I-NOCONFIGDATA, IRQ Configuration data for EISA
slot xxx was not found, please run the ECU and reboot.
OpenVMS continues to boot after this message and will run without the
EISA devices as system resources.
If ECU is not run and UNIX is on the system and booted, no information
messages are printed. The operating system boots but does not use any
EISA resources.
Diagnostics and Utilities 7-19
Advertisement
Table of Contents
