Table of Contents
Advertisement
Document ECG026/0498
W
P
HITE
APER
. .
Diagram 7: Remote ROM Flash Flow
. .
. .
. .
. .
. .
. .
Steps:
. .
. .
Ø Run RMSetup on server/admin box.
. .
. .
Ø schedule remote Flash job via std. network app
. .
. .
Ø Target runs job (Rflash.bat)
. .
. .
Ø WinFlash.exe
. .
. .
Ø Report status via registry
. .
. .
Ø Shutdown.exe
. .
. .
. .
. .
. .
Admin. sends command
. .
information & files to FLASH
. .
remote client.
. .
. .
. .
. .
. .
. .
Fail-safe Boot Block ROM:
. .
. .
. .
The Fail-safe Boot Block ROM allows for system recovery in the unlikely event of a ROM flash
. .
failure; for example, if a power failure occurs during a ROM upgrade. The Boot Block is a flash-
. .
. .
protected section of the ROM that checks to validate the system ROM each time power to the
. .
system is turned on.
. .
. .
If the system ROM is valid, the system starts normally.
. .
. .
. .
If the system ROM fails the validation check, the Fail-safe Boot Block ROM provides enough
. .
support to start the system from a ROMPaq diskette, which can program the system ROM
. .
. .
with a valid image.
. .
. .
As there is no video or hard drive support from the Boot Block ROM, the keyboard lights are used
. .
to communicate information. When the Boot Block detects an invalid system ROM, the system
. .
. .
sounds a series of beeps (one long and three short) and flashes the three keyboard lights. The
. .
following table lists the various keyboard light combinations, as well as the meaning and action
. .
. .
associated with each combination.
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
30
. .
.
Workstation
running Windows NT 4.0
CLIENT
WinFlash
ROM image
Encrypted information
Password
Admin
Console
WinFlash
Status via
Rflash.bat
NT
Registry
Report
Shutdown
Remote Package Components
Advertisement
Table of Contents
