# Using MadgeBoot to configure the Smartrom

To use the MadgeBoot utility to configure the Smartrom, boot up using the Madge Install disk and press [F4] from the MadgeBoot menu. (For information about password protection, see Password protection for Ringnodes.) The Smartrom window gives you options to perform the following:

- Changing Smartrom images

- Default booting schemes

- Specifying a server to boot from

- Specifying a boot image

Changing Smartrom images

To specify the Smartrom image you wish to use, type:

ATPLUS, NW, NRPL, or RPL. (Only type ATPLUS if your Ringnode is an AT Plus or ISA Client Plus.)

Default booting schemes

This option applies only to AT Plus and ISA Client Plus Ringnodes. To choose a booting scheme for ATPLUS.ROM to use by default, type NW, or NRPL.

If you specify a default booting scheme, this disables the prompt that asks you (or the workstation user) to choose, at boot time, which scheme to use. It also prevents workstations booting from the hard disk.

Specifying a server to boot from

To specify a server to boot from using NetWare Remote Reset, type the name of a server. By default, NetWare Remote Reset uses the first NetWare server that it finds. (Only specify a server if you are using NetWare Remote Reset.)

Specifying a boot image

To specify a boot-image file for NetWare Remote Reset to use, type the name of a boot-image file. By default, NetWare Remote Reset uses NET$DOS.SYS. (Only specify a boot-image file if you are using NetWare Remote Reset.) To enable the workstation to boot from the:

- Floppy disk, the hard disk, or the nework: type B.

- Hard disk or the network: type H.

- Floppy disk or the network: type D.

If you have specified a default booting scheme (see above) and you choose B or H, the workstation is prevented from using the hard disk to boot from.

If your workstation has a configurable Start-up Sequence, configure the order of booting from there, (rather than from the Smartrom window). Then, run SMARTROM.EXE and include /rplaware on the command line. This ensures that the Smartrom does not take control of booting until the Start-up Sequence finishes.