The INTIAL_LOAD Record in Advanced Revelation 2.11
Published By | Date | Version | Knowledge Level | Keywords |
---|---|---|---|---|
Revelation Technologies | 23 APR 1992 | 2.1X | INTERMEDIATE | INTIAL_LOAD, PROGRAM, PROGRAMS, STACK, REVBOOT, SYSTEM |
Changes to the boot logic in Advanced Revelation 2.11 reduce the time needed to log in. These changes include:
- Eliminating the SYSOBJ file.
- Eliminating the SECONDARY.LOAD record from the VERBS file.
- Creating in the SYSTEM file the INITIAL_LOAD record.
- Improving the way the DOS file REVBOOT is used.
You can now decide which programs are automatically loaded at boot time and which are never removed from the program stack by changing the INITIAL_LOAD record.
The INITIAL_LOAD Record
The INITIAL_LOAD record is stored in the SYSTEM file. You can edit the record by entering this command at TCL:
EDIT SYSTEM INITIAL_LOAD
Caution! Exercise caution when editing INITIAL_LOAD. Changes to INITIAL_LOAD can corrupt your system.
INITIAL_LOAD is a list of all programs that are placed on the program stack when you log into Advanced Revelation. You can add or delete items from INITIAL_LOAD as you like. However, you must not change the lines marked DO NOT CHANGE.
The program stack is maintained internally as two data structures. The first is a dynamic array of program names. The second is a dimensioned array of object code. When you boot Advanced Revelation, the dynamic array, as determined by INITIAL_LOAD, is loaded from REVBOOT. Additionally, the object code for the first four programs in INITIAL_LOAD, RTP57, RTP57A, RTP27, and STDIOERR are read into memory. All other object code is loaded when the programs are first executed.
Primary Load
Programs that are part of primary load never unload their object code. That is, once the object code is read from disk, it is never flushed from memory. The last program in INITIAL_LOAD that is loaded as part of primary load is RTP2.
Secondary Load
Secondary load programs (those following RTP2) maintain their position in the dynamic array. Their object code can be flushed from memory if necessary.
Other Programs
All other programs are loaded and flushed as they execute. They stay on the stack only for the duration of their execution. When a program finishes, it is removed from the stack.
Rebuilding REVBOOT
When you change INITIAL_LOAD, you must rebuild REVBOOT using the bump process. This is because the list is saved in REVBOOT so that the boot program does not have to build the program stack in a loop. Instead, it parses the stack from REVBOOT and initializes the data structures.
To rebuild REVBOOT:
- Enter BUMP at TCL.
- Change your network driver in the bump window, from what it is to any other driver.
- Answer "Yes" when prompted to change drivers.
- Repeat steps 1 to 3 and change your network driver back to the correct driver for your network.
The process of changing network drivers will cause REVBOOT to be rebuilt. When it is rebuilt your changes to INITIAL_LOAD are incorporated.
The next time you log into Advanced Revelation your changes will take effect.