Table of Contents
Advertisement
Set Environment to Bug/Operating System
ENV [;[D]]
The ENV command allows you to interactively view/configure all
Bug operational parameters that are kept in Battery Backed Up
RAM (BBRAM), also known as Non-Volatile RAM (NVRAM). The
operational parameters are saved in NVRAM and used whenever
power is lost.
Any time the Bug uses a parameter from NVRAM, the NVRAM
contents are first tested by checksum to insure the integrity of the
NVRAM contents. In the instance of BBRAM checksum failure,
certain default values are assumed as stated below.
The bug operational parameters (which are kept in NVRAM) are
not initialized automatically on power up/warm reset. It is up to
the Bug user to invoke the ENV command. Once the ENV
command is invoked and executed without error, Bug default
and/or user parameters are loaded into NVRAM along with
checksum data. If any of the operational parameters have been
modified, these new parameters will not be in effect until a
reset/powerup condition.
If the ENV command is invoked with no options on the command
line, you are prompted to configure all operational parameters. If
the ENV command is invoked with the option D, ROM defaults
will be loaded into NVRAM.
The 177Bug ENV parameter display is shown in the following
example:
177-Bug>
Bug or System environment [B/S] = S?
Field Service Menu Enable [Y/N] = Y?
Remote Start Method Switch [G/M/B/N] = B?
Probe System for Supported I/O Controllers [Y/N] = Y?
Negate VMEbus SYSFAIL* Always [Y/N] = N?
Local SCSI Bus Reset on Debugger Startup [Y/N] = N?
Local SCSI Bus Negotiations Type [A/S/N]
Ignore CFGA Block on a Hard Disk Boot [Y/N]
Set Environment to Bug/Operating System
env
= A?
= Y?
D-3
D
Advertisement
Table of Contents
