Now the following should be entered from the VCP:

1.Press the BREAK key to pass control to the VCP program if not already in VCP mode.

2.For disk on the HPIB/SCSI bus, enter:

%bdcbuscfile[,ss]

Default is BOOT.CMD::SYSTEM (or system)

Default is 2027 (HPIB) or 6027 (SCSI)

where:

%bdc Execute the disk bootstrap loader program for the disk device, including the CTD. The loader will load the boot extension (BOOTEX) into low memory. BOOTEX will set up the swap area, the memory allocation table, and relink and RP program files specified in the command file. BOOTEX will then copy part of itself to the top of physical memory and will load in the system file. When loading is complete the system starts execution immediately (unless the suspend `SS' was added).

bHPIB/SCSI address of the disk drive where your target system file resides. Default address is 2 for HPIB, 6 for SCSI.

uUnit number or head number of the disk drive (07) where the system file resides. Default value is 0.

sc

Select code of the HPIB/SCSI card to which the disk is interfaced. The select

 

code is switchselectable on the card. The default select code is 27 octal.

file

Name of the boot command file to be used by BOOTEX. The file for a disk

 

volume must be in directory SYSTEM. As shown above, the default file name

 

that BOOTEX will use is BOOT.CMD::SYSTEM (or SYSTEM for a FMGR

 

disk cartridge). However, if you have named your boot command file anything

 

other than the default file name, you will have to supply the name to the VCP

 

program to be passed to the boot extension. This allows you to store multiple

 

systems on one disk, and specify to the VCP program to be booted. Further, if

 

you want to execute any of the diagnostic programs, you may pass the name of

 

the diagnostic to be placed into memory by BOOTEX.

,SS

When SS is appended to the file name, a •cold" load will result. That is, the

 

system will be loaded into memory by BOOTEX, and BOOTEX will halt. You

 

can then alter the system with VCP commands, and start up by using the %E

 

VCP command.

 

Note that SS must be separated from the file name with a space or a comma.

If you wish to load a memory image system file directly (the output file from BUILD for a memorybased system, for example) the process is very similar to that described above. The file name is the name of the memory image system file instead of the boot control file. BOOTEX detects that the file is a system file instead of a boot control file and simply loads the system into memory.

H4 VCP Boot Information