User guide

2: Software Installation

DC 900-1333P 83

Edit the boot configuration file (

freeway\boot\bootcfg.xxx

) as follows:

1. Uncomment the physical parameters associated with each ICP in your Freeway.

2. For all Freeways, modify the

slave_address entry of each ICP to match your config-

uration. For Freeway 1150/1200/1300, also modify the

bus_number entry of each

ICP. Appropriate slave addresses (and bus numbers where applicable) are shown

in a table at the beginning of the boot configuration file.

3. Modify the name of the load file in each

download_script entry to match your pro-

tocol or toolkit (for example,

x25load or sraload).

4. If you have moved the load files from the

boot directory, enter the path names for

the load files in each

download_script entry. If no path name is provided in the

download_script entry, Freeway searches the System Boot Directory specified in the

Freeway System Boot Parameters menu (Figure 4–27 on page 149) for the load

file indicated.

5. If you will be using the server-resident application (SRA), uncomment the lines

sra_module = sraxxx.o

and sra_entry = sraInit to load and run the example SRA soft-

ware at boot time. Also modify the

tsi_config_file parameter to use the muxcfg.sra

file.

Step 2: Edit the load file (

pppload)

The Freeway server release G (and later) installs the XIO image files in the

freeway\boot

directory. Prior to June 1, 1998, the XIO image files were distributed in the freeway\icp-

code\icpxxxx\osimpact

directory. As a result, the load files provided with protocols with a

1. Freeway 1100 uses bootcfg.isa (ICP2424) or bootcfg.pci (ICP2432). Freeway 1150/1200/1300 uses

bootcfg.pci. Freeway 2000/4000/8800 uses bootcfg.vme. Any Freeway using ICP_IP virtual ICP devices may

use

bootcfg.ip.

xxx = 486 for Freeway1100/1150/1200/1300, 68K for a Freeway 2000/4000/8800 with an MVME 162

CPU, or

ppc for a Freeway 2000/4000/8800 with an MVME 2600 CPU.