5-2
When a workstation boots from a System Image located on its own disk, it is said to boot locally or from a local disk. When you apply power to a workstation, the bootstrap ROM searches for a file named
<Sys>Syslmage.sys. It searches disks in a predetermined order, depending on the workstation model, and loads the first occurrence of
<Sys>Syslmage.sys containing a valid System Image file. At that point, the disk containing the System Image loaded by the bootstrap ROM becomes the system volume and is known as [Sys}.
If no disk on the workstation contains a bootable System Image, the bootstrap ROM attempts to boot from the server. The following procedure describes the workstation bootstrap sequence. These steps are illustrated in Figure 5-1.
1. The bootstrap ROM searches for the operating system. Disk devices are searched in the following order:
a. Local floppy drives, starting with [(O), then [(1), and so on b. Local hard disks, starting with [dO}, then [dl}, and so on c. The [Sys} volume on the server
2. The bootstrap ROM loads the operating system into memory and transfers control of the workstation to the operating system. Param-eters in the operating system configuration file are implemented at this time.
3. The system initialization sequence is executed.
See Section 9, "Installing System Services," for information about system initialization, and Section 16, "Configuring Workstation Operating Systems," for information about the operating system configuration file.
Bootstrapping
Pawerup workstation
Load operoting
system
Reod Config.sys
Execute Syslnit.jcl
No Bootstrop from server (see next poge)
Start SignOn program
Figure 5-1. Workstation Bootstrap Sequence
502.5-10
eTOS System Administration Guide
5-4
(Cont. from prevo page)
Load operating
system
Read WsNNN>
Config.sys
Execute WsNNN>
Syslnit.jcl No
Read Ws>Config.sys
Execute Ws>Syslnit.jcl
Bootstrap foils
Read Config.sys
Start SignOn program
502.5-1b
Figure 5-1. Workstation Bootstrap Sequence Page 2 of 2
Bootstrapping
Bootstrapping a Workstation From a Server
The following workstation configurations bootstrap from a System Image located on the server:
• Cluster workstations without disks
• Cluster LFS workstations with disks initialized for data storage only (that is, not containing an operating system file)
If the bootstrap ROM does not find the System Image on a local device, it searches for it on the server. To locate the correct System Image, the bootstrap ROM searches for a file named as follows:
[SysJ<Sys>WsNNN>Syslmage.sys
where NNN is a three-digit workstation number, as listed in Table 5-1 and described below.
When a workstation boots from WsNNN>Syslmage.sys, a matching operating system configuration file (WsNNN>Config.sys) and system initialization file (WsNNN>Syslnit.jcl) are executed if they exist. See the flow chart in Figure 5-1 for the exact sequence.
Workstation Type Numbers
The workstation type number (NNN) is derived from the following:
• A processor number etched onto the bootstrap ROM
• The devices detected by the bootstrap ROM while it attempts to bootstrap locally
Table 5-1 lists workstation type numbers. The bootstrap ROM uses the workstation type number (NNN) to locate the correct operating system on the server. For example, the bootstrap ROM on a diskless B26 workstation searches for [SysJ<Sys>Ws252 >Syslmage. sys on the server.
eTOS System Administration Guide
5-6
Table 5-1. Workstation Type Numbers
Workstation
Number (NNN) Processor File System
125 827 Hard disk
126 827 Floppy disk only
127 827 Diskless
200 824 Diskless
210 838* and 386 NGEN* Hard disk
211 838* and 386 NGEN* Floppy drive only
212 838* and 386 NGEN* Diskless
213 Series 5000 Hard disk
219 Series 2000 Diskless
220 839 and Series 386i Hard disk
230 Series 286i Hard disk
231 Series 286i Floppy drive only
240 828, 286 NGEN Hard disk
838*, and 386 NGEN*
241 828, 286 NGEN Floppy drive only
838*, and 386 NGEN*
242 828, 286 NGEN Diskless
838*, and 386 NGEN*
250 826 and 186 NGEN Hard disk
251 826 and 186 NGEN Floppy drive only
252 826, CWS, and Diskless
186 NGEN
*800t ROM versions 3.2 and higher boot from 210,211, or 212; versions lower than 3.2 boot from 240, 241, or 242. The boot ROM version is displayed on the 800tstrap menu; see MUsing the Bootstrap Menu," later in this section.
Bootstrapping
Using the Bootstrap Menu
You can force a cluster workstation to boot from the server rather than from its own disk. You can also bootstrap a workstation type number that is not recognized by the bootstrap ROM. To do so, you manually initiate the bootstrap sequence from the Bootstrap menu. The Bootstrap menu varies slightly among different workstation models. A representa-tive Bootstrap menu is pictured in Figure 5-2, and a procedure for using it is included later in this section.
The bootstrap ROM version number is displayed above the Bootstrap menu. The menu options appear as single characters below the version number. Several commonly used options are described in this section.
See your diagnostics hardware documentation for information about the other menu items.
V3.2 B,D,L,M,P, T:
502.5-2
Figure 5-2. Bootstrap Menu
CTOS System Administration Guide
To bootstrap a workstation using a specific workstation number, follow these steps:
CAUTION
The following procedure interrupts applications that are currently running on the system and may cause you to lose data. Therefore, always exit applications before bootstrapping.
1. To invoke the Bootstrap menu (see Figure 5-2), hold down the space bar while you turn on or reset the workstation.
2. Release the space bar when the Bootstrap menu appears.
3. Type T (either uppercase or lowercase).
4. Type the workstation number, for example, 240.
5. Press RETURN.
6. TypeB.
Note: Other options on the Bootstrap menu are most often used by hardware development engineers to debug bootstrap ROM programs. If you need more information about bootstrap ROMs, see the appropriate technical reference or hardware diagnostics manual.
Indirect Bootstrapping
5-8
If your server is a protected-mode workstation or an SRP, you do not need to store multiple copies of the same System Image in different files.
Instead, [Sys]<Sys>WsNNN>SysImage.sys can contain the file specifica-tion of the actual System Image file.
For example, when you install the eTOS II operating systems, the file named [Sys]<Sys> Ws240>SysImage.sys contains only the following file specification:
[Sys]<Sys>pClstrLfs. img
That is the name of the file containing the protected-mode cluster LFS operating system.
Bootstrapping
Workstation Hardware IDs
On workstations equipped with appropriate hardware, you can assign a hardware ID number (HwNNN) and use it instead of a workstation type number (W sNNN) in the following file specifications:
[Sys]<Sys>HwNNN >Config.sys [Sys]<Sys>HwNNN>Syslnit.jcl
where NNN is the hardware ID assigned to the workstation.
After a workstation bootstraps from the server, the operating system reads the workstation's hardware ID. If the files listed above exist for that hardware ID, they take precedence over the corresponding workstation type number files. When you use this method, you do not need to use the Bootstrap menu to set up unique configurations for workstations that boot from the server.
You assign hardware IDs with the Write Hardware ID command. See the CTOS Executive Reference Manual for information about that command.
SignOn Display
The text displayed on the SignOn screen, with the exception of the SignOn form, is contained in a text file named [Sys]<Sys>SignOn.txt.
You can edit the SignOn text file to display a message that is appropriate for your environment.
In addition, you can create customized SignOn text files for cluster workstations that boot from server. Such files must be located in [Sys]<Sys> on the server and are named as follows:
[Sys]<Sys> WsNNN >SignOn.txt
where NNN is the three-digit workstation type number. If that file does not exist for a particular workstation number, the following file is used:
[Sys]<Sys>Ws>SignOn.txt
Ifneither WsNNN>SignOn.txt nor Ws>SignOn.txt exists, SignOn.txt is displayed.
eTOS System Administration Guide