Insert the operating system CD into the local CD drive.

At the console prompt (>>>), enter the SHOW DEVICE command so you can identify the name of the CD drive (for example, DKA400:)

Enter the boot command in the following format:

BOOT -FLAGS 0,0 source-drive

Substitute the device name of the CD drive (as listed in the SHOW DEVICE display) for source-drive.

For example, if the SHOW DEVICE display lists the device name of your CD drive as DKA400, enter the following command and press Enter:

>>> BOOT -FLAGS 0,0 DKA400

At the console prompt (>>>), enter the SHOW DEVICE command and scan the devices listed in the output to determine the name of the CD drive. Look for a device listed with its hardware address, as in the last line of the following example; compare this information with that provided by the table in step 2.

>>> SHOW DEVICE

dva0.0.0.1000.0    DVA0                     RX23
dka200.2.0.5.0     DKA200                   RZ28M  1004
dka300.3.0.5.0     DKA300                   RZ29B  0016
dka400.4.0.5.0     DKA400                   RZ26L  442E
ewa0.0.0.3.0       EWA0         00-00-F8-1F-70-3D

For additional information, see the HP OpenVMS Version 8.4 for Alpha and Integrity Servers Software Product Description (SPD 82.35.xx) and the hardware manuals that you received with your Alpha computer.

At the console prompt, enter the following command, where lan-device-name is the LAN device (for example, EWA0) identified with your computer:

>>> B -FLAGS 0,0 -FILE APB_084 lan-device-name

For information about the LAN devices your system supports, see Table A-1. Ethernet device EWA0 refers to the first EW device. Subsequent devices are named EWB0, EWC0, and so on. For most systems, you can use the SHOW CONFIGURATION console command to list LAN devices available for boot. For additional information, see the hardware manuals that you received with your Alpha computer and the OpenVMS software product description (SPD). The APB file name in the previous command is the unique file name that was assigned to the APB.EXE file when it was copied from the operating system CD to the InfoServer. This file is the name of the APB program used for the initial system load (ISL) boot program.

	NOTE: Note the following about devices and computers listed in Table A-1: The console LAN device EGA0 is the Gigabit Ethernet device DEGXA. OpenVMS refers to this device as an EW device rather than an EG device. To correlate the console device names for EG and EW devices, compare the MAC address listed for each device by the console and by the LANCP SHOW CONFIGURATION commands. If you are using a DEC 3000 or 4000 series system, note the following: On DEC 3000 series systems, you can boot through the InfoServer with an Ethernet PMAD device or FDDI DEFTA device by specifying the device name as “n/ESA0”. The value for n is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. For more information, see Section A.1.2. On DEC 4000 series systems, you must specify the ISL file name in uppercase (for example, APB_084).

The InfoServer ISL program then displays the following menu:

   
 Network Initial System Load Function
 Version 1.2


  FUNCTION         FUNCTION
    ID
    1     -        Display Menu
    2     -        Help
    3     -        Choose Service
    4     -        Select Options
    5     -        Stop

 Enter a function ID value:

Respond to the prompts as follows, and press Enter after each entry:

1. Enter 3 for the function ID.

2. Enter 2 for the option ID.

3. Enter the service name (ALPHA084 is the default service name for the InfoServer hardware; for the InfoServer utility, ask your system or network manager for the service name).

A sample display follows:

 Enter a function ID value: 3
  OPTION          OPTION
    ID
    1     -       Find Services
    2     -       Enter known Service Name

 Enter an Option ID value: 2
 Enter a Known Service Name: ALPHA084

Begin the conversational boot by entering the BOOT command in the following format:

BOOT -FLAGS 0,1 [device-name]

For device-name, substitute the device name of the drive from which you want to boot. For example, if the system disk has a device name of DKA400, enter the following command and press Enter:

>>> BOOT -FLAGS 0,1 DKA400

At the SYSBOOT> prompt, enter the following command:

SYSBOOT> USE DEFAULT

The USE DEFAULT command specifies that default values should be used for all parameters.

To avoid starting all layered products on a system that is not tuned for them, possibly causing the system to hang, set the STARTUP_P1 system parameter as follows:

SYSBOOT> SET STARTUP_P1 “MIN”

Enter the following command to ensure that the operating system does not record for subsequent system reboots the STARTUP_P1 parameter change you made in step 3:

SYSBOOT> SET WRITESYSPARAMS 0

Enter the following command to continue booting:

SYSBOOT> CONTINUE

When the system finishes booting, determine which changed parameter caused the problem and reset the parameter value. If you specified the value for the parameter in the AUTOGEN parameter file MODPARAMS.DAT, fix the value in that file and run AUTOGEN. For more information, see the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.

After your system runs for at least 24 hours, run AUTOGEN in feedback mode, following the steps described in Section 7.24. Be sure to examine the AGEN$PARAMS.REPORT, as recommended. If necessary, modify system parameters as instructed in Section 7.25. If you need assistance, contact your software support representative. Once you feel confident that the problem is corrected, and AUTOGEN has been run through the SETPARAMS phase, reboot the system.

Begin the conversational boot by entering the BOOT command in the following format:

BOOT -FLAGS 0,1 [device-name]

For device-name, substitute the device name of the drive from which you want to boot. For example, if the system disk has a device name of DKA400, enter the following command and press Enter:

>>> BOOT -FLAGS 0,1 DKA400

Enter the following command at the SYSBOOT> prompt:

SYSBOOT> SET/STARTUP OPA0:

Enter the following command to ensure that the operating system does not record for subsequent system reboots the STARTUP_P1 parameter change you made in step 2:

SYSBOOT> SET WRITESYSPARAMS 0

Enter the following command to continue booting:

SYSBOOT> CONTINUE

When the system is booted, the operator console displays the DCL command prompt ($). You are logged in.

Enter the following DCL command:

$ SET NOON

This command directs the operating system to ignore any errors that might occur. If you do not enter this command and you invoke an error, the system logs you out.

Correct the error condition that caused the login failure. (That is, make the necessary repairs to the startup or login procedure, or to the SYSUAF.DAT file.)

Use a text editor to correct the startup or login file. Note that some system consoles might not supply a screen-mode editor. You can also copy a corrected file and delete the incorrect version by using the RENAME and DELETE commands.

Perform a normal startup by entering the following command:

$ @SYS$SYSTEM:STARTUP

Halt the system by pressing Ctrl/P or whatever method is used for your computer. (See Section A.3 for more information about how to halt Alpha computer systems.)

Begin the conversational boot by entering the BOOT command in the following format:

BOOT -FLAGS 0,1 [device-name]

For device-name, substitute the device name of the drive from which you want to boot. For example, if the system disk has a device name of DKA400, enter the following command and press Enter:

>>> BOOT -FLAGS 0,1 DKA400

If your system has a hardware password (various systems support a password that prevents unauthorized access to the console), you need this password for logging in to the console. If you do not have this password, contact HP customer support to reset the hardware console password.

Enter the following commands at the SYSBOOT> prompt:

SYSBOOT> SET/STARTUP OPA0:
SYSBOOT> SET WINDOW_SYSTEM 0
SYSBOOT> SET WRITESYSPARAMS 0
SYSBOOT> CONTINUE

The first three commands request that:

The last command causes the booting to continue.

At the DCL prompt, the system now accepts startup commands directly from the console. Enter the following two commands as shown. These commands allow a normal system startup while you are left logged in on the console. Without the SPAWN command, you would be logged out when the startup completes.

$ SPAWN
$ @SYS$SYSTEM:STARTUP

Once you log out of this session, the system completes the startup and can be used normally. Optionally, you can choose to reboot the system.