DataMuseum.dk

top - download

    Length: 4096 (0x1000)
    Types: HLP, TextFile
    Names: »INSTALL.HLP«

└─⟦b4205821b⟧ Bits:30000743 8mm tape, Rational 1000, DFS, D_12_7_3 SEQ288
    └─ ⟦this⟧ »INSTALL.HLP« 
└─⟦b434774df⟧ Bits:30000528 8mm tape, Rational 1000, DFS, D_12_6_5
    └─ ⟦this⟧ »INSTALL.HLP« 
└─⟦bc1274df5⟧ Bits:30000750 8mm tape, Rational 1000, DFS backup from PAM's R1000
    └─ ⟦this⟧ »INSTALL.HLP« 

TextFile

INSTALL

The INSTALL program is for use on a model 200 processor only. It combines the 
features of RECOVERY and UPDATE_EEPROM to install a new DFS release tape
on a machine and update the EEPROMs with the newly installed firmware. It will
not touch the environment space of the disk system. Upon invoking it, the
program will query the operator with a series of questions then proceed with
the installation and updating. A sample of dialogue follows. The comments are
notes only and do not appear in a real session.

CLI> push install

Testing EEPROMS...[OK]   -- INSTALL automatically checks the EEPROMS
Tape drive unit number : 0 -- INSTALL prompts for number of tape drive

IOP configurations are as follows : -- INSTALL now prompts for kind of machine
   0 = native model 200
   1 = model 300C ( COPROCESSOR )
   2 = model 300S ( STANDALONE )
Enter processor configuration code :1
Enter unit number of disk to format/build/scan : 0 -- INSTALL promots for disk 
HDA : KEYSTONE:/DEV/RXD0H   -- this / following only reported on co-processors

The server name for logical disk 0 is : KEYSTONE:/DEV/RXD0H
The disk geometry (in decimal) is :
Cylinders => 418
   Tracks => 27
  Sectors => 66

Writing bad block information.        -- at this point, INSTALL proceeds
Writing boot label.                   -- without any further interaction
Writing DFS label.
Constructing free list.
Writing free list.
Allocating and initializing directory.
Creating predefined files.
KERNEL_0.M200
KERNEL_1.M200
KERNEL_2.M200
FS_0.M200
FS_1.M200
FS_2.M200
PROGRAM_0.M200
PROGRAM_1.M200
PROGRAM_2.M200
DFS_BOOTSTRAP.M200
ERROR_LOG
Reading -> DFS_BOOTSTRAP.M200      -- INSTALL echos filenames as they are
Reading -> KERNEL_0.M200           -- loaded into the DFS space
.
.
.
Reading -> 580616.SEG
Reading -> 675849.SEG
Elapsed time is 00:21:14
DFS FILES HAVE BEEN RELOADED       -- INSTALL announces 
Initializing diagnostic file system ... [OK]
DFS RECOVERY COMPLETE
Verifying data file for SELFTEST.HEX  -- INSTALL now starts to update eeproms
File EEPROM checksum is verified.
File EERPOM revision = 900118
File EERPOM location = 21
Verifying data file for BOOT.HEX
File EEPROM checksum is verified.
File EERPOM revision = 900118
File EERPOM location = 19
Verifying data file for UTILITIES.HEX
File EEPROM checksum is verified.
File EERPOM revision = 900118
File EERPOM location = 17
Verifying data file for NETWORK.HEX
File EEPROM checksum is verified.
File EERPOM revision = 900118
File EERPOM location = 15


Programming EEPROM with data from file SELFTEST.HEX
File EEPROM checksum is verified.
File EERPOM revision = 900118
File EERPOM location = 21
Programming EEPROM, write cycle takes about 4 minutes maximum
EEPROM matched file, nothing changed   -- normally this is NOT the case

Programming EEPROM with data from file BOOT.HEX
File EEPROM checksum is verified.
File EERPOM revision = 900118
File EERPOM location = 19
Programming EEPROM, write cycle takes about 4 minutes maximum
EEPROM matched file, nothing changed

Programming EEPROM with data from file UTILITIES.HEX
File EEPROM checksum is verified.
File EERPOM revision = 900118
File EERPOM location = 17
Programming EEPROM, write cycle takes about 4 minutes maximum
EEPROM matched file, nothing changed

Programming EEPROM with data from file NETWORK.HEX
File EEPROM checksum is verified.
File EERPOM revision = 900118
File EERPOM location = 15
Programming EEPROM, write cycle takes about 4 minutes maximum
EEPROM matched file, nothing changed

EEPROMS REPROGRAMMED
INSTALLATION SUCCESSFUL!
Verify B/C/M settings and IOP ENVIRONMENT settings on reboot -- reminder 
BREAK/0 SIMULATED -- CRASHING IOP FOR REBOOT        -- INSTALL crashes the IOP
-- INSTALL is complete now verify B/C/M setings and CONFIGURATION
Dumping IOC RAM to server ................................ -- COPROCESSOR only
R1000 System Crash detected at PC=0001AB04, error code = 08
Operator console break key

Restarting R1000-300 Co-Processor January 22nd, 1990 at 14:01:17
Change BOOT/CRASH/MAINTENANCE options [N] ?  -- «nul»