|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 DFS Tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 DFS Tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - download
Length: 1399 (0x577)
Types: HLP, TextFile
Names: »LOADER.HLP«
└─⟦24d56d853⟧ Bits:30000744 8mm tape, Rational 1000, DFS, D_12_6_5 SEQ293
└─ ⟦this⟧ »LOADER.HLP«
└─⟦9031b0687⟧ Bits:30000407 8mm tape, Rational 1000, DFS, D_12_7_3
└─ ⟦this⟧ »LOADER.HLP«
LOADER The LOADER program is used to boot the R1000. Depending on the BOOT/CRASH/MAINTENANCE options the LOADER will either prompt for a configuration to boot or simply use the STANDARD configuration. The LOADER will first intialize the processor by invoking various experiments. Next the microcode loader for the machine (SBUSULOAD for the Series 100 and DBUSULOAD for the Series 200). The microcode loader will reload the control store, register file, and dispatch RAMs as needed from the microcode image specifed by the configuration file. The LOADER will proceed to start the R1000 by invoking experiments. At this stage the R1000 will begin executing microcode to further initialize the processor and eventually become idle. The LOADER will begin to load subsystems into the R1000 by extracting the names of MLOAD files from the configuration specified and interpreting the directions contained in them. Once all of the subsystems have been loaded into R1000 memory the LOADER will calculate the transitive closure of the subsystems, build instructions for the kernel elaborator and send those to the R1000 as well. Finally the LOADER will send a start message to the R1000. The R1000 will place a constant task name on the run queue and thus begin elaborating the environment. Once done the LOADER invokes the monitor program which performs various tasks while the R1000 is running.