Remote Boot to NetWare Server ============================= Introduction: ------------- This document describes the procedures to install RPL server on NetWare file server. Install the Novell 3.X, 4.X RPL server: --------------------------------------- 1. Create a boot image 1.1 You must create a remote boot diskette. The files on this boot diskette, for example, should include the following files: COMMAND.COM IO.SYS (attrib -s -h io.sys) MSDOS.SYS (attrib -s -h msdos.sys) HIMEM.SYS EMM386.EXE LSL.COM PNPODI.COM IPXODI.COM NETX.EXE NET.CFG AUTOEXEC.BAT CONFIG.SYS The NET.CFG file may contain these lines: LINK DRIVER PNPODIT Frame Ethernet_802.2 # Frame Ethernet_802.3 # Frame Ethernet_II # Protocol IPX 0 Ethernet_802.3 The AUTOEXEC.BAT file may contain these lines : DOSKEY LSL PNPODI (Ethernet ODI Driver) IPXODI NETX PATH F:\LOGIN; SET COMSPEC=F:\LOGIN\COMMAND.COM The CONFIG.SYS file may contain these lines : DEVICE=HIMEM.SYS DEVICE=EMM386.EXE NOEMS /Y=Y:EMM386.EXE *** STACKS=9,256 DOS=HIGH,UMB FILES=30 BUFFERS=30 LASTDRIVE=E FCBS=16,8 Note: DEVICE=EMM386.EXE NOEMS /Y=?:EMM386.EXE you must replace the '?' with the drive letter that maps to your DOS path on the server. 1.2. Boot a workstation with at least one floppy disk drive, and login to the server as SUPERVISOR. 1.3. Change directory to SYS:SYSTEM 1.4. Insert the DOS boot diskette in driver A: and run the DOSGEN utility. This creates a DOS boot image file named NET$DOS.SYS. You can rename NET$DOS.SYS to whatever you want. 1.5. Copy all boot image files to the SYS:LOGIN directory. 2. Create BOOTCONF.SYS text file 2.1 Create BOOTCONF.SYS in SYS:\LOGIN directory if you have multiple boot images. The BOOTCONF.SYS file format is as below: Node ID Number = Boot image files... 2.1.1 Single boot image for each node ID 0x0000B4000012 = ISAPNP.SYS 0x0000B4000013 = NET$DOS.SYS 2.1.2 Multiple boot images for each node ID 0x0000B4000012 = NET$DOS.SYS ISAPNP.SYS 0x0000B4000013 = NET$DOS.SYS NE2000.SYS 2.1.3 Using wildcard characters 0x0000B401* = NET$DOS.SYS ISAPNP.SYS or 0x0000B4* = ISAPNP.SYS or 0x*,* = NET$DOS.SYS ISAPNP.SYS NE2000.SYS Multiple boot images will cause the BOOTROM program to display image options on the workstation screen. The screen looks like Place CURSOR on DISK IMAGE file; Hit ENTER when Ready: NET$DOS.SYS ISAPNP.SYS NE2000.SYS Note: 1. ISAPNP.SYS, NE2000.SYS are renamed from NET$DOS.SYS. 2. 0x*,* stands for all nodes. 3. If you don't have BOOTCONF.SYS file or Node number does not match with those specified in BOOTCONF.SYS, you will boot the default image. 3. Copy all RPL related files to file server 3.1 Copy RBOOT.RPL, ETHER.RPL to the SYS:LOGIN directory. 3.2 Copy RPL.NLM to the SYS:SYSTEM directory. Note: This depends on file server's version. In the RPL developer's kit, for Netware 3.11, use .\RPL\NLM\311\RPL.NLM; for Netware 3.12/4.x use .\RPL\NLM\40\RPL.NLM; 4. Load RPL.NLM module and bind RPL.NLM 4.1 Load RPL.NLM module and bind RPL.NLM to the 802.2 Ethernet adapter. 4.2 Edit the AUTOEXEC.NCF file in the SYS:SYSTEM directory to load RPL modules once the file server starts up. For example: file server name FTEST ipx internal net 831123 load NE2000 port=300 int=3 name=ftest_1 frame=ETHERNET_802.2 load NE2000 port=300 int=3 name=ftest_2 frame=ETHERNET_II load NE2000 port=300 int=3 name=ftest_3 frame=ETHERNET_802.3 load NE2000 port=300 int=3 name=ftest_4 frame=ETHERNET_Snap bind ipx to ftest_1 net=21 bind ipx to ftest_2 net=22 bind ipx to ftest_3 net=23 bind ipx to ftest_4 net=24 ; ---------- for RPL file server ----------------- load rpl bind rpl to ftest_1 ; ---------- end for RPL file server ----------------- mount all load monitor 4.2 Shutdown and reboot the file server to have AUTOEXEC.NCF take effect. (Optional) 5. Configure the Ethernet adapter to enable Boot ROM support. 5.1 Place the PROM on the top of the socket and push the PROM into the socket gently, making sure not to bend the pins on the PROM. 5.2 Configure the Ethernet adapter to "Boot ROM Enable" using setup program.