Specifications

EISA Configuration Utility
CFG Files
Each adapter card in the EISA system should come with a CFG file on
floppy disk. A card's CFG file contains detailed information on the card
as well as the functions that the card can perform. The CFG file tells the
ECU the possible configuration choices for the adapter card and the
system resources that the adapter card needs. System resources include
BMA(Direct Memory Access) channels,IRQ (Interrupt Request) lines,
I/O Address Ports, and memoryspace.BesureallCFG files for all cards
in the system and the CFG file for the motherboard are available before
running the ECU.
CMS File
The CMS file contains a copy of the configuration information that is
written into the system's Extended CMOS Memory. The default name
for a CMS file matches the ID of the system board that was used in the
configuration. Each CMS file should have a corresponding INF file.
SNF File
The INF file contains detailed information about a configuration such as
switch and jumper settings, software statements, connection statements,
and resource allocation. The INF file is used by the "Display/Print"
command to recall information on a saved configuration. Each INF file
should have a corresponding CMS file.
Pi Running the EISA Configuration Utility
The ECU operates on the information provided by the CFG (Configuration)
files that accompany the EISA mainboard and EISA or ISA adapter cards.
The ECU stores configuration data in a battery-backed EISA Extended
CMOS RAM. When an EISA system is powered on, the BIOS reads this
configuration information and initializes all adapter cards in the system. If
the battery runs down, the contents of CMOS RAM can be lost. You must
then either reconfigure the system or copy the configuration data to EISA
Extended CMOS RAM from a backup source.
5-5